Avaya CMC1, Maintenance Procedures

Page: 141 / 426

Server initialization, recovery, and resets
Link Recovery
Maintenance Procedures 141
December 2003
• MultiVantage Connection Server (MVCS) Version 2.0 and above
• Avaya Softconsole R2: firmware version 2.000 and above
NOTE:
As of this writing, there are no plans for the R2 version of Softconsole. But by the time it
becomes available, the iClarity component that actually provides this feature will be
available and that is what Softconsole will use.
Interactions
Internationalization
The H.323 Link Bounce Recovery feature does not rely upon nor is it affected by international
telecommunications PTT variations or standards implementations.
Feature limitations
Since there is no communication possible between the Gateway and the IP endpoint during a link outage,
button depressions are not recognized, feature access codes do not work, and any other type of call
handling ceases. In essence, the server cannot react to any stimuli until the H.323 signaling link is
restored.
At a minimum, the features listed below might be impacted by a link bounce:
• Call Forward
• Call-coverage: stations
• Call-coverage: VDNs
• Call-pickup
• Displays
• Drop
• Group Page
• Hold
• IP-Direct/Shuffling
• Last Number Dialed
• Priority Calling
• Station Hunting
• Terminating Extension Groups
• Transfer
• TTI/PSA
Cross-Product compatibility/commonality
In general, the time delay caused by a failed network connection could result in unacceptable outcomes,
even though calls in progress are not lost. Although the IP endpoint might eventually reconnect to the
original Gateway, the end user might experience what they perceive to be a lack of service while the
endpoint is trying to re-register. Since users cannot put a call on hold, transfer, send-all-calls, and use
other trivial or even advanced switch features, they might conclude that “the phones aren't working.”