The SIP routing system uses the Routing Profile field from the matched subscriber or server flow to take routing decisions. The SIP routing system uses the Next Hop servers specified on the Routing Profile page to determine the communication addresses and transport of the SIP entity for which the incoming SIP call is retargeted.

For DNS NAPTR/SRV procedures followed by Avaya SBC to resolve the Next Hop Address fields, see Locating SIP Servers.

After the SIP server is located, the SIP routing system compares the IP address of the located SIP server. The SIP routing system compares the IP address with the IP addresses or Resolved IP Addresses for the FQDNs associated with the provisioned SIP Server Configurations, looking for a match.

If a match is found, the SIP routing system determines the server flow associated with the matched server configuration. The SIP routing system continues with server flow matching.

If no matching server configuration is found, the SIP routing system rejects the registration as there is no valid server configuration.