Log in to the EMS web interface with administrator credentials.
From the Device menu, click the SBC name to administer.
In the navigation pane, click Configuration Profiles > Routing .
On the Routing Profile page, click Add.
In the Profile Name field, type the routing profile name in the Route_to_Avaya_Server format.
Click Next.
The system displays the second Routing Profile page.
Optional In the URI Group field, select the URI group for the routing profile.
For example, if you have a routing profile Test1 and URI Group user 1234@test.com, any request message to user 1234@test.com will resolve profile Test1.
Optional In the Time of Day field, enter the time-of-day profile.
Note:
Remote users must not use the time-of-day profile for the routing profile.
In the Load Balancing field, click one of the options. You can configure up to 20 next hop addresses with the available load balancing.
Priority: From the list of next-hop addresses, request messages take the first priority. If a request message fails to reach the first next-hop address, the request message takes the second priority.
Round Robin: Request messages are delivered to the next-hop address on a round-robin basis. Any request message is processed sequentially, beginning again with the first next-hop address, in a circular manner.
Weighted Round Robin: Each configured next-hop address is assigned a weight. Request messages route to the next-hop address on the basis of the assigned weight.
DNS/SRV: Used for configuring multiple domain names. If selected, you can enable or disable NAPTR. Avaya SBC uses DNS priority to route the message. If you disable NAPTR, specify the transport type.
In the Transport field, click TCP, UDP, or TLS.
If you define the transport type in the Transport field, the system deactivates the common Transport Type field.
Select the Next Hop Priority check box.
If you enable this setting, Avaya SBC processes the configured next-hop address in the event of failure routing.
Select the Ignore Route Header check box to enable the system to ignore the message route header while resolving message routing.
