Advertisement
AVAYA E1/QSIG
routed via coverage to a QSIG trunk connected to a Modular Messaging
system equipped with the Find Me feature, the Find Me feature would
place the call to the user and connect the calling and called parties.
When the Communication Manager received the Transfer Complete
messages from the Messaging system, and Path Replacement was
enabled on the Communication Manager, it would proceed with the
Path Replacement. While performing this task, the Trunk-to-Trunk
Transfer parameter would be checked, and if set to "none", the call
between the calling party and the found user would be torn down. A
change was put into the following releases and load numbers to correct
this:
1.3 Load 537.0
2.0 Load 226.0
2.1 Load 411.0
When the Communication Manager System is running on one of these loads
or a later one, the Path Replaced call will not be torn down.
8.12 Call Call transfers may not display the Call ID to ringing phones.
The Call ID is not provided until the subscriber answers the phone.
•
This issue was resolved in MM 3.0 where the Calling Party Number
(number only, not the name) is displayed.
•
Starting with MM 5.1, both name and calling party number will be
displayed on ringing phones. Please note, for name to be displayed the PBX
must send the MAS the Calling Name using the QSIG Name Identification
Supplementary Services Protocol (ECMA-164).
8.13 The Communication Manager supports up to 28 lines of input
within the DCS to QSIG TSC Gateway. This limitation affects how
many entries can be configured for remote locations in a centralized
voice mail environment.
8.14 If the Avaya CM is networked to a non-Avaya PBX using H.323
trunking, please consult PSN001841u.
8.15 If the Avaya CM is networked to non-Avaya PBXs that use MM for
voice messaging the Avaya CM integrated to MM should be at the
following minimum releases:
Avaya CM 3.1.4 SP 2 or later
Avaya CM 3.1.5 SP0 or later
Avaya CM4.0.3 base or later
Avaya CM 4.0.4 base or later
Avaya CM 5.0 SP3 or later
Avaya CM 5.1.0 base or later such as 5.1.1 and 5.1.2
8.16 Re-Route Request set to "y" (page 2 of the Hunt Group Form)
eliminates potential call tromboning where 3-legs may remain active
and Path Replacement in effect appears to have failed. Should remote
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1
32
Advertisement
