User's Manual

Avaya Branch Gateway Manager 10.0 Page 251
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Configuration Settings: Line
5.4.12 SM Line
This type of line can only be added in the configuration of an Avaya Branch Gateway system fitted with an B5800 Branch
Gateway System SD card. This type of line is used to create a SIP connection between an B5800 Branch Gateway system
and the Avaya Aura® Session Manager in the Avaya Aura® network.
If the Avaya Aura® network has multiple Avaya Aura® Session Managers to provide redundancy, two SM lines can be
added, one configured for each Avaya Aura® Session Manager.
For full details refer to the B5800 Branch Gateway Installation and Configuration Notes.
5.4.12.1 Session Manager
Usability
· Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number: Default = Automatically assigned
This value is automatically assigned by the B5800 Branch Gateway and should be unique for each line added to the
configuration.
· Session Manager line prioritization – Up to two Session Manager lines can be configured. Beginning in Release
6.2, the two Session Manager lines are prioritized based on the line number. The lower line number is considered
the primary Session Manager line. For example, if the first Session Manager line is configured as line number 17
and the second Session Manager line is configured as line 18, then line number 17 is considered the primary
Session Manager line. If you want to designate the second Session Manager line (line 18 in this example) as the
primary Session Manager line, you must change one or both of the line numbers so that the second Session
Manager line is configured with a lower number than the current primary line.
· Session Manager line redundancy – Based on the priority of the Session Manager lines designated by the line
number, the active line to which the Avaya Branch Gateway sends all calls will always be the highest priority
Session Manager line in service. That is, if the primary Session Manager line is in service, it will be the active line
for sending calls. If the connection to the primary Session Manager line is lost, causing the Avaya Branch Gateway
to switch to the secondary Session Manager line, then when the primary line comes back up later, the Avaya
Branch Gateway reverts back to the primary Session Manager line.
· In Service: Default = Enabled
This option can be used to manually take the SM line out of service. It does not reflect or set the actual state of the
line.
· SM Domain Name
This should match a SIP domain defined in the Avaya Aura® Session Manager system's SIP Domains table. Unless
there are reasons to do otherwise, all the B5800 Branch Gateway systems in the Avaya Aura® network can share the
same domain.
· SM Address
Enter the IP address of the Avaya Aura® Session Manager the line should use in the Avaya Aura® network. The same
Avaya Aura® Session Manager should be used for the matching Entity Link record in the Avaya Aura® configuration.
· Outgoing Group ID: Default = 99999
This value is not changeable. However note the value as it is used in B5800 Branch Gateway short codes used to route
calls to the Avaya Aura® Session Manager.
· Prefix: Default = Blank
This prefix will be added to any source number received with incoming calls.
· Max Calls: Default = 10
Sets the number of simultaneous calls allowed between the B5800 Branch Gateway and Avaya Aura® Session Manager
using this connection. Each call will use one of the available licenses that are shared by all SIP trunks configured in the
system.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect (System | Telephony | Telephony ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· URI Type: Default = SIP. Release 6.2+
When SIP or SIPS is selected in the drop-down box, the SIP URI format is used (for example, [e-mail]).
This affects the From field of outgoing calls. The To field for outgoing calls will always use the format specified by the
short codes used for outgoing call routing. Recommendation: When SIP Secured URI is required, the URI Type should
be set to SIPS. SIPS can be used only when Layer 4 Protocol is set to TLS.
· Network Configuration: Default = TLS. Release6.2+.
159 159