In this section:

Related articles:

 

This object creates a Call Crankback Profile. This profile is a table of call release codes that cause the SBC 5000 series to attempt to reroute (or "crankback") the call when a matching code is returned by Egress Signaling.

The Call Crankback Profile contains the call release codes that automatically cause the SBC 5000 series software to attempt to reroute the call. Additional release codes may be added to the table. Any release code that is in the table, including any default code, may be removed from the table.

Removing a release code from the table causes the SBC 5000 series software to return that release code to Ingress Signaling rather than attempting to reroute the call.

To View Crankback Profile

On SBC main screen, go to Configuration > Profile Management > Category: Call Routing Profiles > Crankback Profile. The Crankback Profile window is displayed.

Security Configuration - Crankback Profile

 

To Edit Crankback Profile

To edit any of the Crankback Profile in the list, click the radio button next to the specific Crankback Profile name.

Security Configuration - Crankback Profile Highlighted

The Edit Selected Crankback Profile window is displayed below.

Security Configuration - Crankback Profile Edit Window

 

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

To Create Crankback Profile

To create a new Crankback Profile, click New Crankback Profile tab on the Crankback Profile List panel.

Security Configuration - Crankback Profile Fields

 

The Create New Crankback Profile window is displayed.

Security Configuration - Crankback Profile Create Window

 

The following fields are displayed:

Crankback Profile

Parameter

Description

Name

The name of the Call Crankback Profile, or the table of call release codes that cause crankback by the SBC 5000 series software. Must be 1-23 characters.

Late Crankback

Specifies whether to allow crankback after an ALERTING, PROCEEDING, or equivalent message (backwards call message) has been received from the egress network:
• enabled—allow crankback after a backwards call message is received from the egress network.
• disabled (default)—do not allow any crankback after a backwards call message is received from the egress network.

Attempt Record
Generation

Specifies whether the SBC 5000 series should generate an ATTEMPT accounting record whenever a call is rerouted (cranked back):
• enabled—generate an ATTEMPT record when a call is rerouted by the SBC 5000 series.
• disabled (default)—do not generate an ATTEMPT record when a call is rerouted by the SBC 5000 series.

To Delete Crankback Profile

To delete any of the created Crankback Profile, click the radio button next to the specific Crankback Profile which you want to delete.

Security Configuration - Crankback Profile Highlighted

Click Delete at the end of the highlighted row. A delete confirmation message appears seeking your decision.

Security Configuration - Crankback Profile Delete Confirmation

 

Click Yes to remove the specific Crankback Profile from the list.

 

Notes on Using Crankback for DNS
  • dnsCrankback needs to be enabled on the egress sipTrunkGroup.
  • The crankbackProfile assigned to the egress sipTrunkGroup is used for DNS crankback.
  • The  SBC maps the received SIP response from the egress call leg using the sipToCpcCauseMapProfile from the egress sipTrunkGroup. The CPC cause is then looked up in the egress sipTrunkGroup's crankbackProfile.
    • If a match is found, the SBC attempts a new target.
    • If a match is not found, SBC skips the DNS crankback and proceeds with the normal crankback at CC level using the ingress sipTrunkGroup's crankback profile

  • No labels