Crankback After 3xx Redirection

For a 3xx redirect response with multiple contacts (having host port as

SIP signaling IP address), if the trunk group is disabled or the CAC limit is reached for a previous contact's route the following applies:

• The subsequent contacts are tried.
  
  For example, when A calls B, ERE/PSX returns three routes – Route1, Route2, and, Route3.
  Unable to show "metadata-from": No such page "_space_variables"
  sends INVITE towards B on Route1. B replies (3xx) with three contacts (Contact1, Contact2, and Contact3). The host port of all the three contacts is
  Unable to show "metadata-from": No such page "_space_variables"
  SIP signaling IP address. The ERE/PSX is checked for the route towards Contact1. A single route RouteA1 is returned. When RouteA1 trunk group is disabled or CAC call limit is reached, the subsequent contacts (contact2 and contact3) must be tried. Therefore, Invite is sent for contact2.
  
  
• The subsequent routes in the original route set are tried if all the contacts are exhausted.
  
  For example, when A calls B, ERE/PSX returns three routes – Route1, Route2, and Route3.
  Unable to show "metadata-from": No such page "_space_variables"
  sends INVITE towards B on Route1. B replies (3xx) with three contacts (Contact1, Contact2, and Contact3). The host port of all the three contacts is
  Unable to show "metadata-from": No such page "_space_variables"
  SIP signaling IP address. ERE/PSX is checked for the route towards Contact1. A single route RouteA1 is returned. When RouteA1 trunk group is disabled or CAC call limit is reached, the subsequent contacts (contact2 and contact3) must be tried. If all the contacts fail original routes, Route2 and Route3 must be tried.

SIP Redirect Handling

manages the process of trying "targets" to reach the destination of a SIP call. The targets consist of:

• Routes returned by the initial route lookup performed by the PES module.
• Explicit destinations received in 300 redirect response messages.
• Additional routes determined as a result of re-querying PSX PES, which is indicated in a 300 redirect response.

Re-querying occurs when the IP address of the redirect contact is 

that sent the INVITE.

Important aspects of 

SIP redirect processing are:

• Unable to show "metadata-from": No such page "_space_variables"
  maintains two lists, routes and redirect contacts. The merge/purge process applies only to redirect contacts, not the original routes.
• A PSX Signaling Profile drop-down allows the provisioner to configure one of the following:
  • No redirection allowed.
  • Multiple re-directions per route.
  • A single redirection per route.
• Unable to show "metadata-from": No such page "_space_variables"
  processes only the first 10 contacts in any single redirect received.
• Unable to show "metadata-from": No such page "_space_variables"
  allows a maximum of 10 redirect attempts per route.
• If one of the redirects cause 
  Unable to show "metadata-from": No such page "_space_variables"
  to re-query PSX, all previously determined routes and redirects are purged. A maximum 10 such redirect re-queries of PSX are allowed per call.

The first redirect contact causes a PSX query (the host portion of the contact URI is

SIP signaling IP address) and therefore the rest of the contacts are purged.