This procedure will create a routing profile with next hop as a Trunk side Server IP address.
Note:
Use the following profile name: Route_to_Trunk_Svr.
Procedure
Log in to the EMS web interface with administrator credentials.
From the Device menu, click the SBC name to administer.
In the left navigation pane, click Configuration Profiles > Routing.
In the Application pane, click Add.
The Application pane displays the existing routing profiles, and the Content pane displays the parameters of the selected routing profile.
In the Profile Name field, type the profile name in the Route_to_Trunk_Svr format.
Click Next.
The system displays the second Routing Profile window.
Log in to the EMS web interface with administrator credentials.
In the navigation pane, click Configuration Profiles > Routing.
In the Application pane, click Add.
The Application pane displays the existing routing profiles, and the Content pane displays the parameters of the selected routing profile.
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 window.
Optional In the URI Group field, select the URI group of 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, enter one of the options. You can configure up to five 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.
Note:
You must create another routing profile for next hop as a SIP trunk address.
Weighted Round Robin: Each configured next-hop address is assigned a weight. The request messages routes to the next-hop address on the basis of the assigned weight.
DNS/SRV: Multiple domain names can be configured. 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, enter TCP or TLS. If you define the transport type here, 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 Trunk Server from Server Configuration.
Click Add to configure the next-hop address.
Click Finish to save the configuration and exit.
This displays the Routing Profile screen, showing the newly created Route_to_Trunk_Svr Routing Profile along with the Route_to_Call_Svr Routing Profile created by the procedure described in Creating Routing Profile for Call Server.
For a failover trunking configuration, select the Next Hop priority checkbox.
Specify the priorities for the configured trunking servers.
Priority 1: the primary server
Subsequent priorities: secondary server(s)
The following are the ways in which Avaya SBC can failover from one trunking server to the next. The ways in which Avaya SBC detects whether the server is reachable.
Heartbeat: Enable this setting on the Server Profile setting.
SIP Timer: SIP RFC 3261 Timer. By default, this functionality is available for all the request messages. If you want to overwrite RFC 3261 timer, use the server interworking profile timer configuration
Server Error Message: If the server sends a 5xx message, Avaya SBC considers the server as currently unavailable.
