-
1
- #1
I recently upgraded my single-site IP Office as well as an 8-site SCN, and want to post some of the bugs I encountered. Hope this is helpful to anyone upgrading to Server Edition. They seem like little things but if not caught can cause severe problems.
Manager problems
1. Can’t save changes due to the “No more than 300 hunt groups are allowed in Non-select IP Office Solution”. This has already been mentioned on this forum, and can be fixed by applying Critical Patch Manager 9.1.1.12 Build 1. But you need to get this from Avaya.
2. System short codes: at random times voicemail collect short codes are missing the VMPro module name between the quotation marks. So “MainAutoAttendant” is imported as “”. Which can manifest itself as an unwanted busy signal.
3. Hunt groups: sometimes the hunt group members aren’t imported, so you have to add them manually. An empty hunt group can also result in a disconnect or busy signal (but not always).
4. User rights groups: Need to be rebuilt from scratch. Be careful because the old user rights names still appear in the user profiles after they’re imported. You may even need to rename them and then apply the new user rights profiles to each user.
5. PRI line groups: Can’t number them as line 0 anymore. If you have multiple sites in your solution each site needs its unique line group.
6. Call Park buttons: In multiple site configurations, you may need to program unique Park IDs at each site. For example, in my 8-site network, one site’s parked calls could be retrieved from phones at several other sites. To correct this I programmed the Call Park 1-2-3 Action Data fields as 4-5-6 at one site, 7-8-9 at another, etc.
7. User login and voicemail codes. They look like they're in the user profiles after importing, but it's an illusion. You need to either reset them or put in new ones.
Voicemail Pro problems
Lots of subtle but potentially very serious problems here.
1. Short codes and ARS numbers no longer supported in transfer actions. Before the upgrade, entries such as *9501 or 917075551212 programmed in basic transfer actions would route the caller out of Voicemail Pro. No longer. The only way I’ve gotten this to work is to create a phantom user in Manager, unconditionally forward it to the outside number, then replace the short code or ARS number previously programmed with the phantom user extension.
2. User variables: Sometimes data is missing. For example, in a set user variable action, there may be missing data in the specific/”assign the following user variable” field.
3. Test conditions: see User variables, information may be missing from the Specific tab.
4. Specific group start points: touch tones not recognized in queued start point actions. I’ve got an open case with Avaya to address this. I built a call flow that used to work pre-Server Edition, where a caller can opt out of the queue and leave a message. Now the DTMF tones don’t work.
If anyone else has experienced problems with Server Edition please post them here. Thanks!
Manager problems
1. Can’t save changes due to the “No more than 300 hunt groups are allowed in Non-select IP Office Solution”. This has already been mentioned on this forum, and can be fixed by applying Critical Patch Manager 9.1.1.12 Build 1. But you need to get this from Avaya.
2. System short codes: at random times voicemail collect short codes are missing the VMPro module name between the quotation marks. So “MainAutoAttendant” is imported as “”. Which can manifest itself as an unwanted busy signal.
3. Hunt groups: sometimes the hunt group members aren’t imported, so you have to add them manually. An empty hunt group can also result in a disconnect or busy signal (but not always).
4. User rights groups: Need to be rebuilt from scratch. Be careful because the old user rights names still appear in the user profiles after they’re imported. You may even need to rename them and then apply the new user rights profiles to each user.
5. PRI line groups: Can’t number them as line 0 anymore. If you have multiple sites in your solution each site needs its unique line group.
6. Call Park buttons: In multiple site configurations, you may need to program unique Park IDs at each site. For example, in my 8-site network, one site’s parked calls could be retrieved from phones at several other sites. To correct this I programmed the Call Park 1-2-3 Action Data fields as 4-5-6 at one site, 7-8-9 at another, etc.
7. User login and voicemail codes. They look like they're in the user profiles after importing, but it's an illusion. You need to either reset them or put in new ones.
Voicemail Pro problems
Lots of subtle but potentially very serious problems here.
1. Short codes and ARS numbers no longer supported in transfer actions. Before the upgrade, entries such as *9501 or 917075551212 programmed in basic transfer actions would route the caller out of Voicemail Pro. No longer. The only way I’ve gotten this to work is to create a phantom user in Manager, unconditionally forward it to the outside number, then replace the short code or ARS number previously programmed with the phantom user extension.
2. User variables: Sometimes data is missing. For example, in a set user variable action, there may be missing data in the specific/”assign the following user variable” field.
3. Test conditions: see User variables, information may be missing from the Specific tab.
4. Specific group start points: touch tones not recognized in queued start point actions. I’ve got an open case with Avaya to address this. I built a call flow that used to work pre-Server Edition, where a caller can opt out of the queue and leave a message. Now the DTMF tones don’t work.
If anyone else has experienced problems with Server Edition please post them here. Thanks!
