Lucent Technologies PacketStar PSAX, User Manual, Page: 312 / 405

255-700-243 B-3
PacketStar
®
PSAX 12-Port Medium-Density DS1 Multiservice Module User Guide , Issue 1 Release 8.0
Appendix B Reference Information
SPVC Connection Cause Codes Table for Connection Retry
This traffic descriptor uses the parameters two buckets, tagging, CLP=0+1
cells (high and low priority) for bucket 1, and CLP=0 cells (high priority)
for bucket 2. For bucket 1, the Multiservice Media Gateway ignores the
CLP bit value for cells passing into bucket 1 and drops all cells violating the
value set for the PCR. For bucket 2, the system takes one of the following
actions:
~
When the connection is configured for variable bit rate (VBR) traffic, the
Multiservice Media Gateway tags all CLP=0 cells violating the value set
for the SCR to CLP=1 in bucket 2.
~ When the connection is configured for constant bit rate (CBR) traffic, the
Multiservice Media Gateway tags all CLP=0 cells violating the value set
for the PCR to CLP=1 in bucket 2.
The network then might drop some or all cells during congestion.
SPVC Connection Cause Codes Table for Connection Retry
SPVC connection cause codes, displayed in the Last Rls Cause field on all the
SPVC connection configuration windows, are provided in Table B-1. The
word Yes in the “Prompts a Retry” column indicates that if the cause code
number, shown in the “Cause Code” column, is reported by the equipment at
the far (remote) end, the PSAX system will try to establish the connection
again up to the number of times specified in the Retry Limit field on the
SPVC connection configuration windows. The ATM Forum UNI and Frame
Relay Forum FRF.4 standards use many (but not all) of the same cause codes,
and these standards reference ITU-T standards for many of the cause codes.
Table B-1. Connection Cause Codes for SPVCs
Cause
Code
Description
Prompts
a Retry
Referenced
Standard
1 Unallocated (unassigned) number. The called party number is
not currently assigned. As a result, the called party cannot be
reached. No ITU-T Q.850
2 No route to specified transit network. The equipment sending
this cause code received a request to route the call through an
unknown transit network. The transit network is unknown
to the equipment because it does not exist or does not serve
the equipment. No ITU-T Q.850
3 No route to destination. The network through which the call
was routed does not serve the destination. As a result, the
called party cannot be reached. Yes ITU-T Q.850
10 VCC is unacceptable. The VPI/VCI is unacceptable to the
sending entity for use in the call. No ATM Forum UNI
3.0/3.1
16 Normal call clearing. No ITU-T Q.850
17 User is busy. The called party is unable to accept another call
because the user-busy condition has been encountered. Yes ITU-T Q.850
18 No user is responding. A called party did not respond to a call
establishment message with either an alerting or connect
indication within a designated time period. No ITU-T Q.850