Creating a Routing Profile for a Call Server

Last Updated : Apr 26, 2023 |

About this task

Use this procedure to create a routing profile with the next hop as a call server address.

Procedure

  1. Log in to the EMS web interface with administrator credentials.
  2. From the Device menu, click the SBC name to administer.
  3. In the navigation pane, click Configuration Profiles > Routing.
  4. 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.

  5. In the Profile Name field, type the routing profile name in the Route_to_Avaya_Server format.
  6. Click Next.

    The system displays the second Routing Profile window.

  7. 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.
  8. Optional In the Time of Day field, enter the time-of-day profile.

    Remote users must not use the time-of-day profile for the routing profile.

  9. In the Load Balancing field, enter one of the following 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 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 the 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.

  10. In the Transport field, enter TCP or TLS.

    If you define the transport type here, the system deactivates the common Transport Type field.

  11. Select the Next Hop Priority check box.

    If you enable this setting, Avaya SBC processes the configured next-hop address when routing fails.

  12. Select Call Server from Server Configuration.
  13. Click Add to configure the next-hop address.
  14. Click Finish.