Use the crankbackProfile parameter to assign a specific crankback profile to a zone.

A crankback profile consists of a list of call release codes that the SBC uses to determine whether to reroute (or "crankback") a call if the call does not connect successfully to the initial destination. If egress signaling returns a release code that is in the reason code list in the crankback profile, the SBC attempts to reroute the call. If a release code is not in the list, the SBC returns the release code to ingress signaling rather than attempting to reroute the call. 

For flexibility, crankback profiles can be configured at three levels: trunk group, zone, and global. By default, the "default" crankback profile is assigned at the SBC global level, while the trunk group and zone level crankback profile settings are initially empty (" "). Thus in the SBC default configuration, trunk groups and zones inherit the default crankback profile from the global level. However, if you configure a profile at the trunk group or zone level, the user-specified profile assigned at the most specific level takes precedence.

Command Syntax

The CLI syntax for assigning the zone crankback profile is shown below.

Zone Crankback Profile Option
% set addressContext <address context> zone <zone> crankBackProfile <profile name>

Command Parameter

ParameterLength/RangeDefaultDescription
crankBackProfile <profile name>23 characters" " (empty string)Use this option to specify the crankback profile to apply at the zone level. No profile is assigned by default. If no profile is specified, the zone inherits the crankback profile assigned at the global level. 

Configuration Example

The commands in the following example configure "zone1" with a specific, user-defined profile called "zone1Crankback." Any trunk groups within zone1 that are not assigned a crankback profile also use the zone1Crankback profile, which they inherit from the zone configuration.

% set addressContext AC1 zone zone1 crankBackProfile zone1Crankback
% commit