In this section:
This object creates a Crankback Profile containing a table of call release codes used by the SBC Core to attempt to reroute (or "crankback") a call when a matching code is returned by Egress Signaling. Release codes may be added or removed from this table. Removing a release code from the table causes the SBC software to return that release code to Ingress Signaling rather than attempt to reroute the call.
You can configure up to 20 Crankback Profiles (including default profile). As profiles are created, they are assigned indexes 2, 3, 4, and so on by the SBC (index 1 is reserved for default profile). Index assignments are viewable using the show command.
Use the crankback index number to assign a particular Crankback Profile to a particular SIP, or H.323 trunk group for ingress signaling.
This object influences rerouting policy for SIP 3xx Redirection processing if the IP Profile is configured to use the Crankback Profile. For example, when a SIP 3xx Redirect is initiated and a SIP INVITE message is issued, if a disconnect release code is returned in the SIP response, the Crankback Profile is examined for a matching code. If a matching code is found and at least one more SIP redirect destination is present, a SIP INVITE is issued to that destination.
This scenario is repeated up to ten times, after which additional SIP redirect destinations are disregarded as if not present. However, only four Contact headers in a redirect are accepted and processed. If more than four Contact headers are sent, they are ignored.
If a matching code is found but no additional SIP redirect destination is present, the SIP redirect is terminated with that code. If no matching code is found in the Crankback Profile, then the SIP redirect is terminated with that (unmatched) code.
% set profiles callRouting crankbackProfile <profile_name> attemptRecordGeneration <disabled | enabled> lateCrankback <disabled | enabled> reason <reason code, 1-255> location <location type> useLocationValue <disabled | enabled>
The Crankback Profile Parameters are as shown below:
% set profiles callRouting crankbackProfile CB_CUSTOM attemptRecordGeneration enabled lateCrankback enabled reason 10 location publicLocal % set profiles callRouting crankbackProfile CB_CUSTOM reason 11 location internationalNet % commit % show profiles callRouting crankbackProfile CB_CUSTOM lateCrankback enabled; attemptRecordGeneration enabled; reason 10 { location publicLocal; } reason 11 { location internationalNet; }