User's Manual

5. In the SIP Entity 1 drop-down box, select the name of the Session Manager system
that is at one end of the link.
SIP Entity 1 must always be a Session Manager instance. For a Session Manager
line from a B5800 Branch Gateway system, this should match the Session Manager
set as the SM Address in the Session Manager line’s configuration.
6. In the Protocol drop-down box, select TCP.
When TCP is selected, the Port field is automatically set as 5060. This is the port
to which the SIP Entity 2 sends SIP requests.
7. In the SIP Entity 2 drop-down box, select the name of the B5800 Branch Gateway
system that is at the other end of the link.
When you selected TCP in the previous step, the Port field was automatically set
as 5060.
8. Select the Trusted check box.
This check box must be checked. If it is not checked, calls from the associated SIP
Entity 2 will be denied by Session Manager.
9. In the Notes field, enter notes regarding this entity link, as appropriate.
10. Click Commit.
Creating time ranges
Additional time ranges can be created and used with a routing policy to define when the routing
policy is active. For most B5800 Branch Gateway implementations, you do not need to define
additional time ranges. If you need to add or adjust a time range, see “Creating Time Ranges”
in Administering Avaya Aura Session Manager, document number 03-603324.
Creating routing policies
A routing policy is a collection of multiple time ranges and a destination SIP entity. For each
dial pattern configured to route calls received by the Session Manager, the routing policy
associated with that dial pattern defines when and where matching calls are directed.
Separate routing policies are required for each B5800 Branch Gateway entity to which the
Session Manager routes calls. No routing policy is required for Communication Manager
Feature Server systems.
1. On the System Manager console, under Elements, click Routing.
2. In the left navigation pane, click Routing Policies.
3. On the Routing Policies page, click New to create a new routing policy.
Session Manager 6.1
Implementing the Avaya B5800 Branch Gateway November 2011 153