Acme Packet 4600
 
Acme Packet 4500
 
Acme Packet 6100
 
Net-Net 3810
 
Net-Net 4250
 
Acme Packet 3820
 
Acme Packet 6300
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Purpose

Details

Normal Call Clear (SIP-SIP) Calls

Failure Scenarios: 4XX-6XX for INVITE.

For Cancel : Call canceling after getting 180

Applies to:

Purpose

 This document explains why Radius Vendor-Specific Attributes for Sip-Status and Acme-Disconnect-Cause are 0's.

Details

These two fields rely on the Reason Header being present in the BYE or CANCEL message.

Here is how the fields are populated based on whether or not there is a Reason Header present:

Normal Call Clear (SIP-SIP) Calls

1. If there is no reason header carried then both "Sip-Status" and "Disconnect-Cause" will be 0
2. If there is a reason header but NO VALUE then we set "Sip-Status" = 200 and "Disconnect-Cause"= 16
3. If there is a reason header and VALUE for Q.850 then we set "Disconnect-Cause"= value carried in the header.

"Sip-Status" = 0 -----------------> Setting sip status to 0 make sense as this mostly will be interworking call.

Failure Scenarios: 4XX-6XX for INVITE.

1. "Disconnect-Cause" will be set to the value carried in Reason header of error response for INVITE.
2. If there is no Reason header in 4XX-6XX, then value of "Sip-Status" is mapped to "Disconnect-Cause".
   
   

For Cancel : Call canceling after getting 180

1. "Disconnect-Cause" will be set to the value carried in Reason header of CANCEL request.
2. If there is no Reason header in CANCEL, then sip status for invite response(mostly 487) is mapped to acme disconnect cause.

This solution has no attachment