-
Cisco Voice Switch Service Module (VXSM) Configuration Guide, Release 5.2
-
PDF Version of Cisco Voice Switch Service Module (VXSM) Configuration Guide, Release 5.2
-
About this Guide
-
Introduction
-
General Description
-
Configuration for VoIP Switching Applications
-
Configuration for AAL2 Trunking Applications
-
Configuring VXSM Features
-
Loading and Upgrading VXSM Code Images
-
VXSM Troubleshooting
-
Media Gateway Clocking
-
Table Of Contents
Configuration for AAL2 Trunking Applications
Multipurpose Service Module (MPSM) Alternative
Create VXSM Resource Partition
Configuring HDLC Signaling AAL5 Trunks for Nx64 Format
Configuration for AAL2 Trunking Applications
A Cisco MGX 8880 and a Cisco MGX 8850 equipped with VXSMs and functioning as a media gateway can be configured to meet the requirements of an AAL2 trunking applications.
In AAL2 Trunking applications, the voice TDM interface and the packet network interface need to be configured. The trunking application involves VXSM cards, the PXM-45 card, and the AXSM cards. These cards all function together and must be configured accordingly.
VoATM trunking configuration consists of the following tasks.
•
PXM-45 card configuration
•
•
•
Multipurpose Service Module (MPSM) Alternative
This chapter describes procedures in which the interface to the packet network ia and AXSM card. For AAL2 trunking applications (on an MGX 8850 platform only), VXSM can operate in conjunction with a Multiprotocol Service Module (MPSM) in which the MPSM provides the interface to the ATM network. Interworking with the MPSM enables the MGX Voice Gateway to support IMA, ATM and Frame Relay services with channelized capability on DS1 and DS0 levels.
The configuration procedures in this chapter are applicable to MPSM configurations except that the MPSM card must be provisioned instead of the AXSM card. The MPSM card must be configured for ATM context using the MPSM cnfclictx atm command. After the context is set to ATM, provisioning is performed with the upln, addport and addcon command sequence. For more details, please refer to the MPSM user documentation.
Quick Start Procedure
The following table shows a brief overview of the sequence of tasks and commands required to setup the media gateway for a VoATM Trunking application. The same procedure, but in greater detail, is presented later in this chapter.
PXM-45 Card Configuration
Log on to the PXM-45 card and perform the following steps to configure the PXM-45 card for VoATM using the VXSM. The PXM-45 has a large number of commands. These steps deal only with the minimum commands required to setup the MGX 8850 as media gateway.
Step 1
unknown.7.PXM.a > cnfname <node name>Enter up to 32 characters for the new node name, (node name is case-sensitive).
For example:
unknown.7.PXM.a > cnfname gateway1After the user responds Yes to a confirmation request, the name is changed to gateway1
Step 2
gateway1.7.PXM.a > cnfdate <mm/dd/yyyy>Step 3
geteway1.7.PXM.a > cnftmzn <timezone>Step 4
geteway1.7.PXM.a > cnftmznmgt <timeoffsetGMT> Offset can be from -12 to +12.Step 5
geteway1.7.PXM.a > cnftime <hh:mm:ss>Step 6
geteway1.7.PXM.a > addcontroller <cntrlrId> i <cntrlrType> <slot> [cntrlrNamecntrlrId is the controller ID, enter 2 to specify a PNNI controller.
cntrlrType is the controller type, enter 2 to specify a PNNI controller type.
slot is the PXM slot in the MGX 8850, enter 7 or 8 as appropriate.
cntrlrName is an optional controller name, enter a text name is desired.
Step 7
geteway1.7.PXM.a > ipifconfig lnPci0 <IP_Addr><netmask <Mask>Specify the values for the IP address and its associated netmask.
AXSM Card Configuration
Log on to the AXSM card and perform the following steps to configure the AXSM card for VoATM using the VXSM. The AXSM has a large number of commands. These steps deal only with the minimum commands required to setup the MGX 8850 as media gateway.
Step 1
AXSM_SCT.CARD.2.V1
The SCT file must have been ftp'd to the node's PXM-45 disk in the C:SCT/TEMP directory
Use the dspctchksum command to display the checksum value of the file. Note the value of checksum
Note
General link parameters
COSB (Class of Service Buffers) parameters
Virtual circuit threshold parameters
COSB threshold parametersStep 2
Step 3
geteway1.10.AXSM.a > addsct <card type> <sct type> <sct ID> <Maj ver> <chksum>cardtype is the card whose SCT you want to make available to the card by installing the SCT in the appropriate directory. Enter 1 for AXSM
scttype identifies either a port-level or a card-level SCT. Enter 2 for card level.
SCT ID refers to a specific service class template. The SCT is either provided by Cisco or created through CWM. Possible IDs are, Cisco-provided: 1-100 and User-created: 101-255. The default SCT ID is 0.
Maj ver is the major version number of the file. This number is assigned by Cisco.
checksum is the checksum for the file. Use the value obtained from the dspsctchksum command. The value is also published in the relevant release notes.
Step 4
Step 5
Step 6
geteway1.10.AXSM.a > upln <bay.line>For bay, enter 1 if the line on the back card is in the upper bay and enter 2 if it is in the lower bay. For line, enter the back card port number to which the line is connected.
Step 7
geteway1.10.AXSM.a > cnfln -sonet <bay.line> -slt <LineType> -clk <clock source>Enter the bay and line of the line being configured (see upln above). For LineType, enter 1 for SONET or 2 for SDH. For clockSource, enter 1 to use a clock received over the line from a remote node or 2 (the default) to use the local timing defined for the local node.
Step 8
geteway1.10.AXSM.a > addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType>For ifNum, enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. For UNI and NNI ports, you can assign one logical interface per line.
For guaranteedRate and maxRate, enter an OC3 value in the range of 50 to 353207 cells per second.
For ifType, 1 specifies UNI, 2 specifies NNI. For trunking mode, each trunk port should be configured as NNI.
Step 9
geteway1.10.AXSM.a > addpart <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>For ifNum, enter the port number. For partId, enter 1 for PNNI. For cntrlid, enter 2 for PNNI.
The remaining parameters are used to specify maximum and minimum values for vpi/vci, bandwidth, connections, etc., see the Cisco MGX 8850 (PXM45 and PXM1E) Command Reference, Release 5 for details.
VXSM Card Configuration
Log on to the VXSM card and perform the following steps to configure the VXSM card for VoIP. The VXSM has a large number of commands. These steps deal only with the minimum commands required to setup the MGX 8850 as a media gateway
Create VXSM Resource Partition
Step 1
geteway1.5.VXSM.a > addrscprtn <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> <ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>For ifNum, enter 1 for port number. For partId, enter 1 for PNNI. For cntrlid, enter 2 for PNNI.
The remaining parameters are used to specify maximum and minimum values for vpi/vci, bandwidth, connections, etc., see the Cisco MGX 8850 (PXM45 and PXM1E) Command Reference, Release 5 for details.
Configuring the TDM Interface
Identifying Voice Circuits
The OC-3, 48 T1/E1, and 3 T3/E3 versions of the VXSM cards, support a variety of multiplexing schemes for interfacing to voice circuits. These schemes fall into four major categories:
•
•
•
•
Many of the VXSM commands require the user to specify a line, a single voice circuit, or a group of voice circuits. The following paragraphs describe how these items are specified for the different multiplexing schemes.
OC-3 Systems
Specifying a DS0 stream from the highly multiplexed bit stream of OC3 is performed using the relationships (paths) shown in Figure 4-1.
Figure 4-1 OC-3 Hierarchical Relationship
The bit stream interfaces with VXSM via one of the four physical lines in the OC3 back card. This interface is usually in the upper bay (but, when a redundant back card is used and is active, it is in the lower bay).
For a particular line, the OC3 stream consists of three paths and, depending upon the format, a path consists of either 7 virtual tributary groups (vtg) or 28 DS1s. A vtg can be further divided into either four virtual tributaries (version 1.5) or three virtual tributaries (version 2.0). The DS1 and the virtual tributaries (vt) consist of 24 T1 DS0s for T1 or 31 DS0s for E1.
As shown in the diagram, the relationship between DS0s and physical ports can take one of three paths. The paths are common between the physical line and STS-1 level. From the STS-1 level to the DS0, one of three paths can be taken.
The path that a particular DS1/DS0 will use can be configured by the user with the -payload parameter in the cnfpath -sts command. This parameter can be set to:
•
•
•
Note
Using the system described above, DS1 paths in VXSM commands are formatted as follows:
•
The DS1 is specified as: bay.line.path.vtg.vt
bay = upper of lower bay of the VXSM backcard.
line = the line number on the associated OC-3 card in the range 1 to 4.
path = the path of the virtual tributary in the range 1 to 3.
vtg = the virtual tributary groups applicable to the connection in the range 1 to 7.
vt = virtual tributaries in the range 1 to 4 for vt1.5 or 1 to 3 for vt2.0.
Caution
vtg = the virtual tributary group.
vt = virtual tributary
•
The DS1 is specified as: bay.line.path.ds3.DS1
bay = upper of lower bay of the VXSM backcard.
line = the line number on the associated OC-3 card in the range 1 to 4.
ds3 = the SONET (STS-1) path payload type as ds3 in the range 1 to 3.
ds1 = the ds1 channel within the ds3 interface in the range 1 to 28.SDH Systems
The VXSM- 155 card supports voice circuits that are multiplexed according to the Synchronous Digital Hierarchy (SDH) standard. Each OC- 3 line presents the data stream as a 155.52 Mbps Synchronous Transport Module (STM-1).
Figure 4-2 shows the multiplexing paths between STM-1 at the physical line and the T1 or E1 voice circuits.
When using the SDH interface, the user must configure the path using the cnfpath -sts command. The format of this command is:
cnfpath -sts <bay.line.path> [-payload <Path Payload>] [-tm <Tributary Mapping Type>]
[-tg <Tributary Grouping>] [-txtrace <Transmit Trace>] [-extrace <Expect Trace>]<bay.line.path>, specifies the bay (upper of lower back card), the physical line number on the back card, the path number between the STM and the AU (1, 2, or 3 for AU-3, 1 for AU-4)
-payload <Path Payload>, specifies the TU/VC combination (TU-11/VC-11 for T1 or TU-12/VC-12 for E1).
-tm<Tributary Mapping Type>, specifies the mapping mode, 1 = asynchronous mode or 2 = byteSynchronous mode.
-tg <Tributary Grouping>, specifies the tributary grouping This is a choice between AU-3 (the default) or AU-4.
2 = au3Grouping—Applicable to SDH interfaces: STM1, -AU-3, -TUG-2, -TU-12, -VC12 or STM1, -AU-3, -TUG-2, -TU-11, -VC11.
3 = au4Grouping—Applicable to SDH interfaces: STM1, -AU-4, -TUG-3, -TUG-2, -TU-12, -VC12 or STM1, -AU-4, -TUG-3, -TUG-2, -TU-11, -VC11.Figure 4-2 SDH Hierarchical Relationships
T1/E1 Systems
In T1/E1 systems, the front card supports up to 48 T1 or E1 lines. The back card supports up to 24 T1 or E1 lines. Depending upon the number of lines to be supported, one or two half high back cards are configured with a single front card; one in the upper or lower bay and the other (if configured) in the remaining open bay.
A physical line or a DS1 service is specified simply as:
bay.linewhere:
bay = 1 or 2—1 for the upper bay, 2 for the lower bay.line = 1 - 24—The physical T1 line on the backcard in the range 1 to 24.
If the command requires the interface to be further specified down to the DS0 level, the DS0 is specified as:
bay.line ds0grpwhere:
ds0grp = 0 - 24 or 31 — The DS0 group in the range of 0 to 23 for T1 or 0 to 30 for E1.
T3.E3 Systems
In T3/E3 systems, the front card supports up to 6 T3 or E3 lines. The back card supports up to 3 T3 or E3 lines. Depending upon the number of lines to be supported, one or two half high back cards are configured with a single front card; one in the upper or lower bay and other (if configured) in the remaining open bay.
A DS1 is specified simply as:
bay.line.pathwhere:
bay = 1 or 2—1 for the upper bay, 2 for the lower bay.line = 1 - 3—The physical T3 line on the backcard in the range 1 to 3
path = 1 - 28—The DS1 circuit in the T3 line in the range of 1 to 28
If the command requires the interface to be specified down to the DS0 level, the DS0 is specified as:
bay.line.path ds0grpwhere:
ds0grp = 0 - 24 or 31 — The DS0 group in the range of 0 to 23 for T1 or 0 to 30 for E1.
Note
Voice Interfaces (VIF)
A voice interface (vif) is a user configurable set of parameters that is applied to a group of ds0s within a ds1. The configuration settings of the vif are used by the digital signal processors (DSPs) to determine how a voice payload is to be processed by VXSM.
A voice interface is created using the addvif command. With this command the user specifies a vif number and its associated ds1, in addition, the type of signaling, the type of service (H.248 switching, trunking, etc.). Other bearer channel parameters such as echo cancellation and voice activity detection, are also specified. These parameters are contained within a vif which, when the vif is added, are assigned default values.
Once a vif is created, its parameters can be discovered using the dspvif command. There are also display and configure commands for the user to see and configure the various parameters.
An example of the addvif and dspvif commands is as follows:
The following command sequence adds a voice interface in a DS1 path for the VXSM card in slot 3 of the media gateway and then displays the results:
M8850_NY.3.VXSM.a > addvif 1.1.1.1.1 0 24 9 250M8850_NY.3.VXSM.a > dspvif 1.1.1.1.1 0======================================================Configuration of DS0 Group in DS1======================================================DS1 Line : 1.1.1.1.1DS0 Group : 0Service Type : h248DS0 Bit Map : 24To configure a vif perform the following steps.
Step 1
Step 2
dspvif [<bay.line.path.vtg.vt >] | [<bay.line.path.ds3.ds1>] <ds0GroupId> for OC-3
dspvif <bay.line> <ds0GroupId> for 48 T1/E1
dspvifterms
dspvifterm [< bay.line.path.vtg.vt >] | [<bay.line.path.ds3.ds1>] <ds0GroupId> for OC-3
dspvifterm <bay.line> <ds0GroupId> for 48 T1/E1
dspvifparam <bay.line> <ds0GroupId> for 48 T1/E1
dspvifparams
Step 3
cnfvifparam <specified ds!> <ds0GroupId> <NoiseRegEnable> <NonLinearProcEnable> <MusicOnHoldThreshold> <ModemPassThru> <UpspeedCodec> <Repetition>
cnfvifterm <specified ds!> <ds0GroupId> <gatewayLinkId> <packageIds> <profileId>(Only applicable when service is H.248)
See the chapters entitled VXSM Commands for a description of the commands listed in steps 2 and 3.
Configuring the TDM Lines
Use the following steps to configure the TDM lines on the VXSM.
Step 1
cnfpath -sts<bay.line.path>[-payload <PathPayload>][-tm <TributaryMappingType>][-tg <TributaryGroupingType>][-txtrace <PathTraceToTransmit>][-exptrace <PathTraceToExpect]
<bay.line.path>
bay: 1
line: 1 - 4
path: 1 - 3 or 1 (AU4 only)
[-payload <PathPayload>]
3 - ds3
4 - vt15vc11
5 - vt20vc12
[-tm <TributaryMappingType>]
1 - asynchronous
2 - byteSynchronous (NA for ds3)
[-tg <TributaryGroupingType>]
1 - notApplicable (Sonet)
2 - au3Grouping (SDH)
3 - au4Grouping (SDH)
[-txtrace <PathTraceToTransmit>]
trace-string: size 16(SDH) or 64(Sonet)
[-exptrace <PathTraceToExpect]
trace-string: size 16(SDH) or 64(Sonet)
Step 2
geteway1.5.VXSM.a > upln <bay.line>For bay, enter 1 for upper bay or 2 for uper bay.
For line, enter a value in the range 1 - 4 for OC3 or 1 - 24 for 48T1/E1.
Step 3
geteway1.5.VXSM.a > uppath -sts<bay.line.path>For bay, enter 1 for upper bay or 2 for lower bay.
For line, enter a value between 1 and 4 to indicate the physical OC3 interface on the back card.
For path, enter a value between 1 and 3 to indicate the DS3 path within the OC3 interface.
Step 4
geteway1.5.VXSM.a > uppath -ds1<bay.line.path.vtg/ds3.vt/ds1>For bay, enter 1 for upper bay or 2 for upper bay.
For line, enter a value between 1 and 4 to indicate the physical OC3 interface on the back card.
For path, enter a value between 1 and 3 to indicate the DS3 path within the OC3 interface.
Note
vt = virtual tributariesStep 5
For OC3 cards, the syntax of this command is:
addvif <LineNum> <Ds0GrpIndex> <Ds0BitMap> <ServiceType><BulkProvisionNumber>
Where:
LineNum -- (bay.line.path.vtg.vt or bay.line.path.ds1)
bay {1 - upper}
line (range=1..4)
path (range=1..3)
vtg (range=1..7)
vt (range=1..4)(ds1) (range=1..3)(e1)
ds1 (range=1..28)
Ds0GrpIndex -- DS0 group index
T1: (range=0..23)
E1: (range=0..30)
Ds0BitMap -- DS0 channel number
For trunkingService or DS0Xconn: single bit input
For H248: multiple bits input (e.g. 1-24 or 1,5,10-20)
T1: 1,2,3,...,24
E1: 1,2,3,...,31
ServiceType -- service type
8 - Trunking
9 - H248
10 - DS0Xconn
BulkProvisionNumber -- bulk provisioning number
Single DS0 configuration (range=1..8064(OC3)/1152(T1)/1488(E1))(default=1)
Multiple DS0 configuration (range=1..336(OC3)/48(T1E1))(default=1)
For 48T1/E1 cards the syntax of this command is the same as for OC3 except that the LineNumparameter is expressed as:
LineNum -- (bay.line)
bay {1 - upper}
line (range=1..24)
Creating VXSM Trunks
In trunking non-switching applications, an AAL2 PVC connection needs to be created for each bearer trunk to be supported. In addition, provision must be made for transporting signaling information across the network. HDLC signaling is transported using separate AAL5 PVCs; SS7 signaling is carried in the AAL2 PVC using the AAL2 custom profile of 200. All these connections extend between the VXSM cards at the local and remote endpoints of the trunk.
Creating a Trunk Connection
To make connections between a local VXSM and a remote VXSM card, perform the following procedure. This procedure should be performed for each trunk to be supported by the media gateway Each trunk requires a PVC for a bearer circuit and, if used, a separate PVC for signaling.
Two connections types can to be created.
•
•
For each connection, select one end of the trunk as the slave and the other end as the master.
Step 1
geteway1.5.VXSM.a > addcon <ifNum> <vpi> <vci> <serviceType> <pvcType> <application> <mastership> [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>] [-rscr <remote PCR>] [-lmbs <local MBS>]......For ifNum specify 1 as the interface number. For vpi and vci specify values in the ranges 0 to 255 and 0 to 65535 respectively. For service type, specify 1 (constant bit rate) or 2 (vbr-rt).
For pvc type, specify 1 (AAL5) if the connection is for CCS signaling or specify 2 (AAL2) if the connection is for bearer.
For application specify 3 for a CCS signaling connection or 2 for a bearer connection.
For mastership specify 2 for slave.
Omit the - slave parameter. The gateway will assign a value and display it as NSAP.VPI.VCI. The user should note the value and use it when adding the master end of the connection on the AXSM.
Of the remaining optional parameters, enter values or accept the defaults. These parameters are best set from the master end. See the CLI chapter for details.
Step 2
geteway1.5.VXSM.a > addcon <ifNum> <vpi> <vci> <serviceType> <pvcType> <application> <mastership> [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>] [-rscr <remote PCR>] [-lmbs <local MBS>]......For ifNum, specify 1 as the interface number. For vpi and vci specify values in the ranges 0 to 255 and 0 to 65535 respectively. For service type, specify 1 (constant bit rate) or 2 (vbr-rt).
For mastership, specify 1 for master.
For the -slave parameter, enter the NSAP.VPI.VCI that was noted when configuring the slave end of the connection.
Of the remaining optional parameters, enter values or accept the defaults. See the CLI chapter for details.
Step 3
Step 4
The port must be down to use this command. When a port is first created, its administrative state is down, in which there is no need to down it. If the port is up, do the following:
1.
2.
3.
Use the cnfpnportsig command to configure the port as signaling NNI.
The syntax of this command is:
cnfpnportsig <portid> [-univer {uni30 | uni31 | uni40 | q2931 | none | self}] [-nniver {iisp30 | iisp31 | pnni10 | enni | aini}] [-unitype {public | private}] [-addrplan {both | aesa | e164}] [-side {user | network}] [-vpi <vpi>] [-sigvci signalling-vci] [-rccvci routing-vci] [-cntlvc {ip}] [-passalongcap {enable | disable}] [-hopcntgen {enable | disable}] [-vpivcialloc {enable | disable}] [-svcroutingpri <priority>]
The configuration of the port can be checked by using the dsppnportsig command.
M8850_NY.7.PXM.a > dsppnport 1:2.1:1Port: 1:2.1:1 Logical ID: 16848897IF status: up Admin Status: upUCSM: enableAuto-config: enable Addrs-reg: enableIF-side: network IF-type: nniUniType: private Version: pnni10PassAlongCapab: n/aInput filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 200minSvccVci: 35 maxSvccVci: 255minSvpcVpi: 1 maxSvpcVpi: 200#SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive:p2p : 0 0 0 0p2mp: 0 0 0 0#Svcc: #Svpc: Total:p2p : 0 0 0p2mp: 0 0 0Total: 0
Configuring AAL2 Trunks
When an AAL2 bearer trunk has been established, it can be configured further using the following commands.
CIDs
Each voice channel must be assigned a channel identifier (CID) for transport across the AAL2 trunk.
Note
Use the addcid command to create a CID and associate it with a ds1/ds0 voice stream. For OC3 cards, the format of this command is:
addcid <ifIndex> <VPI> <VCI> <CID> <bay.line> <Ds1PathIndex> <Ds0 Group Index> <Profile Type><Profile Number> <Voice Codec> <VBD Codec><Repetition>For T1/E1 systems the format of this command is:
addcid <ifIndex> <VPI> <VCI> <CID> <bay.line.> <Ds0_Group_Index> <Profile_Type> <Profile_Number> <Voice_Codec> <VBD_Codec><Repertition>The vpi and vci parameters must be the vpi and vci of the AAL2 PVC. The CID must be a value between 8 and 255. The vci.vpi,CID combination, uniquely defines a channel in a specified PVC and associates it with a specified ds1/ds0 voice channel.
Profile Type
This parameter specifies the ATM AAL2 profile type for the AAL2 CID.The valid values are as follows:
1 = ITU
2 = CustomProfile Number
This parameter specifies the ATM AAL2 profile number for the AAL2 CID.The valid value are as follows:
For the ITU profile type—1, 2, 3, 7, and 8.
For custom profile type—100. 101, 110, and 200.When the AAL2 connection is used to transport SS7 signaling, select profile type 200.
Voice Codec
This parameter specifies the voice codec used for an AAL2 voice trunking connection.The valid values are:
2 = G.729a
3 = G.726-16
4 = G.726-24
5 = G.726-32
6 = G.711u
7 = G.711a
13 = G.729ab
18 = Clear channel
19 = G.726-40When the AAL2 connection is used to transport SS7 signaling, select 2 = Clear channel.
VBD Codec
This parameter specifies the voice band data codec used in an AAL2 voice trunking connection.The valid values are:
1 = None (default)
2 = G726r32k
3 = G726r40k
4 = G711u
5 = G711aRepetition
Once a CID has been created, it can be reconfigured using the cnfcid command.
For the VXSM OC3 card:
cnfcid <ifIndex> <VPI> <VCI> <CID> <Profile Type> <Profile Number> <Voice Codec>
<VBD Codec>For the VXSM T1/E1 card:
cnfcid <ifIndex> <VPI> <VCI> <CID> <Profile Type> <Profile Number> <Voice Codec> <VBD Codec>
Subcell Multiplexing
With subcell multiplexing, a partially filled cell can be filled with data from another CID. This makes a more efficient use of the bandwidth of the PVC. The partially filled cell is delayed for this purpose but only for a specified period. When the period is up and the cell is still partially filled, it is sent unfilled.
Use the -ctimer parameter in the addcon or cnfcon command to specify the period that an unfilled cell will wait before being transmitted. The wait period is in the range 0 to 50. Configuring the subcell multiplexing feature must be performed before adding CIDs to the connection.
Upspeed
VXSM supports detection of FAX and Modem devices attached to the TDM (trunk) side. The following tones are supported:
•
•
VXSM uses the standard "User state control packets" indicating the change to voiceband data (VBD). The User state control packets are sent as type 3 packets with triple redundancy.
Upon detection of a modem or FAX tone, the master end of the connection performs a CAC check. If successful, it upspeeds to a less complex codec (for example, G.711) to accommodate the voiceband data.
Note that the CAC is performed by the master end of the connection (the CAC-Master). The CAC-Master is specified by the user in the addcon command using the -cmaster parameter.
The upspeed codec is specified in addcid command using the VBD_codec parameter.
Configuring HDLC Signaling AAL5 Trunks for Nx64 Format
In trunking mode the HDLC signaling is transferred across the network as AAL5 connections. If the HDLC data stream conforms to an Nx64 format, the required configuration involves the following steps.
Step 1
addnx64prof <profile_index>[<Nx64TransportMode>][<Nx64FrameFillPattern>][<InterFrameGapFlagCount>]
[<Nx64BitInversion>]<profile_index>
Specify an index number that uniquely identifies a Nx64 profile entry.
The first entry (i.e., the value of this object is one) is used for default profile, it can not be modified or deleted.
The value for this parameter is a number in the range 2 - 65535.
[<Nx64TransportMode>]
Specify the Nx64 packet stream transport mode as HDLC.
1 = hdlc (the Nx64 data the gateway receives are HDLC frames);
2 = transparent (the Nx64 data the gateway receives are unstructured bit stream and they will be transmitted to the network transparently).
[<Nx64FrameFillPattern>]
Specify the Nx64 HDLC frame start/end fill pattern.
1 = hdlcPattern (specifies 0x7E HDLC frame start/end bit pattern)
2 = iDlePattern (specifies 0xFF IDLE bit pattern)
This parameter is applicable only when the transport mode is set to 'hdlc'.
[<InterFrameGapFlagCount>]
Specify the HDLC inter-frame gap flag count.
A value of '0' means that only one flag is transmitted between a pair of frames and it is shared by them. In this case, the inter-frame flag is the start flag for frame (m) and the end flag for frame (m+1).
This object is only applicable when the transport mode is configured as 'hdlc', otherwise, the value of this object is ignored.
The valid value for this parameter is a number in the range from 0 - 15.
[<Nx64BitInversion>]
Specify whether or not bit inversion is turned on to support inverted HDLC functionality.
When this parameter is set to 'true', all the data stream on the Nx64 link is bit inverted
1 = true
2 = false.Step 2
addnx64aal5 <port><vpi><vci><bay.line.path.vtg/ds3.vt/ds1><ds0_group_number><nx64_profile>
<port><vpi><vci><bay.line.path.vtg/ds3.vt/ds1>
These parameters identify the individual AAL 5 connection to be configured.
<port.>
This parameter is used to specify the port number of the Nx64 AAL5 entry.
The valid value for this parameter is the number 1.
<vpi><vci>
Specify the AAL5 connection to be configured. The vpi is a number in the range 1 - 255. The vci is a number in the range 1 - 65535.
<bay.line.path.vtg/ds3.vt/ds1>
Specify the DS0 path identifier to be used in adding a Nx64 AAL5 entry for the VXSM OC-3 card.
The valid values of this construct and their meaning are as follows:
bay = 1—Designates the VXSM OC-3 card in the upper bay.
line = 1 - 4—Line number. Specifies one of four possible working lines for the OC-3 interface.
path = 1 - 3—Path identification number. Specifies the path identifier for the following path payload type:vt1.5 payload—For T1 interface.
vt2.0 payload—For E1 interface.
Note
vtg/ds3 = 1 - 7—Virtual tributary group or 1 for ds3 path identification number.
vt/ds1 = 1 - 4—Virtual tributary or ds1 path identification number, as follows:vt = 1 - 4—For T1 interface.
vt = 1 - 3—For E1 interface.
ds1 = 1—28.ds0= 1 - 24 (T1)/1 - 31(E1)Specifies the DS0 path identifier to be used in adding a Nx64 AAL5 entry for the VXSM OC-3 card.
The valid values of this construct and their meaning are as follows:
bay = 1—Designates the VXSM OC-3 card in the upper bay.
line = 1 - 4—Line number. Specifies one of four possible working lines for the OC-3 interface.
path = 1 - 3—Path identification number. Specifies the path identifier for the following path payload type:vt1.5 payload—For T1 interface.
vt2.0 payload—For E1 interface.
Note
vtg = 1 - 7—Virtual tributary group path identification number.
vt = 1 - 4—Virtual tributary path identification number, as follows:vt = 1 - 4—For T1 interface.
vt = 1 - 3—For E1 interface.ds0= 1 - 24 (T1)/1 - 31(E1)
<ds0_group_number>
Specify a number that uniquely identifies a DS0 group containing one or more DS0 that connect to an AAL5 trunking connection.
This object is mandatory when adding an AAL5 entry. Once an AAL5 entry is added, this object can not be modified.
The valid value for this parameter is a number in the range 1 - 31
<nx64_profile>
Specify the Nx64 data profile for an AAL5 trunking connection
The value for this parameter is a number in the range 1 - 65535.
Step 3
Configuring More Features
In addition to the features described so far in this chapter, there are many more VXSM features that can be configured by the user. Refer to Chapter 5 in this guide to see configuration details of these additional features. Such features include:
•
•
•
•
•
•
