Specifies the descriptive name of the routing profile

Specifies the URI Group to which the next hop routing profile applies. The options are:

• *

• Emergency

Specifies the time of day for the trunk server to resolve the routing profile.

Specifies the type of load balancing option. The options are:

• Priority

• Round-Robin

• Weighted Round-Robin

• DNS/SRV

Activates or deactivates Naming Authority Pointer. When you select the Load Balancing algorithm as DNS SRV, the EMS server enables the NAPTR check box. If you disable NAPTR, you must specify the transport protocol.

Assigns the transport type for each next hop address. Select the protocol for transporting outgoing signaling packets.

The options are:

• None

• TCP

• TLS

• UDP

In this case, Common Transport Type field is unavailable. You can select the transport type according to the next hop address.

Enables LDAP based call routing.

Displays a collection of existing LDAP server profiles. Use this field to define the LDAP server profile for a routing profile and sends the LDAP search requests to the LDAP server.

This field is available only when you select the LDAP Routing check box.

Displays the configured LDAP Base DN to search the users using the LDAP server.

This field is available only when you select the LDAP Routing check box. You must specify only one Base DN to search the user using the LDAP server.

Specifies if the matched attributes based on LDAP Base DN (Search) will get priority.

This field is available only when you select the LDAP Routing check box.

Enables the alternate routing for using the next routing entry if Avaya SBC fails to route messages using resolved routing entry.

This field is available only when you select the LDAP Routing check box.

Specifies if the Next Hop Priority option is enabled. If Avaya SBC fails to route the message using resolved routing entry from message, that is using request URI or Route Header then the system will send the message to the alternate routing entry from the routing profile.

Specifies the Next Hop configuration for the In-Dialog message. If you enable the Next Hop In-Dialog option, then the In-Dialog request tries to use the same routing entry to route the message.

Enables Avaya SBC to ignore the Route Header.

Enables support for the E.164 Number Mapping (ENUM) protocol.

Specifies the ENUM suffix that is added to change the number to a domain name.

This field is available only when you select the ENUM check box.

Enables support for Branch Survivability to route messages from Branch Session Manager to Session Manager.

Specifies the server name used to route messages from Branch Session Manager to Session Manager.

This field is available only when you select the Server Name Indication (SNI) check box.

Adds a next hop address.

Specifies the priority and weight assigned for load balancing options.

The search attribute present in the LDAP search request.

This field is available only when you select the LDAP Routing check box.

Specifies the regex pattern that is used to get the phone number from the request URI of INVITE message.

This field is available only when you select the LDAP Routing check box.

Specifies the regex result after getting the phone number from the request URI of INVITE message.

This field is available only when you select the LDAP Routing check box.

Specifies the server configuration.

Specifies the IP address or domain of the Next Hop server. You can add up to 20 next hop addresses.

Assigns the transport type for each next hop address. Select the protocol for transporting outgoing signaling packets.

The options are:

• None

• TCP

• TLS

• UDP

In this case, Common Transport Type field is unavailable. You can select the transport type according to the next hop address.