Advertisement
AVAYA E1/QSIG
The caller immediately hears the greeting of 7001 (no additional
ringing) and can subsequently leave a message.
Note: For full details on how to configure and implement the Transfer
to QSIG Voice Mail feature on your Avaya switch, please consult your
Avaya Sales or Support representative.
8.8
Possible reasons for QSIG Path Replacement failure.When your
QSIG Modular Messaging systems Auto Attendant, Caller Application
or Find Me features are transferring a call, you will see a second
channel in Port Monitor appear busy until the transfer has been
completed. After the transfer has been completed you will see that both
channels are now idle in Port Monitor, this shows that the QSIG Path
Replacement feature has completed successfully.
Note: Path Replacement is a PBX function.
There is no MM programming to support/control Path Replacement.
However there are some switch configurations that will cause Path
Replacement to fail, therefore your MM Server will stay bridge onto the
transferred call, keeping two channels busy in Port Monitor. The
following list of features can cause Path Replacement to fail:
Call Vector. A call that has experienced SS-CT (Supplementary
Service Call Transfer) that terminated to a vector and received answer
treatment can have its path replaced. This is allowed only after a true
user answers the call so that vector processing is completed. A vector
step of recorded announcement or wait listening to music could cause a
CONNECT message to be sent back and make the far end think ANF-
PR (Path Replacement Additional Network Feature) could take place. If
the PR Propose is received while still in vector processing, the vectoring
PBX will deny the ANF-PR attempt but will initiated its own attempt at
ANF-PR when a user does answer the call.
Data Call Setup. ANF-PR platform will reject the ANF-PR invocation
request if the old connection is a data call. ANF-PR may cause
disruption in user information during switchover of the old connection
to the new connection, so it will be undesirable to disrupt the data call.
For a call where the Bearer Capability Class (BCC) or Information
Transfer Capability, Octet 3 of Bearer Capability IE, indicates that the
call is data call, ANF-PR shall not be allowed.
For a voice grade data and voice, PBX uses the BCC value or
Information Transfer Capability value of "3.1 KHZ audio", so using the
bearer capability information would not be enough to distinguish
between a voice call and voice grade data call. PBX provides a feature
"data pre-indication" which allows using the BCC of the data extension
instead of the voice extension even though the call is originated using
the voice extension. So, ANF-PR shall not be allowed on a call for
which data pre-indication is activated.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1
22
Advertisement
