SIP Release Codes and Causes

The CDR Diagnostic contains the following fields, among others:

  1. Release Code: SIP code

  2. Release Cause: the reason for a release code

Release Causes

Release Causes are local to 46 Labs and can come from either the Traffic Switch or the Traffic Manager.

From the Traffic Switch:

SIP Code / Release Code

Release Cause

Description

(18X/2XX)

BLOCK_SDP_RFC1918_IP

Blocked due to use of a private IP. (i.e. can't reach internet)

(18X/2XX)

BLOCK_SDP_ORIG_WRONG_PORT

Blocked due to customer's port not matching the trunk group port. (For example: TG is set up for 5060, customer set up for 5061)

(18X/2XX)

BLOCK_SDP_TERM_WRONG_PORT

Blocked due to vendor's port not matching the trunk group port. (For example: TG is set up for 5060, vendor set up for 5061)

(18X/2XX)

BLOCK_SDP_HAS_NO_CODECS

Blocked due to the sending party sending signaling with no codec identified in the SDP.

(200)

BLOCK_CANCEL_AFTER_200

The customer's party canceled the call after the 200 OK. (i.e. race condition)

(200)

NORMAL_CLEARING

Normal/good call.

(200)

HANGUP_BY_SUSPENSION

Call hungup due to the Trunk Group Balance/Payment "Kill Calls on Suspension" feature.

(403)

VENDOR_403

The owner of number does not have the TF/DID programmed into the switch. (i.e. downstream vendor 403)

(404)

VENDOR_404

The vendor is indictating that the number is not valid.

(408)

LOCAL_PDD_TIMEOUT

PDD timed out before the call was able to connect between vendors.

(408)

PDD_TIMEOUT

PDD timed out.

(408)

REMOTE_PDD_TIMEOUT

PDD timeout returned by a vendor. (i.e. exceeded their PDD)

(428)

VENDOR_428

The server policy requires an Identity header and one has not been provided.

(436)

VENDOR_436

Bad Identity-Info - The request has an Identity-Info header, and the URI scheme in that header cannot be dereferenced.

(437)

VENDOR_437

Unsupported Certificate - The server was unable to validate a certificate for the domain that signed the request.

(438)

VENDOR_438

Invalid Identity Header - The server obtained a valid certificate that the request claimed was used to sign the request, but was unable to verify that signature.

(484)

ADDRESS_INCOMPLETE

Request-URI is incomplete. (i.e. the number is not formatted correctly)

(486)

NUMBER_BUSY

The callee is busy.

(487)

ORIGINATOR_CANCEL

The request has terminated by bye.

(487)

200_AFTER_CANCEL

The request has terminated by cancel.

(4XX/5XX/6XX)

ROUTE_REJECT

The call details state a rejection/404/etc in or during routing.

(4XX/5XX/6XX)

CARRIER_REJECT

An intermediary machine or process rejected the call attempt. This contrasts with the 607 (Unwanted) SIP response code in which the called party rejected the call. The response may include the contact entities that blocked the call in Call-Info header containing. This provides a remediation mechanism for legal callers that find their calls blocked.

(500)

NO_OUT_SOCKET

The IP assigned is not available.

(503)

CALL_FAILURE

A server is undergoing maintenance or is temporarily overloaded and so cannot process the request. A "Retry-After" header field may specify when the client may reattempt its request. (i.e. service unavailable)

(504)

VENDOR_504

The server attempted to access another server in attempting to process the request, and did not receive a prompt response. (i.e. server timeout)

(607)

VENDOR_607

Unwanted - The called party did not want this call from the calling party. Future attempts from the calling party are likely to be similarly rejected.

(608)

VENDOR_608

Rejected - An intermediary machine or process rejected the call attempt. This contrasts with the 607 (Unwanted) SIP response code in which the called party rejected the call. The response may include the contact entities that blocked the call in Call-Info header containing. This provides a remediation mechanism for legal callers that find their calls blocked.

 

From the Traffic Manager:

SIP Code / Release Code

Release Cause

Description

(Depends on what the user will choose)

ANI_GLOBAL_BLOCK

The call is violating an ANI Global Block list rule.

(Depends on what the user will choose)

ANI_ROUTEPLAN_BLOCK

The call is violating an ANI Routeplan Block list rule.

(Depends on what the user will choose)

DNIS_GLOBAL_BLOCK

The call is violating a DNIS Global Block list rule.

(Depends on what the user will choose)

DNIS_ROUTEPLAN_BLOCK

The call is violating a DNIS Routeplan Block list rule.

(Depends on what the user will choose)

MEDIAIP_GLOBAL_BLOCK

The call is violating a Media IP Global Block list rule.

(Depends on what the user will choose)

MEDIAIP_ROUTEPLAN_BLOCK

The call is violating a Media IP Routeplan Block list rule.

(Depends on what the user will choose)

404_GLOBAL_BLOCK

The call is violating a 404 Global Block list rule.

(Depends on what the user will choose)

404_ROUTEPLAN_BLOCK

The call is violating a 404 Routeplan Block list rule.

(Depends on what the user will choose)

EX_ROUTING_BLOCK

The call is violating a (external) block list rule.

(503)

ISUP_OLI_BLOCK

ISUP-OLI block (to block payphones)

(503)

ANI_SD_BLOCK

Blocked due to the "Short Duration" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

ANI_487_BLOCK

Blocked due to the "487" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

ANI_PRV_BLOCK

Blocked due to the "ANI PRV" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

ANI_BLOCK_ACD

Blocked due to the "Minimum ANI ACD" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

ANI_BLOCK_ASR

Blocked due to the "Minimum ANI ASR" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

DEST_PRV_BLOCK

Blocked due to the "Dest. PRV" Intelligent Filter found in Routeplan Options. (Relationship > Routing > Create > Intelligent Filters)

(503)

NO_CUSTOMER_DECK

There is no ratedeck assigned to customer trunk group.

(503)

NO_VENDOR_DECK

There is no ratedeck assigned to vendor trunk group.

(503)

EMPTY_TG_LIST

There are no assigned IPs in the trunk group.

(503)

MAX_RATE

Due to exceeding amount entered into the Maximum Rate field found in Routeplan Options. (Relationship > Routing > Create)

(503)

NEPR

The call failed due to not having enough profitable routes.

(503)

LERG_NOT_FOUND

The switch is unable to find the NPANXX in the LERG.

 

Release Code/SIP Code

Similar to HTTP, SIP (Session Initiation Protocol) is based on request and response transactions. Every transaction consists of a SIP request and (at least) one SIP response. For more information, please refer directly to RFC 3621 or the assignment list from the Internet Assigned Numbers Authority (IANA).