TAC03012_GEd 02 1 2009 Alcatel-Lucent.

, All rights reserved

Alcatel-Lucent University Antwerp
1
University
ISAM Voice Operator
Managed with 5520 AMS
Section G: Redundancy
Alcatel-Lucent University Antwerp
University
During class please switch off your mobile, pager or other that may interrupt.
TAC03012_GEd 02 2 2009 Alcatel-Lucent., All rights reserved
2
Course objectives
At the end of this section, you will be able to
Understand MEGACO ISAM Voice Redundancy
TAC03012_GEd 02 3 2009 Alcatel-Lucent., All rights reserved
3
Table of contents
MEGACO ISAM Voice Redundancy . . . . . 4
TAC03012_GEd 02 4 2009 Alcatel-Lucent., All rights reserved
Alcatel-Lucent University Antwerp
4
University
MEGACO ISAM Voice Redundancy
TAC03012_GEd 02 5 2009 Alcatel-Lucent., All rights reserved
5
NVPS 1+1 Redundancy
Both configuration data (including CDE files) and dynamic
data are synchronized with the redundant board
The maximum data synchronization interval is 60s
Redundant NVPS must be in adjacent slots (odd+even)
For FD shelf, the slots of NTIO and NTB dont support NVPS
NT sees difference through LT Protection Group status
Only active NVPS can be managed by AMS
TAC03012_GEd 02 6 2009 Alcatel-Lucent., All rights reserved
6
NVPS Hot Switch Over (HSO)
ISAM Voice supports NVPS hot switch, which means:
POTS/ISDN Established voice calls are not lost. Voice flows are
briefly interrupted although the user does not perceive this
disruption.
POTS/ISDN Calls being established during HSO process are lost
POTS/ISDN Call releases initiated during the HSO process can be
delayed no longer than 2-3 seconds after HSO start
H.248 connection is kept alive
MGC is not aware of the NVPS switchover
Same address for H.248 is held between active NVPS and standby NVPS
When switchover happens, the newly active NVPS will send GARP for
signaling IP/voice IP
The ISDN signaling gateway interface is kept alive (SIGTRAN itf.)
The XLES link between NVPS and POTS/ISDN boards is kept alive
TAC03012_GEd 02 7 2009 Alcatel-Lucent., All rights reserved
7
Triggers for NVPS Switch Over
Criteria for NVPS to be active
The NVPS will be active if its planned on the NT. The other NVPS
board would remain passive standby.
The active NVPS board should be plugged in an odd slot
Triggers for Switch Over
Fatal error (causing a restart) occurs on the active NVPS
Active NVPS is pulled out
Lock/Unplan/Restart the active NVPS
Operator sends the switch over command to active NVPS
Uplink failure between NT and NVPS
TAC03012_GEd 02 8 2009 Alcatel-Lucent., All rights reserved
8
Control Interface with MGC Heart Beat
Direction MGC to MG
MGC will send heart beat messages to ISAM Voice periodically.
ISAM Voice will self-study the time interval of the heart beat messages
and update it if any change. This time interval will be treated as heart
beat period.
If MG has not received any message from MGC during the continuous 7
times of heart beat period, ISAM Voice will judge that MGC is failed.
Direction MG to MGC
ISAM Voice will send heart beat messages to MGC timely. The heart
beat period is defined in CDE file.
MGC will give Reply to ISAM Voice when receiving the MG heart beat
message.
In the condition ISAM Voice MG has not received Reply from MGC, ISAM
Voice will resend the heart beat message for 7 times (currently time
interval is about 2s), if still not receive Reply from MGC, ISAM Voice will
judge that MGC is failed.
> MGC to MG: the heart beat message is a AuditValue command to ROOT termination with NULL
parameter.
> MG to MGC: the heart beat message is a Notify command with it package.
TAC03012_GEd 02 9 2009 Alcatel-Lucent., All rights reserved
9
Control Interface with MGC Process After MGC failure
Process After MGC failure
If there is no secondary MGC, ISAM Voice will periodically try to
register again to the failed MGC.
If there is a secondary MGC, ISAM Voice will try to register to this
MGC. If no response, then he will try again to register to the
primary MGC. If still no response, then to the secondary MGC,
etc
If the ISAM Voice is unable to connect to an MGC within 10
minutes (configurable), it will release all its established RTP
paths.
If the ISAM Voice connects to an MGC, then the normal
registration process takes place between MGC and ISAM Voice.
If the ISAM Voice has established connection with the secondary
MGC, and the primary MGC has recovered, ISAM Voice will not
switch off from the secondary one to the primary one.
> To a failed primary MGC, ISAM Voice will register through a ServiceChange command with the
restartmethod parameter.
> To a secondary MGC, ISAM Voice will register through a ServiceChange command with the
failovermethod parameter.
TAC03012_GEd 02 10 2009 Alcatel-Lucent., All rights reserved
10
Control Interface with MGC MGC/MG Association
The MG may register in one of two ways:
Announce its initial presence.
Indicate that it was commanded by MGC to change its association
MGC Association failure
MG detects the MGC Association failure through the heart beat
mechanism described before.
If MG detects the failure of MGC, it attempts to contact the next
MGC on its pre-provisioned list.
MGC switch over (handoff)
When MGC encounters a failure condition, it may direct the MG
to a specific secondary MGC.
> The MG may register to announce its initial presence with Method=Restart, Reason =cold/warm
> The MG may register to indicate that it was commanded by MGC to change its association with Method =
Handoff, Reason =MGC Directed Change
> If MG detects the failure of MGC, it sends a ServiceChange message with a Failovermethod and a "MGC
Impending Failure" reason. When contacting its previously controlling MGC, the MG sends the ServiceChange
message with restart" method.
> If an MG fails, but is capable of sending a message to the MGC, it sends a ServiceChange with an appropriate
method (Graceful or Forced) and specifies the Root TerminationID. When it returns to service, it sends a
ServiceChange with a "Restart" ServiceChangeMethod.
> When MGC encounters failure condition, it sends a ServiceChange command with a ServiceChangeMethodof
Handoff, a ServiceChangeReasonof 903 (MGC Directed Change) and the address of the new MGC in the
ServiceChangeMgcIDparameter.
> When MG receive hand-offfrom MGC, it then sends a ServiceChange Command to the specified MGC with a
serviceChangeMethodof Handoffand a ServiceChangeReasonof 903 (MGC Directed Change).
TAC03012_GEd 02 11 2009 Alcatel-Lucent., All rights reserved
11
www.alcatel-lucent.com