Crankback Profile - CLI

Use the crankbackProfile object to configure crankback profiles. 

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 crankback 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. 

You can configure which release codes trigger rerouting by adding or removing release codes from a crankback profile. You also have the option to associate a location value with a specific reason code. When a location is configured and enabled, the specified location value must be included along with the reason code in the egress disconnect signaling to trigger crankback. Including a location with a reason code is optional.

The SBC provides a default crankback profile (named "default"), the contents of which can be edited. Or, you can create your own crankback profiles. The SBC supports a total of 20 crankback profiles in the system.

For flexibility, crankback profiles can be assigned 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

% set profiles callRouting crankbackProfile <profile_name> 
	attemptRecordGeneration <disabled | enabled> 
	lateCrankback <disabled | enabled> 
	reason <reason code, 1-255> 
		location <location type> 
		useLocationValue <disabled | enabled>

Command Parameters

The crankback profile parameters are as shown below:

Command Example

% 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; 
	}