User's Manual

6. In the Managed Bandwidth Units field, accept the default setting.
7. In the Total Bandwidth field, accept the default setting, blank
8. In the Default Audio Bandwidth field, accept the default setting.
9. In the Location Pattern section, click Add to add a location pattern.
10. In the IP Address Pattern field, enter an IP address pattern that matches the IP
LAN address range.
The * character can be used as a match-all wildcard. For example, the pattern
192.168.42.* matches all addresses in the range 192.168.42.1 to
192.168.42.255.
11. In the Notes field, enter notes about this location pattern, as appropriate.
12. Click Commit.
Creating adaptations
Occasionally calls to or from the branch may require digit conversion in order to ensure correct
routing. For example, reinserting an external dialing prefix. This is done using a set of digit
conversions stored by the digit adaptation associated with the SIP entity.
Adaptations are optional and are deployment specific. For more information, see “Adaptations”
in “Chapter 5: Managing Session Manager routing” in Administering Avaya Aura
®
Session
Manager, document number 03–603324.
Creating SIP entities
A SIP entity is required for each branch system. This is in addition to the SIP entities that should
already exist for Session Manager and Communication Manager Feature Server or
Communication Manager.
1. On the System Manager console, under Elements, click Routing.
2. In the left navigation pane, click SIP Entities.
3. On the SIP Entities page, click New to create a new SIP Entity.
4. On the SIP Entity Details page, in the Name field, enter the name of the SIP
entity.
5. In the FQDN or IP Address field, enter the IP address of the B5800 Branch
Gateway system LAN interface configured for the Session Manager line
operation.
6. In the Type drop-down box, select Survivability Server.
Session Manager 6.1
Implementing the Avaya B5800 Branch Gateway November 2011 151