Appendix C Reference Information
SPVC Connection Cause Codes for Connection Retry
C-4
255-700-447
PacketStar
®
PSAX 2300 Multiservice Media Gateway User Guide
, Issue 1
Release 9.0.0
SPVC Connection Cause Codes for Connection Retry
The SPVC connection release cause codes, displayed in the Last Rls Cause
field on all the SPVC connection configuration windows, are provided in
Table C-2. 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
23N34
21-Port High-Density E1
IMA
Yes
UPC, AQueMan
AQueMan
‡
,
EPD
**
23N33
12-Port Medium-Density
DS1 IMA
Yes
UPC, AQueMan
AQueMan
‡
,
EPD
**
20N33
6-Port DS1 IMA
20N34
6-Port E1 IMA
20N36
6-Port Enhanced DS1/T1
Multiservice
20N56
6-Port Enhanced E1
Multiservice
Yes
AQueMan
AQueMan
‡
,
EPD
**
23N64
12-Port Medium-Density
DS1 Multiservice
Yes
UPC, AQueMan
AQueMan,
EPD
23N66
21-Port High-Density E1
Multiservice
Yes
UPC, AQueMan
AQueMan,
EPD
23N07
Quadserial
Yes
¶¶
UPC, AQueMan
AQueMan,
EPD
20N07
6-Port Multiserial
Yes
¶¶
AQueMan
AQueMan,
EPD
*
This column indicates whether buffer space is shared on modules with more than one I/O port.
†
The traffic processing option order listed in this column indicates the processing order performed on the
traffic.
‡
See the Quality of Service tables in the Reference Information appendix for more information on the
AQueMan algorithm implementation.
§
The term TM4.1 refers to af-tm-0021.000, Traffic Management 4.1. This standard for priority queuing
applies to the newest PSAX modules that run at high speed. Further options are available to users within
this standard for Virtual Interfaces (see Section 4.2.2.4), traffic shaping for user-defined VCs, and the
early packet discard (EPD) function.
¶
VI support and per VC traffic shaping are not supported at the same time on the same egress path on an
ATM interface. Either one or the other is supported on the same egress path.
**
EPD is automatically enabled on modules for AAL5 service only.
††
On the OC-3c 1+1 APS and STM-1 1+1 MSP modules, users have two choices: 1) AQueMan egress pro-
cessing with UPC and Virtual Interfaces, or 2) VCs can be user-defined for traffic shaping.
‡‡
On older modules , AQueMan egress processing is used.
§§
These modules do not have separate buffers per port. All other modules have separate buffers per port
except the 1-port modules.
¶¶
RS232, RS449, EIA530, V.11.
Table C-1. Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces
ATM Interface Modules
Interport
Shared
Buffer
*
Ingress Traffic
Processing Priority
Queuing
†
Egress Traffic Processing
Priority Queuing
†