Configuration manual

thought to be in service. The Reactive setting is used for an Avaya Aura
®
Session Manager
line currently thought to be out of service.
• If a response is received and is not a 408, 500, 503 or 504 response, the Avaya Aura
®
Session Manager line is treated as in service; otherwise the line is treated as being out
of service.
• If the line is out of service, and call comes from the trunk, the trunks status is changed
back to in service.
• If the line is in service, a call may fail due to either being unable to deliver the message
or receive a 100 response within a configured timeout. The line will not go out of service
because this may be a temporary failure due to a busy system.
• In addition each Avaya Aura
®
Session Manager line can be manually set to in or out of
service using the In Service option on the Avaya Aura
®
Session Manager line's Session
Manager tab.
Enabling branch SIP extension support
About this task
Before adding any SIP extensions, the B5800 Branch Gateway system must be enabled for
SIP extension support. Use this procedure to configure the B5800 Branch Gateway to support
the addition of SIP extensions.
Important:
The configuration changes in the following procedure will require the B5800 Branch
Gateway system to be rebooted.
Procedure
1. From the System Manager console, select the B5800 Branch Gateway device and
click Edit to edit the system configuration for the device. IP Office Manager will be
launched on your PC. For more information, see
Editing a B5800 Branch Gateway
system configuration from System Manager on page 159.
2. In the left navigation pane, click System.
3. Click the LAN1 or LAN2 tab, depending on which branch site LAN interface will be
used for the SIP extensions.
4. In the LAN Settings tab, make a note of the IP Address and IP Mask details as
these will be required during the SIP extension configuration.
5. Click the VoIP tab.
6. Check the SIP Registrar Enable check box. This is necessary for support of SIP
extensions directly by the branch or when providing survivability support for Avaya
Aura
®
SIP extensions.
7. Click OK.
Initial branch configuration
156 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012
Comments? infodev@avaya.com