Provisioning data
SLS requires that the Branch Gateway has connected to an MGC at least once and has
received provisioning information, including:
• Avaya Aura
®
Communication Manager port information sent through the H.248 control
channel:
- Tone sources, including a distinctly different dial tone to inform users that the system
is operating in survivable mode
- Loss plan
• Avaya Aura
®
Communication Manager provisioning information for the options in the
station and trunk media modules is sent through the CCMS channel
• Provisioning and Installation Manager (PIM) queries Avaya Aura
®
Communication
Manager for station/trunk configuration and dial plan routing administration data through
SNMP. Alternatively, the provisioning may be entered manually via an SNMP MIB
browser or via the local Branch Gateway’s CLI interface.
Related topics:
Standard Local Survivability data sources and communication paths
on page 106
Standard Local Survivability data sources and communication paths
Table 3: Figure notes:
1. 248 call signaling and configuration data
2. CCMS messages through Clear Channel
3. Branch Gateway Maintenance Channel
4. PIM extracts Communication Manager translation subset through OSSI
Standard Local Survivability (SLS)
106 Administering Avaya G430 Branch Gateway
October 2013
Summary of Contents for G430
Page 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Page 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Page 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Page 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...