|
|
Table Of Contents
Features and Advanced Configurations
Dynamic Payload for Voice Codecs
1560/980 Hz Modem Tone Detection
Bandwidth Utilization Enhancements
PVC OAM Cell Parameter Configuration
Private Network-to-Network Interface Priority Routing
Trunking Gateway Control Protocol Release 1.0
AAL1 SVC-Based TDM Hairpinning
ISDN Backhaul Advanced Configuration
Diagnostic Testing for DSP Failures
Static and Real-Time Configuration Display
VISM-PR Bulk Statistics Upload to CWM
VISM TDM Line Statistics Collection
Loopbacks for Lines and Connections
E1 CAS Idle Code Configuration
TDM Companding Law Configuration
Programmable CAS Bit Mapping (ABCD CAS bits)
Adjustable Music On-Hold Threshold
Features and Advanced Configurations
This section describes the VISM/VISM-PR features and advanced configurations listed in Table 9-1.
DSP/Bearer Features
This section describes the VISM/VISM-PR DSP/bearer capabilities. It includes the following sections:
•
Codecs
•
•
•
Codecs
VISM/VISM-PR allows the use of codec templates in which you can select a template instead of specifying each allowable codec individually.
Within each codec template, you can specify an order of preference. At call setup time, the codec to be used from the configured template is either specified by the call agent or negotiated between the calling and called VISM/VISM-PR cards. If the codec is negotiated, the most preferred codec that both VISM/VISM-PR cards can support is selected.
Table 9-2 lists the VISM/VISM-PR codecs and their attributes.
G.729a Codec with 20 ms Packetization Period
VISM/VISM-PR cards contain a custom profile to support the G.729a codec with a 20-millisecond (ms) packetization period.
The Custom profile type, 210, supports upspeeding from the G.729a codec with a 20-ms packetization period to other codecs, including G.711 Mu/A law and Clear Channel. Profile type 210 also includes the CCD voiceband data (VBD) codec.
For the VISM card, the G.729a codec with a 20-ms packetization period is supported for AAL2 trunking and applies to templates 1, 3, and 4.
For the VISM-PR card, the G.729a codec with a 20-ms packetization period is supported for switching and trunking modes and applies to templates 1, 3, 4, and 5.
VISM-PR Lossless Compression
The lossless compression feature includes the lossless compressed (LLC) codec that allows higher throughput through the T1/E1 lines by removing information redundancy.
Lossless compression provides the following functions:
•
•
•
•
The lossless compression codec supports the following specifications:
•
•
•
•
•
Note
Dynamic Payload for Voice Codecs
VISM/VISM-PR supports the dynamic payload for voice codecs.
To configure the VISM/VISM-PR card for dynamic payload, complete the following steps:
Step 1
nodename.1.12.VISM8.a > cnfdynamicpayload <dynamic_payload>Replace the <dynamic_payload> argument with a value of 1.
•
•
Step 2
nodename.1.12.VISM8.a > dspdynamicpayloadDynamic Payload flag: enableWhen dynamic payload is enabled, the session description protocol (SDP) payload type is negotiated in the range from 96 to 127 during codec negotiation.
The payload type specified in the addrtpcon, cnfrtpcon, or cnfvbdcodec command is passed to the digital signal processor (DSP) to modify its static payload types. When dynamic payload is disabled, the DSP uses the static payload type values for the codec.
V.110
VISM-PR can support V.110 data traffic transport through ATM trunks.
When V.110 is enabled on a line, VISM-PR detects the V.110 traffic and upspeeds to Clear Channel. This upspeeding allows for 64K clear data transport. When the V.110 stream is not detected, VISM-PR downspeeds from Clear Channel to a previous codec.
The total number of supported V.110 calls is the same as the total number of Clear Channel calls that are supported in AAL2 trunking mode.
You can enable or disable V.110 on a line and is applicable only to AAL2 trunking mode.
Enabling V.110
To enable or disable V.110, complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
cnflnv110 <line_number> <v110_flag>
Replace <line_number> with the line number on which you want to enable or disable V.110. Range is 1-8.
Replace <v110_flag> with one of the following values to enable or disable V.110 on the line:
•
•
The following example shows the sample syntax to enable V.110 detection on line 1.
nodename.1.28.VISM8.a > cnflnv110 1 1
nodename.1.28.VISM8.a >
Step 6
nodename.1.28.VISM8.a > dspln 1LineNum: 1LineConnectorType: RJ-48LineEnable: ModifyLineType: dsx1ESFLineCoding: dsx1B8ZSLineLength: 0-131 ftLineXmtClockSource: LocalTimingLineLoopbackCommand: LocalLineLoopLineSendCode: NoCodeLineUsedTimeslotsBitMap: 0xffffffLineLoopbackCodeDetection: codeDetectDisabledLineSignalingType: No SignalingLineCcsChannels: 0x0LineTrunkConditioning: disableLineBearerBusyCode: 127CircuitIdentifier:TxDigitOrder: aniThenDnisTonePlanRegion:TonePlanVersion: 0RingingTO: 180RingBackTO: 180Type <CR> to continue, Q<CR> to stop:BusyTO: 30ReorderTO: 30DialTO: 16StutterDialTO: 16OffHookAlertTO: 5RemoteRingbackMethod: proxyV110Detection: enableLineNumOfValidEntries: 8nodename.1.28.VISM8.a >1560/980 Hz Modem Tone Detection
Some proprietary modem modulations might not be recognized as modem signals. Therefore, the modem cannot switch from a compressed voice mode channel to modem pass-through.
The 1560/980 Hz modem tone can be used to detect a proprietary signal from the modem and to carry the encrypted data over a secure modem connection in a VoIP network.
In Release 3.3.20, you can configure the VISM-PR card to detect the 1560/980 Hz modem tone in the VoIP switching mode.
When the 1560/980 Hz modem tone is detected, the VISM-PR upspeeds to the Clear Channel codec. Voice activity detector (VAD) and echo canceller (ECAN) are automatically disabled. When silence is detected, the VISM-PR downspeeds back to its voice codec and to the original VAD and ECAN states.
Prerequisites
Before enabling 1560/980 Hz tone detection, complete the following tasks for the local and remote VISM-PR cards:
1.
2.
Note
3.
Configuring the Tone Detection
By default, 1560/980 Hz tone detection is disabled.
To enable or disable the detection of the 1560/980 Hz tones, complete the following steps.
Note
Step 1
sol-mgx2.1.19.VISM8.a > cnfsplmodemtoneenbl <tone_id>Replace <tone_id> with a value of 1 to indicate 1560/980 Hz tone.
sol-mgx2.1.19.VISM8.a > cnfsplmodemtoneenbl 1sol-mgx2.1.19.VISM8.a >Step 2
sol-mgx2.1.19.VISM8.a > dspsplmodemtone1560/980 Hz Modem Tone Detection : ENABLEDStep 3
sol-mgx2.1.19.VISM8.a > cnfsplmodemtonedsblReplace <tone_id> with a value of 1 to indicate 1560/980 Hz tone.
sol-mgx2.1.19.VISM8.a > cnfsplmodemtonedsbl 1sol-mgx2.1.19.VISM8.a >Step 4
sol-mgx2.1.19.VISM8.a > dspsplmodemtone1560/980 Hz Modem Tone Detection : DISABLEDConfigurable Jitter Buffer
The configurable jitter buffer feature provides configuration of jitter buffer mode (fixed and adaptive) and initial delay time on a codec basis.
Fixed mode is used if the latency is expected to be constant.
Adaptive mode is used if the latency is expected to be varied.
This feature reduces packet loss for fax, modem, and CCD calls.
Use the following command to configure the jitter buffer:
cnfcodecjtrdelay <codecType> <jitter_mode> <jitter_initdelay>
Replace the above arguments with the values listed in Table 9-3.
Use the dspcodecjtrdelays command to display the jitter buffer parameters you configured with the cnfcodecjtrdelay command.
nodename.1.5.VISM8.a > dspcodecjtrdelayscodecType delay mode timestamp initial delay------------- ----------- --------- -------------1 - G.711u fixed No hundred2 - G.711a fixed No hundred3 - G.726-32K adaptive N/A sixty4 - G.729a adaptive N/A sixty5 - G.729ab adaptive N/A sixty6 - clr chan fixed No hundred7 - G.726-16K adaptive N/A sixty8 - G.726-24K adaptive N/A sixty9 - G.726-40K adaptive N/A sixty11 - G.723.1-H adaptive N/A sixty12 - G.723.1a-H adaptive N/A sixty13 - G.723.1-L adaptive N/A sixty14 - G.723.1a-L adaptive N/A sixty15 - Lossless fixed No sixteen
Note
ATM Fax Relay
The ATM fax relay feature allows the VISM-PR card to transport fax over an ATM trunk more reliably and efficiently than fax pass through by using less bandwidth.
This feature is applicable to the VISM-PR card in AAL2 trunking mode.
Note
If both the near-end and far-end gateways support ATM fax relay, an attempt is made to switch to ATM fax relay for the connection.
If neither gateway supports ATM fax relay or an attempt to switch fails, the connection remains established as a voice call or pass through until one of the endpoints goes on-hook.
ATM fax relay uses less than 50 cps bandwidth for each connection.
Configure ATM Fax Relay Parameters
To configure ATM fax relay parameters, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.18.VISM8.a > cnffaxrelayparams <line_number> <Max_Xmit_Rate> |<NSF_Override> <NSF_Country_Code> <NSF_Vendor_Code> <T30_ECM>|Replace the above arguments with the values listed in Table 9-4.
Example 9-1 shows the command to configure the maximum fax transmission rate of 14400 bps on line 1. Unless the optional parameters are configured, they automatically set to the default values.
Example 9-1 Configuring Fax Relay Parameters
nodename.1.28.VISM8.a > cnffaxrelayparams 1 6nodename.1.28.VISM8.a >Step 4
nodename.1.28.VISM8.a > dspfaxrelayparams <line_number>Replace the <line_number> argument with a value in the range 1-8.
Example 9-2 shows the sample output of the fax relay parameters for line 1.
Example 9-2 Displaying Fax Relay Parameters
nodename.1.18.VISM8.a > dspfaxrelayparams 1line_number: 1Max_Xmit_Rate: fx14400bpsNSF_Override: enabledNSF_Country_Code: 173NSF_Vendor_Code: 81T30_ECM: enablednodename.1.18.VISM8.a >Configure ATM Fax Relay Acknowledgment Timeout
To configure the fax relay acknowledgment timeout, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.18.VISM8.a > cnffaxrelaytimeout <line_number> <Ack_Timer>Replace the <line_number> argument with a line number in the range 1-8.
Replace the <Ack_Timer> argument with a value in the range 250-10000 ms in multiples of 250.
The acknowledgment timer is the amount of time the near-end fax waits for a response from the far-end fax. Expiration of this response time indicates that the request to switch over to ATM fax relay has been rejected or discarded by the far-end.
The following example shows the command to configure the acknowledgment timeout as 1000 ms on line 1.
nodename.1.28.VISM8.a > cnffaxrelaytimeout 1 1000Step 4
nodename.1.18.VISM8.a > dspfaxrelaytimeout <line_number>Replace the <line_number> argument with a value in the range 1-8.
Example 9-3 shows the default timeout value for line 1.
Example 9-3 Displaying Fax Relay Timeout Values for a Line
nodename.1.18.VISM8.a > dspfaxrelaytimeout 1line_number: 1FAX_Ack_Timer: 1000 msStep 5
nodename.1.18.VISM8.a > dspfaxrelaytimeouts
Example 9-4 shows the default fax acknowledgment timeout values for all of the lines on the VISM-PR card.
Example 9-4 Displaying Fax Relay Timeout Values for All Lines
nodename.1.18.VISM8.a > dspfaxrelaytimeoutsLine_Number FAX Ack Timeout (ms)----------- ---------------------1 10002 10003 10004 10005 10006 10007 10008 1000Enable ATM Fax Relay
By default, ATM fax relay is enabled for the line.
To enable ATM fax relay, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.18.VISM8.a > cnffaxrelay <line_number> <faxrelay>Replace the <line_number> argument with a value in the range 1-8.
Replace the <faxrelay> argument with one of the following values:
•
•
Step 4
nodename.1.18.VISM8.a > dspfaxrelay <line_number>
Replace the <line_number> argument with a value in the range 1-8.
Example 9-5 shows that fax relay is enabled on line 1.
Example 9-5 Displaying Fax Relay Status
nodename.1.18.VISM8.a > dspfaxrelay 1line_number: 1faxrelay: EnabledStep 5
nodename.1.18.VISM8.a > dspfaxrelays
Example 9-6 shows that ATM fax relay is enabled on all of the lines of the VISM-PR card.
Example 9-6 Displaying Fax Relay Status for All Lines
nodename.1.18.VISM8.a > dspfaxrelaysLine_Number Fax Relay----------- -------1 Enabled2 Enabled3 Enabled4 Enabled5 Enabled6 Enabled7 Enabled8 EnabledT.38 Fax Relay
The ITU T.38 recommendation for the fax relay feature is for fax transmission over IP networks. To configure the T.38 fax transfer parameters for a specified line, use the cnft38params.
For more information about the cnft38params command, see "cnft38params" section on page 10-354 of Chapter 10, "CLI Commands."
Note
Call Agent-Controlled T.38 Fax
The call agent-controlled T.38 fax feature is an additional operational mode for MGCP 1.0. The VISM can interoperate with H.323 and non-Cisco gateways, and is supported for VoIP calls. This feature is activated by fax tone and signaling carried with the call agent.
The cnft38fxlco command allows you to set the local connection option fax preamble response to off.
Mid-Call DTMF
The mid-call dual tone multifrequency (DTMF) feature enables the collection and notification of digits to the call agent following a call setup for an endpoint. This feature also supports the out-pulsing of DTMF digits at a call agent's request. This feature is used for services that require two-stage dialing, such as calling card applications.
Mid-call DTMF is supported for all the channel-associated signaling (CAS) variants, for DTMF mode only.
DTMF Relay and Passthrough
VISM/VISM-PR supports DTMF relay using named telephony events (NTEs), named signaling event (NSE) based relay, and Cisco-RTP based relay. For all other tones, VISM uses NSEs.
By default, DTMF relay is enabled. In VoIP switching mode, if you want to run DTMF in passthrough mode, use the cnfvoiptransparams command to disable the DTMF relay.
nodename.1.27.VISM8.a > cnfvoiptransparams <DtmfRelay> <CasBits> |<EventNego> <EventNegoPolicy> <SIDPayloadType>|Use the following parameter values to disable the DTMF relay:
nodename.1.27.VISM8.a >cnfvoiptransparams 2 1 2 1The optional <EventNego> argument is used to enable and disable event negotiation since this argument is used by VISM/VISM-PR to decide whether or not to advertise a named telephony event (NTE) for DTMF relay.
VISM/VISM-PR card looks at a combination of the <DtmfRelay> and <EventNego> arguments to ascertain whether or not to enable the DTMF relay or to fall back to DTMF passthrough (inband).
If event negotiation is disabled, the VISM/VISM-PR card does not advertise the DTMF relay NTE capability.
ATM (PVC) Features
This section contains the VISM/VISM-PR ATM (PVC) features described in the following sections:
•
•
•
Preferred Routes
Note
In a PNNI network with a large number of SPVCs, the Cisco MGX 8850 (PXM1E and PXM45) can route SPVCs and SPVPs over predefined trunk routes in a PNNI group. This capability means that fewer connections need to be manually rerouted.
You can provision the VISM-PR card to specify a routing preference in case the preferred route is not available.
This feature is applicable to VISM-PR cards operating in AAL2 trunking or VoIP switching mode.
Preferred route configuration is done on the PXM card. Therefore, only VISM-PR SPVC connections that have master endpoints can be added as preferred routes.
For more information on configuring preferred routes, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1.
Prerequisites
Before configuring your SPVC as a preferred route, complete the following prerequisites:
•
•
–
–
–
–
Configure Preferred Routes
To configure your VISM-PR card for preferred routes, complete the following steps:
Step 1
Step 2
Step 3
Use the following optional <prefrte> and <direct> arguments, which support the preferred route feature.
nodename.1.12.VISM8.a > addcon <localVCI> <preference> <pvc_type> <application> <PCR> <mastership> |<remoteConnId> <serviceType> <scr> <mbs> <priority> <prefrte> <direct>|Replace the above arguments with the values listed in Table 9-5.
Example 9-7 shows a PVC being added as the master endpoint of a preferred route.
Example 9-7 Adding a PVC as a Preferred Route
nodename.1.12.VISM8.a > addcon 131 1 2 2 50000 1 mgx8850.0.4.120.120 1 150 777 1Step 4
Use the optional <prefrte> and <direct> arguments that support the preferred route feature.
nodename.1.12.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress> <priority> <prefrte> <direct>In Example 9-8 the master endpoint of this connection is associated with a preferred route.
Example 9-8 Associating a Master Endpoint to a Preferred Route
nodename.1.12.VISM8.a > cnfcon 131 60000 1 777 1where 777 is the preferred route ID, and 1 is a directed route.
Replace the above arguments with the values listed in Table 9-6.
Step 5
nodename.1.12.VISM8.a > dspcon <LCN>Replace the <LCN> argument with the logical channel number of the SPVC you configured in Step 4.
Example 9-9 shows the preferred route information for LCN 131.
Example 9-9 Displaying the Preferred Route Identifier
nodename.1.12.VISM8.a > dspcon 131
ChanNum: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: FailedChanRTDresult: 65535 msChanPortNum: 255ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 29ChanLocalVci: 131ChanLocalNSAP: 47009181000000000164444b9400000107ebff00ChanRemoteVpi: 29ChanRemoteVci: 131ChanRemoteNSAP: 47009181000000000164444b9400000101180400ChanMastership: MasterChanVpcFlag: VccChanConnServiceType: CBRChanRoutingPriority: 8ChanMaxCost: 2147483647ChanRestrictTrunkType: No RestrictionType <CR> to continue, Q<CR> to stop:ChanConnPCR: 50000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 50000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 50000ChanMbsIngress: 50000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalsePref Rte Id : 777Directed Route: YesChanUserPcrNumber: User BW OffChanUserMinPCRBW: 10ChanUserMaxPCRBW: 50000ChanUserMaxScrBW: 0ChanUserMaxMbsBW: 0ChanNumNextAvailable: 133For slave endpoints, the preferred route identifier value is 0, and the directed route flag is No.
Priority Bumping
Note
Priority bumping can be used to set up high-priority connections even when the available bandwidth resources on the links are not enough to route the connection. With priority bumping on the VISM-PR card, the connections that have a priority lower than the priority of the incoming connection are bumped so that the necessary resources for routing the high-priority connections are available.
The lower priority calls might have to be de-routed on the ingress interface and the egress interface to free up resources.
Priority bumping is used in a PNNI network and is applicable to the VISM-PR card and AAL2 trunking mode only.
Configure Priority Bumping
To configure priority bumping on the VISM-PR card, complete the following steps:
Step 1
Step 2
Step 3
Step 4
•
•
•
•
Step 5
nodename.1.12.VISM8.a > addcon <localVCI> <preference> <pvc_type> <application> <PCR> <mastership> |<remoteConnId> <serviceType> <scr> <mbs> <priority> <prefrte> <direct>|Replace the above arguments with the values listed in Table 9-7.
Example 9-10 shows a PVC being added as the master endpoint of a preferred route with the highest priority.
Example 9-10 Adding a PVC with Highest Priority
nodename.1.12.VISM8.a > addcon 131 1 2 2 50000 1 mgx8850.0.4.120.120 1 150 777 1 1Step 6
nodename.1.12.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress> <priority> <prefrte> <direct>Replace the above arguments with the values listed in Table 9-8.
Example 9-11 shows that the master endpoint of this connection is associated with a preferred route and that the endpoint is set as the highest priority.
Example 9-11 Configuring Priority Bumping on a Connection
nodename.1.12.VISM8.a > cnfcon 131 60000 1 777 1 1Step 7
nodename.1.12.VISM8.a > dspcon <LCN>Replace <LCN> with the logical channel number of the SPVC you configured in Step 6.
Example 9-12 shows the routing priority for LCN 131. The priority is shown in bold.
Example 9-12 Displaying the Priority of a Connection
nodename.1.12.VISM8.a > dspcon 131ChanNum: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: FailedChanRTDresult: 65535 msChanPortNum: 255ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 29ChanLocalVci: 131ChanLocalNSAP: 47009181000000000164444b9400000107ebff00ChanRemoteVpi: 29ChanRemoteVci: 131ChanRemoteNSAP: 47009181000000000164444b9400000101180400ChanMastership: MasterChanVpcFlag: VccChanConnServiceType: CBRChanRoutingPriority: 1ChanMaxCost: 2147483647ChanRestrictTrunkType: No RestrictionType <CR> to continue, Q<CR> to stop:ChanConnPCR: 50000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 50000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 50000ChanMbsIngress: 50000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalsePref Rte Id : 777Directed Route: YesChanUserPcrNumber: User BW OffChanUserMinPCRBW: 10ChanUserMaxPCRBW: 50000ChanUserMaxScrBW: 0ChanUserMaxMbsBW: 0ChanNumNextAvailable: 133AIS Propagation Control
The alarm indication signal (AIS) propagation control feature prevents the CPE from dropping calls when a network link failure is temporary.
You can configure the suppression of ATM network alarms for a particular duration. If the ATM network alarms persist beyond this duration, the alarms are allowed to propagate onto the TDM line and be considered a permanent network failure.
This section contains the following topics:
If an endpoint is in AAL2 trunking mode, the VISM/VISM-PR propagates a network alarm to the T1/E1 line that is associated with the network link. The CPE equipment (PBX) receives this alarm and drops the calls.
VISM/VISM-PR processes several alarms. However, for this feature, only the following alarms are suppressed:
•
•
•
Because this alarm suppression causes network link failures to be ignored, the Operation, Administration, and Maintenance (OAM) end-to-end loopback monitoring function must be configured to detect permanent network failures.
Enabling AIS Suppression
By default, AIS suppression is disabled. VISM/VISM-PR cards on both ends of the AAL2 trunk need to be loaded with firmware that supports and enables AIS suppression.
To enable AIS suppression for a particular duration, complete the following steps.
Note
Step 1
nodename.1.12.VISM8.a > cnfvismmode 2WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? yINFORMATION: The new 'aal2Trunking' mode has 182 CLI commands.Step 2
nodename.1.12.VISM8.a > cnfaissuppression <enableFlag> |<LCN> <delay_time>|Replace the above arguments with the values listed in Table 9-9.
The following example shows the syntax for enabling alarm propagation:
nodename.1.12.VISM8.a > cnfaissuppression 1INFORMATION: Successfully Enabled AIS Suppression.If you attempt to enable AIS propagation when it is already enabled, the following message displays:
WARNING: AIS Suppression is already enabled.The following example enables AIS propagation with an AIS delay of 30 seconds on all enabled PVCs:
nodename.1.12.VISM8.a > cnfaissuppression 1 ALL 30nodename.1.12.VISM8.a >The following example disables AIS propagation on all enabled PVCs:
nodename.1.12.VISM8.a > cnfaissuppression 2 ALLnodename.1.12.VISM8.a >The following example enables AIS propagation on PVC 131 with an AIS delay of 60 seconds:
nodename.1.12.VISM8.a > cnfaissuppression 1 131 60Step 3
nodename.1.12.VISM8.a > dspaissuppressionConnId ChanNum Status AIS Delay Time AIS Delay Left------ ------- -------- -------------- --------------nodename.27.255.27.131 131 DISABLED 60 0Step 4
nodename.1.12.VISM8.a > cnfaissuppression 2INFORMATION: Successfully Disabled AIS Suppression.Configuring OAM Loop Count
Since an OAM end-to-end loopback failure can still cause line alarms, you must configure the OAM loop count to be longer than the expected duration of the temporary network outage that results from a reroute.
Note
Step 1
nodename.1.12.VISM8.a > cnfvismmode <2>Step 2
nodename.1.12.VISM8.a > dspoamloopcntThe loop count is displayed with the default value of 5 seconds.
OAM Loopback Cell Timeout Count: 5Step 3
nodename.1.12.VISM8.a > cnfoamloopcnt <count>Replace <count> with the number of seconds you want to use, in the range 5 to 60.
Displaying Alarms
VISM/VISM-PR discovers network outages by means of OAM end-to-end loopback failures. Lost OAM loopback cells can be monitored by using the following command:
dspconcnt <LCN>
The following example shows the output:
mgx.1.12.VISM8.a > dspconcnt 131ChanNum: 131Chan State: alarmChan XMT ATM State: Sending FERF OAMChan RCV ATM State: Receiving AIS OAMChan Status Bit Map: 0x2OAM Lpb Lost Cells: 20AAL2 HEC Errors: 2AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 1AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 118467937AAL2 CPS Packet Rcv: 116227849AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0OAM AIS and far-end receive failure (FERF) cells that are transmitted and received are tabulated in counters. With this feature, an alarm is not generated on the line.
The following examples show alarm counts after an OC-3 failure. AIS alarm cells are received, and FERF cells are transmitted in response.
•
mgx.1.12.VISM8.a > dspsarcnt 131SarShelfNum: 1SarSlotNum: 5SarChanNum: 131Tx Rx--------------- ---------------Total Cells: 406656 333840Total CellsCLP: 0 0Total CellsAIS: 0 13Total CellsFERF: 12 0Total CellsEnd2EndLpBk: 85 69Total CellsSegmentLpBk: 0 0RcvCellsDiscOAM: 0•
mgx.1.12.VISM8.a > dspalm -ds1 1LineNum: 1LineAlarmState: No AlarmsLineStatisticalAlarmState: Alarm(s) On --SEFS24hrAlarmUAS24hrAlarm
Note
Without the AIS propagation feature, the LineAlarmState shows XmtAIS and RcvRAI.
mgx.1.12.VISM8.a > dspalm -ds1 1LineNum: 1LineAlarmState: Alarm(s) On --RcvRAIXmtAISLineStatisticalAlarmState: Alarm(s) On --SEFS24hrAlarmUAS15minAlarmUAS24hrAlarmAlarms Not Suppressed
Alarm suppression does not affect the following AAL2 type 3 packet alarms (transmitted and received per CID):
•
•
•
•
These alarms allow the line alarms that are received due to a T1/E1 failure to be propagated to the remote end.
Bandwidth Utilization Enhancements
This section includes the following bandwidth utilization features:
•
•
ATM Bandwidth Reuse for Non-overlapping Traffic
This feature allows you to place an unused PVC out-of-service during nonservice hours and place another PVC in-service during the service window while utilizing the same ATM bandwidth. This feature is applicable to VISM-PR cards in PNNI networks.
When a PVC is placed out-of-service, the PVC does not utilize any bandwidth and does not generate any alarms towards the CPE.
This bandwidth enhancement requirement uses the existing dncon command. The dncon command is now supported on both the master-end and the slave-end of the connections and is also used to disable the OAM end-to-end loopback functionality.
Disabling the OAM end-to-end loopback functionality on both ends of the connection avoids generating alarms to the TDM side. Therefore, you do not see alarms during non-service hours. The row status is not affected for the slave-end connection, and only the connection administrative status is changed to Down.
The existing upcon command is modified for both the master and slave ends. On the master end, the upcon command causes the OAM end-to-end loopback functionality to be re-enabled and places the PVC back in-service. The connection is re-routed if enough bandwidth is present.
On the slave end, the upcon command causes OAM end-to-end loopback functionality to be re-enabled, so the PVC can be monitored for failure.
To place a PVC out-of-service/in-service without causing alarms on the PVC and TDM side, complete the following steps in the order listed below:
Step 1
Step 2
Step 3
nodename.1.12.VISM8.a > dncon <LCN>Replace <LCN> with the slave-end channel number of the connection.
The slave-end stops generating voice packets and also stops OAM end-to-end loopback request cell generation. However, incoming OAM end-to-end loopback request cells are processed, and appropriate OAM end-to-end loopback response cells are generated.
This process ensures that alarms are not generated on the slave-end when you perform Step 4.
Step 4
nodename.1.12.VISM8.a > dncon <LCN>Replace <LCN> with the master-end channel number of the connection.The PVC is placed into an administratively down state. This state tears down the PVC, stops checking for OAM end-to-end loopback failures, and stops generating voice packets.
Step 5
nodename.1.12.VISM8.a > upcon <LCN>Replace <LCN> with the master-end channel number of the connection.
Step 6
nodename.1.12.VISM8.a > upcon <LCN>Replace <LCN> with the slave-end channel number of the connection.
Dynamic PVC Bandwidth Management
You can dynamically change and manage PVC bandwidth on VISM-PR cards with calls present.
This feature also provides you with configurable administrative states at the CID (or bearer connection) level to manage the operations of used bandwidth. You can take put the PVC into a minimum mode configuration in which just enough bandwidth is used to maintain the signaling link. It is recommended that both sides of the connection be placed in a minimum mode.
To configure the administrative states and the bandwidth usage on the PVC, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.12.VISM8.a > cnfcidis <LCN> <cid_number> |<maxcid>|In-service means the CID is enabled and operationally active. To place a CID in-service, enough bandwidth must exist.
Replace the above arguments with the values listed in Table 9-10.
The following example shows CID 100 on LCN 131 is configured for in-service.
nodename.1.12.VISM8.a > cnfcidis 131 100
Step 4
nodename.1.12.VISM8.a > cnfcidoos <LCN> <cid_number> |<maxcid>|An out-of-service state means that the CID(s) are disabled and not operationally active.
Replace the above arguments with the values listed in Table 9-11.
The following example shows CID 8 on LCN 131 is configured for out-of-service.
nodename.1.12.VISM8.a > cnfcidoos 131 8
Step 5
nodename.1.12.VISM8.a > dspcid <LCN> <cid_number>Replace <LCN> with the logical channel number of the CID, in the range 131-510.
Replace <cid_number> with the number of the CID, in the range 8-255.
The following example shows the CID 8 on LCN 131 is in the out-of-service administrative state:
nodename.1.12.VISM8.a > dspcid 131 8LCN number : 131CID number: 8Endpoint number : 1CidRowStatus: activeType3redundancy: enabledVAD: disabledVADInitTimer: 250Profile type: ITUProfile number: 1Codec type: G.711uCas transport: disabledDTMF transport: enabledEcan on/off: enabledICS enable: Disabledpkt period: 5Cid state: FailedCid Fail Reason: SelfCid Admin State: OOSStep 6
nodename.1.12.VISM8.a > cnfconbwtoggle <LCN> <USER_BW_OPTIONS>Replace <LCN> with the logical channel number, in the range 131-510.
Replace <USER_BW_OPTIONS> with one of the following bandwidth toggle options:
•
•
Step 7
nodename.1.12.VISM8.a > dspcon <LCN>Replace <LCN> with the logical channel number, in the range 131-510.
The following example shows sample bandwidth values on LCN 131. The original PVC configured bandwidth is being used, shown in the ChanUserPcrNumber field (User BW Off). If the minimum bandwidth is used, the ChanUserPcrNumber field shows User BW Min.
mnodename.1.12.VISM8.a > dspcon 131ChanNum: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: NotInProgressChanRTDresult: 65535 msChanPortNum: 1ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 0ChanLocalVci: 131ChanLocalNSAP: 6d696c7777693033000000000000000015000100ChanRemoteVpi: 0ChanRemoteVci: 0ChanRemoteNSAP: NULL NSAPChanMastership: SlaveChanVpcFlag: VccChanConnServiceType: CBRChanRoutingPriority: 8ChanMaxCost: 255ChanRestrictTrunkType: No RestrictionType <CR> to continue, Q<CR> to stop:ChanConnPCR: 10000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 10000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 10000ChanMbsIngress: 10000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalseChanPrefRouteId: 0ChanDirectRoute: FalseType <CR> to continue, Q<CR> to stop:ChanUserPcrNumber: User BW OffChanUserMinPCRBW: 10ChanUserMaxPCRBW: 10000ChanUserMaxScrBW: 0ChanUserMaxMbsBW: 0ChanNumNextAvailable: 132Channel Current Peak Rates
Several real-time statistics can be collected and displayed for cell rates on the PVC.
To display the cell rate in cells per second (cps) per PVC, use the existing dspconcnt command.
nodename.1.12.VISM8.a > dspconcnt <LCN>Replace <LCN> with the logical channel number, in the range 131-510.
The following example shows sample cell rates values on LCN 131:
nodename.1.12.VISM8.a > dspconcnt 131ChanNum: 131Chan State: alarmChan XMT ATM State: Sending FERF OAMChan RCV ATM State: OAM End-to-End Loopback FailureChan Status Bit Map: 0x4OAM Lpb Lost Cells: 406799AAL2 HEC Errors: 0AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 0AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 81848211AAL2 CPS Packet Rcv: 0AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0Chan 24Hr Peak Xmt Cell Rate (CPS):185Chan Current Xmt Cell Rate (CPS):184Chan 24Hr Peak Rcv Cell Rate (CPS):0Chan Current Rcv Cell Rate (CPS):0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0Type <CR> to continue, Q<CR> to stop:Channel countersAAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0AIS Successful Suppression Count: 0
Note
PVC OAM Cell Parameter Configuration
This feature allows you to configure the transmitted and received permanent virtual circuit (PVC) OAM cell parameters—cell gap, recovery cell count, and unacknowledged cell count.
Use the following command to configure OAM parameters.
cnfoamparams <oam_cell_gap> <retry_cnt> <recover_cnt>
Replace the above arguments with the values listed in Table 9-12.
Use the dspoamparams command to display the OAM parameters that you configured with the cnfoamparams command.
nodename.1.1.VISM8.a > dspoamparamsOAM Cell Gap: 500 msOAM Cell Retry Count: 3OAM Cell Recover Count: 5Private Network-to-Network Interface Priority Routing
This release supports the Private Network-to-Network Interface (PNNI) routing priority feature. This feature allows you to specify a routing priority for a connection. The PNNI controller uses your configuration selections to route the higher priority connections before routing the lower priority connections.
Note
Use the cnfpncon command to configure a routing priority for a specified connection.
nodename.1.28.VISM8.a > cnfpncon <LCN> <rout_priority>Replace <LCN> with a value in the range 131-510.
Replace <rout_priority> with a route priority value in the range 1-15. A value of 1 is (highest). A value of 15 is lowest. Default is 8.
Use the dspcon command to display the values you configured using the cnfpncon command.
nodename.1.1.VISM8.a > dspcon 131
ChanNum: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: FailedChanRTDresult: 65535 msChanPortNum: 255ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 29ChanLocalVci: 131ChanLocalNSAP: 47009181000000000164444b9400000107ebff00ChanRemoteVpi: 29ChanRemoteVci: 131ChanRemoteNSAP: 47009181000000000164444b9400000101180400ChanMastership: MasterChanVpcFlag: VccChanConnServiceType: CBRChanRoutingPriority: 8ChanMaxCost: 2147483647ChanRestrictTrunkType: No RestrictionType <CR> to continue, Q<CR> to stop:ChanConnPCR: 50000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 50000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 50000ChanMbsIngress: 50000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalsePref Rte Id : 777Directed Route: YesChanUserPcrNumber: User BW OffChanUserMinPCRBW: 10ChanUserMaxPCRBW: 50000ChanUserMaxScrBW: 0ChanUserMaxMbsBW: 0ChanNumNextAvailable: 133Additional VBR Enhancements
Use the addcon or cnfcon commands to configure the VBR connection type. The following additional connection service types can be configured with the these commands:
•
•
•
Call Control
This section describes the VISM/VISM-PR call control features described in the following sections:
•
•
•
•
•
•
Separate Bearer IP Address
Two IP addresses allow you to add separate IP addresses for the control and bearer/data paths for VISM. This feature enables the control and data traffic togo to two different domains.
Configuring Bearer IP Address
Use the cnfvismip command to configure a bearer IP address.
cnfvismip <vismIpAddr> <netMask> |<vismBearerIpAddr> <bearerNetMask>|
Replace the above arguments with the values listed in Table 9-13.
The following example shows sample syntax for the cnfvismip command.
nodename.1.28.VISM8.a > cnfvismip 10.20.30.99 255.255.255.0 10.20.31.99 255.255.255.0Bearer IP Address Ping
In Release 3.3, you can ping both the control traffic IP address and the bearer traffic IP address on the VISM/VISM-PR card.
Before completing the steps in this section, configure control and bearer IP addresses as described in the Configuring Domain Names and IP Addresses section in the VoIP Switching Mode or VoIP Trunking Mode sections.
To configure the VISM/VISM-PR card to respond to bearer ping requests, complete the following steps:
Step 1
Step 2
nodename.1.28.VISM8.a > cnfbearerippingenable <enable>Replace the <enable> argument with one of the following values:
•
•
Step 3
nodename.1.4.VISM8.a > dspvismparamVISM mode: voipSwitching/voipTrunkingVISM features Bit Map: 0x5bcFunctionModuleType: VISM-8T1CAC flag: enableDS0s available: 192Template number: 2Percent of functional DSPs: 100IP address: 25.5.4.2Subnet mask: 255.255.255.0Bearer IP address: 25.5.4.3Bearer Subnet mask: 255.255.255.0Bearer IP ping: enableRTCP report interval: 5000 msecRTCP receive multiplier: 3RTP receive timer: disableControlPrecedence/Tos: 0x60BearerPrecedence/Tos: 0xa0Aal2 muxing status: disableTftp Server Dn TFTPDOMAINAggregate Clipping enableType <CR> to continue, Q<CR> to stop:Aggregate Svc Bandwidth 0Codec negotiation option 1Profile negotiation option 1VAD Duty Cycle 61VAD Tolerance 100VISM Initiated NW COT OffVISM CO4 Timer 1000 msecCALEA flag disableSupportdModuleType: VISM-8T1.VismNSAP: 6376676d67783161000000000000000004000100Call Throttling
Call throttling is implemented on the VISM-PR card to maintain the stability of the card when the call rate exceeds the maximum allowable limit. The VISM-PR card drops the incoming calls when the maximum operational limit is exceeded. These new incoming calls are rejected with error code 409—Internal overload (xGCP).
New calls are dropped until the call rate drops below the maximum operational limit.
To display the message failure counter and 24-hr rejection counters, use the dspxgcpdetailcnts command.
nodename.1.28.VISM8.a > dspxgcpdetailcntsIP Address : 10.86.28.56CRCX Count : 0CRCX Fail Count : 0MDCX Count : 0MDCX Fail Count : 0DLCX Received Count : 0DLCX Received Fail Count : 0DLCX Sent Count : 0DLCX Sent Fail Count : 0RQNT Count : 0RQNT Fail Count : 0Notify Count : 0Notify Fail Count : 0Audit Endpoint Count : 0Audit Endpoint Fail Count : 0Audit Connection Count : 0Audit Connection Fail Count : 0RSIP Count : 4RSIP Fail Count : 4CRCX Throttled Count : 100CRCX Throttled 24 Hr Count : 100Trunking Gateway Control Protocol Release 1.0
The Trunking Gateway Control Protocol (TGCP) is a profile of the Media Gateway Control Protocol (MGCP) 1.0 that is used to control the trunking gateway in packet cable network.
This section contains the following topics:
Configuring TGCP
To configure the call agent for the TGCP 1.0 protocol, complete the following steps:
Step 1
nodename.1.28.VISM8.a > dspmgprotocolsNumber mgProtocol---------- -----------1 MGCP 0.12 SGCP 1.1+3 SRCP 1.0.24 SGCP 1.55 MGCP 1.06 TGCP 1.0Step 2
nodename.1.28.VISM8.a > addmgcgrpprotocol <Red_Group_Num> <protocol_number> |<Qrntn_Persist> <Qrntn_Def> <Sign_OnOff> <Prov_Resp> <RspAck_Attr> <Disc_Proc> <Cancel_Graceful>|Replace the above values with the values listed in Table 9-14.
The following example shows the addition of TGCP 1.0 protocol to redundancy group 1.
PXM1E_SJ.1.28.VISM8.a > addmgcgrpprotocol 1 6 1 1 2 1 1 1 1
Step 3
Step 4
nodename.1.28.VISM8.a > dspmgcgrpprotocolsMgcGrp Prot Qrntn Qrntn Sign Prov RspAck Disc CancelNum Num Persist Def OnOff Resp Attr Proc Graceful--------------------------------------------------------------------------------------1 TGCP 1.0 Qrtn StepProcess DelNegEvt Send Send Enable SendThe above example shows the default values for TGCP 1.0.
Step 5
nodename.1.28.VISM8.a > delmgcgrpprotocol <Red_Group_Num> <protocol_number>Replace Red_Group_Num with a value of 1-8 and protocol_number with 6:
nodename.1.28.VISM8.a > delmgcgrpprotocol 1 6Configuring the Timers
To configure the timers for TGCP, complete the following steps:
Step 1
nodename.1.20.VISM8.a > cnflongdurationtimer <timeout>Replace the <timeout> argument with a value in the range 0-24 hours.
The following example shows the timeout value configured to 1 hour:
cvgmgx1a.1.20.VISM8.a > cnflongdurationtimer 1
Step 2
nodename.1.20.VISM8.a > dsplongdurationtimerLong duration timer value: 1Step 3
nodename.1.20.VISM8.a > cnfco1timer <timeout>nodename.1.20.VISM8.a > cnfco2timer <timeout>Replace the <timeout> argument with a value in the range 0-60 seconds.
The following example shows that the continuity timer 1 timeout is set to 3 seconds and that the continuity timer 2 is set to 60 seconds:
nodename.1.20.VISM8.a > cnfco1timer 3nodename.1.20.VISM8.a > cnfco2timer 60Step 4
nodename.1.20.VISM8.a > dspco1timerCO1 timer value: 3nodename.1.20.VISM8.a > dspco2timerCO2 timer value: 60Step 5
nodename.1.28.VISM8.a > cnfdisctimers <TdInit> <TdMin> <TdMax>Replace the above arguments with the values listed in Table 9-15.
CALEA
The Commission on Accreditation for Law Enforcement Act (CALEA) feature, used with VoIP applications, provides data (through eavesdropping) about an intercepted subject (the user/subscriber) in two forms for both the receive and transmit directions. The two forms are
•
•
The call identifying data (called number) is provided by call agents. The call content data (voice) is provided by the edge/access routers (Cisco 7200, for example) and trunking gateways (MGX 8000 series platforms) in combination with VISM cards.
The VISM CALEA implementation supports the CALEA law intercept confirmation interface.
To enable the CALEA feature, use the cnfcalea command.
cnfcalea <calea_flag_enable>
Replace the <calea_flag_enable> argument with a value of 1 to enable.
To ascertain whether or not CALEA is enabled, use the dspcalea command.
PXM1E_SJ.1.28.VISM8.a > dspcaleaCALEA : disable
The dspvismparam also shows whether or not CALEA is enabled or disabled.
nodename.1.28.VISM8.a > dspvismparamVISM mode: voipSwitching/voipTrunkingVISM features Bit Map: 0x5bcFunctionModuleType: VISM-PR-8T1CAC flag: enableDS0s available: 192Template number: 2Percent of functional DSPs: 100IP address: 10.10.1.99Subnet mask: 255.255.255.0Bearer IP address: 0.0.0.0Bearer Subnet mask: 0.0.0.0Bearer IP ping: disableRTCP report interval: 5000 msecRTCP receive multiplier: 3RTP receive timer: disableControlPrecedence/Tos: 0x60BearerPrecedence/Tos: 0xa0Aal2 muxing status: disableTftp Server Dn TFTPDOMAINAggregate Clipping enableType <CR> to continue, Q<CR> to stop:Aggregate Svc Bandwidth 0Codec negotiation option 1Profile negotiation option 1VAD Duty Cycle 61VAD Tolerance 100VISM Initiated NW COT OffVISM CO4 Timer 1000 msecCALEA flag disableSupportdModuleType: VISM-PR-8T1.VismNSAP: 470091810000000007856e1363000001070bff00MGC Redundancy
The media gateway controller (MGC) redundancy feature provides redundancy for call agents on VISM cards. You can associate one or more call agents as members of a redundancy group.
An MGC redundancy group consists of one or more MGCs (which are identified by their domain name). An MGC can be part of one redundancy group, and each redundancy group can have multiple MGCs. At any given time, only one MGC in the redundant group is active.
You can add more than one domain name and configure redundant call agents on the same logical MGC. Only the IP addresses corresponding to each physical entity are returned by the DNS server. To allow VISMs to traverse the items identified by all of the IP addresses, you must identify these physical entities as redundant call agents.
You can have a maximum of 8 MGCs configured on the VISM. For more information about configuring MGCs, see "Configuring the Call Agent Interface" section in "VoIP Switching Mode."
External DNS
The external domain name server (DNS) feature allows VISM to use an external DNS to resolve the IP address you configure. The domain names can be for MGCs, call agents, or trivial file transfer protocol (TFTP) servers used for CAS file downloads. Resolution of IP addresses can be configured with the following methods:
•
•
•
•
For configuration information see the VoIP switching chapter.
AAL1 SVC-Based TDM Hairpinning
Hairpinning prevents packet delay by looping the call through the same VISM card instead of going through an external router and back to the VISM card.
The AAL1 SVC operating mode supports TDM hairpinning.
Use the cnfvismmode command to configure VISM operating mode to mode 9.
VoAAL1 switched virtual circuit (SVC) operating mode is supported with the G.711 codec and clear channel.
Note
Note
MGCP 1.0
The following MGCP 1.0 features are supported (in addition to the MGCP 0.1 functionality):
•
–
–
–
•
–
–
–
–
–
–
–
Use the following set of CLI commands in Table 9-16 to configure MGCP.
RSVP-Based Admission Control
Resource Reservation Protocol (RSVP)-based admission control signaling with MGCP is supported, which provides quality VoIP connections. For the connections, the RSVP-MGCP interaction results in the following operations:
•
•
•
•
Note
The following connection data is returned in response to the call agent initiated DLCX and gateway-initiated DLCX or AUCX commands:
•
•
•
•
•
•
Note
•
Use the commands in Table 9-17 to configure the RSVP-based admission control feature.
Local Traffic Grooming
VISM supports the call-agent controlled grooming feature. Grooming allows VISM to avoid routing local traffic through the IP network. Instead, voice packets from a local connection are switched locally in the ATM switch.
A call agent determines if a call needs to be set up as local. To set up a local call, the call agent selects an ATM connection over a VoIP connection. The VISM card, as a gateway, receives the connection request message from the call agent for an ATM connection. The VISM card allows VoIP calls and VoAAL1 SVC calls to coexist and allows provisioning of VoIP and ATM simultaneously.
To use the grooming feature, you must use the cnfvismmode command and select the VoIP and switched ATM AAL1 SVC operating mode. Using this mode does not change any other settings on your card. The type of connection for a call is determined by the connection request (CRCX) received from the call agent or by the bearer type configuration.
Announcement File System
This release allows VISM to play prerecorded local announcements in switched VoIP connections. Under the control of a call agent, announcements can be played toward any IP endpoint or toward any VISM endpoint.
Up to 125 different announcements can be cached on the VISM card for immediate playout. The packet network has a persistent announcement storage area. Announcements are downloaded on demand from the announcement storage area and remain on the VISM card until they have expired or are replaced. If the 125 announcement maximum is reached, subsequent requests for the storage of announcements not on the VISM card result in the replacement of "cached" announcements.
Announcements can be played over established connections in any VISM-supported codec, but they must exist on the announcement file server in the desired encoding.
Note
VISM announcements require the support of the MGCP 0.1/1.0 call agent.
Announcement Timeouts
VISM uses a provisionable timeout value of 5 seconds. If an announcement does not start playing within the timeout period (measured from the point when the request was received), the action is canceled and, if requested by the call agent, an off event is reported. If the call agent specifies a timeout value in the request, this value is ignored.
Announcement Direction
Announcements can be played toward the packet network or toward the TDM network (not both). The direction is determined by the notation of the MGCP S: line. Announcement direction examples:
S: a/ann(all-lines-busy.au)This notation indicates that all-lines-busy.au is to be played toward the TDM network.
S: a/ann@connid(all-lines-busy.au)This notation indicates that all-lines-busy.au is to be played toward the packet network.
Broadcast Announcements
VISM supports announcement requests for a single endpoint or connection. The request may only specify a single announcement to be played on a single endpoint in a single direction. Broadcast announcements are not supported.
Multiple Announcement Requests for the Same Endpoint
If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the same direction), the playing announcement continues and the new announcement request is ignored.
If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the other direction), the playing announcement is stopped and the new announcement is played. Events are not generated for the stopped announcement.
Announcement File Server
Announcements are contained in an announcement file server, which resides on an IP network reachable from the VISM through the use of Trivial File Transfer Protocol (TFTP).
Announcement File Server Name
You can configure the announcement file server node name on the VISM the same way that you configure a node name for the TFTP server.
Announcement File Server Directory Structure
You can use any directory or path on the file server as the main directory for storing announcement files. If you do not provision an announcement path prefix on VISM, the main announcement file directory is the default TFTP directory on the server. If a path prefix is provisioned, this prefix is used as the main announcement directory. If the prefix is not absolute (does not begin with a forward slash (/)), the prefix is understood to be in the default TFTP directory.
You can configure codec subdirectories under the main announcement directory on the announcement file server. A codec subdirectory exists for each codec used for announcement files. The subdirectories can be one or more of the following:
•
•
•
•
•
•
•
•
•
•
When the call agent requests that an announcement be played toward the TDM network on an unconnected endpoint, you can specify the codec to be used.
You can configure another level of directories to group announcement files by language. These directories are specified by the call agent (or when the VISM is being provisioned) as part of the announcement file name. For example, the call agent might specify the announcement file name english/ann1.au. If the file was encoded in G.729a and the prefix was /tftpboot, the file would reside at /tftpboot/g729_a/english/ann1.au.
VISM Announcement Cache Management
VISM manages an announcement cache in resident memory. When an announcement is requested, it is retrieved from the announcement file server and placed in the on-board announcement cache. Subsequent requests for the same announcement do not require retrieval of the announcement file from the announcement file server.
Note
Announcement Expiry
You can provision an announcement aging policy. Once an announcement has aged (reached expiry) in the on-board cache, it is refreshed—retrieved again from the announcement file server. This provides you with the means to balance the cost of file server access with the time before an announcement changed on the file server is propagated to the VISM. In addition, you can delete dynamic files from the announcement cache at any time.
Permanent Announcements
You can provision permanent announcements for VISM. A permanent announcement is retrieved from the announcement file server and installed permanently in the VISM announcement file cache. Permanent announcements are excluded from aging (and being automatically refreshed) and are also excluded from being replaced if the announcement cache becomes full.
Permanent announcements can be removed from the cache explicitly only by the use of a CLI command. If VISM is reset or fails over to a standby card, permanent announcements are retrieved as soon as the card becomes active. The announcement encoding must be specified when permanent announcements are provisioned or deleted.
Use the CLI commands in Table 9-18 to configure the announcement file system feature.
ISDN Backhaul Advanced Configuration
This section describes the advanced ISDN backhaul configurations.
Step 1
nodename.1.28.VISM8.a > cnfsesack <session_num> <acknowledgment_timeout> <acknowledgment>Replace the above arguments with the values listed in Table 9-19.
Step 2
nodename.1.28.VISM8.a > cnfsesmaxreset <session_number> <resets>Replace <session_number> with the value you entered for the session_num argument in Step 1.
Replace <resets> with the maximum number of resets that the VISM card performs before a connection is reset. Range is 0-255. Default is 5.
Step 3
nodename.1.28.VISM8.a > cnfsesmaxseg <session_number> <segment_size>Replace <session_number> with the value you entered in Step 1.
Replace <segment_size> with the maximum segment size, in octets, that can be received by a VISM card after a synchronize message is sent. Range is 30-65535.
Step 4
nodename.1.28.VISM8.a > cnfsesmaxwindow <session_number> <window_size>Replace <session_number> with the value you entered in Step 1.
Replace <window_size> with a value in the range 1-64.
Step 5
nodename.1.28.VISM8.a > cnfsesnullsegtmout <session_number> <timeout>Replace <session_number> with the value you entered in Step 1.
Replace <timeout> with a measure of the idle time allowed before a null segment is sent. Range is 0-65535 ms. Default is 2000 ms.
Step 6
nodename.1.28.VISM8.a > cnfsesoutofseq <session_number> <packets>Replace <session_number> with the value you entered in Step 1.
Replace <packets> with the maximum number of out-of-sequence packets that can be accumulated before an EACK packet is transmitted. Range is 0-255.
Note
Step 7
nodename.1.28.VISM8.a > cnfsesport <session_number> <local_port> <remote_port>Replace the above arguments with the values listed in Table 9-20.
Table 9-20 Parameters for cnfsesport Command
session_number
The value you entered in Step 1.
local_port
Local port number. The VISM port number used for the session. Range is 1124-49151.
remote_port
Remote port number. The call agent port number used for the session. Range is 1124-65535.
Step 8
nodename.1.28.VISM8.a > cnfsesretrans <session_number> <retransmit_timeout> <max_retransmits>Replace the above arguments with the values listed in Table 9-21.
Table 9-21 Parameters for cnfsesretrans Command
session_number
Value you entered in Step 1.
retransmit_timeout
Timeout period (defined in milliseconds) for sending an acknowledgment. Range is 100-65535 ms. Default is 600 ms.
max_retransmits
Maximum number of retransmissions. Range is 0-255. Default is 3.
Step 9
nodename.1.28.VISM8.a > cnfsesstatetmout <session_number> <timeout>Replace <session_number> with the value you entered in Step 1.
Replace <timeout> with the maximum number of milliseconds that VISM waits for a transfer state before executing an auto reset. Range is 0-65535. Default is 2000.
Step 10
nodename.1.28.VISM8.a > cnfsessyncatmps <session_number> <sync_attempts>Replace <session_number> with the value you entered in Step 1.
Replace <sync_attempts> with the maximum number of attempts to synchronize VISM with the call agent. Range is 1-32. Default is 5.
Step 11
You have completed configuring ISDN PRI backhaul.
Advanced LAPD Configuration
This section describes the advanced Link Access Protocol D Channel (LAPD) configurations that are applicable to the VISM/VISM-PR cards.
Step 1
nodename.1.28.VISM8.a > cnflapdwinsize <line_number> <ds0_number> <window_size>Replace the above arguments with the values listed in Table 9-22.
Step 2
nodename.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <N200>Replace the above arguments with the values listed in Table 9-23.
Step 3
nodename.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <timer_T200> <timer_T203>Replace the above arguments with the values listed in Table 9-24.
Diagnostics/Statistics
This section contains the VISM/VISM-PR card configurations for diagnostics and statistics described in the following sections:
•
•
•
•
•
•
Voice Quality Statistics
On the VISM-PR, you can collect real-time voice quality statistics to assist with network analysis and troubleshooting system performance. These statistics are available when a VoIP call connection exists on a DS0.
The following voice quality parameters are reported:
•
•
These statistics are applicable when the VISM-PR card is operating in the VoIP trunking and switching modes.
To display the new jitter and round-trip delay parameters, use the existing dsprtpconnstat command.
cvgmgx1a.1.1.VISM8.a > dsprtpconnstat <endpt_num>Replace the <endpt_num> argument with a value in the following ranges:
•
–
–
•
–
–
•
–
•
–
–
Example 9-13 shows the sample display of the voice quality statistics for endpoint 1.
Example 9-13 Voice Quality Statistics Display
cvgmgx1a.1.1.VISM8.a > dsprtpconnstat 1Endpoint index = 1No. of RTP Packets Sent = 26383402No. of RTP Packets Received = 26383333No. of Octets Sent = 2110672160No. of Octets Received = 2110666640No. of RTP Packets Lost = 72Interarrival Jitter = 0Latency = 125cvgmgx1a.1.1.VISM8.a >When the VISM-PR card receives an out-of-sequence packet, the interarrival jitter value is expected to be large.
If the playout timestamp is not enabled in fixed dejitter buffer mode, the round-trip delay value is expected to have a large deviation from the actual value.
To obtain more accurate round-trip delay values, enable the playout timestamp by using the cnfplayouttimestamp command.
Diagnostic Testing for DSP Failures
When a VISM-PR card detects channel failures on the DSP, the call agent and Cisco WAN Manager (CWM) are informed. In AAL2 trunking mode a trap is generated for a DSP failure.
For DSPs to initiate diagnostics and report any failures to the call agent or CWM, the exec diag, which performs the diagnostic activities, must be enabled. If the exec diag is disabled, DSP failures are not reported.
Enable or Disable Diagnostics
To enable or disable exec diag, use the commands in the following steps.
Note
Step 1
Step 2
nodename.1.28.VISM8.a > cnfexecdiag <execdiag>Replace <execdiag> with a value of 1 to enable or 2 to disable the exec diag on all of the channels.
Step 3
nodename.1.28.VISM8.a > dspexecdiagLineNo/Ds0No DSP Exec Status------------ ---------------1/ 1 Enable1/ 2 Enable1/ 3 Enable1/ 4 Enable1/ 5 Enable1/ 6 Enable1/ 7 Enable1/ 8 Enable1/ 9 Enable1/10 Enable1/11 Enable1/12 Enable1/13 Enable1/14 Enable1/15 Enable1/16 Enable1/17 Enable1/18 Enable1/19 Enable1/20 Enable1/21 Enable1/22 Enable1/23 Enable1/24 EnableINFO: line ds1 '2' is not enabledINFO: line ds1 '3' is not enabledINFO: line ds1 '4' is not enabledINFO: line ds1 '5' is not enabledINFO: line ds1 '6' is not enabledINFO: line ds1 '7' is not enabledINFO: line ds1 '8' is not enabledStep 4
nodename.1.28.VISM8.a > cnflnexecdiag <line_number> <execdiag>Replace <line_number> with the line number, in the range 1-8; replace <execdiag> with a 1 to enable or 2 to disable diagnostics. The following example shows channel diagnostics being enabled on line 1.
nodename.1.28.VISM8.a > cnflnexecdiag 1 1Step 5
nodename.1.28.VISM8.a > dsplnexecdiag 1LineNo/Ds0No DSP Exec Status------------ ---------------1/ 1 Enable1/ 2 Enable1/ 3 Enable1/ 4 Enable1/ 5 Enable1/ 6 Enable1/ 7 Enable1/ 8 Enable1/ 9 Enable1/10 Enable1/11 Enable1/12 Enable1/13 Enable1/14 Enable1/15 Enable1/16 Enable1/17 Enable1/18 Enable1/19 Enable1/20 Enable1/21 Enable1/22 Enable1/23 Enable1/24 EnableStep 6
nodename.1.28.VISM8.a > cnfds0execdiag <line_number> <ds0_number> <execdiag>Replace <line_number> with the line number, in the range 1-8; replace <ds0_number> with a value in the range 1-24 for T1 lines or 1-31 for E1 lines; and replace <execdiag> with a 1 to enable or 2 to disable diagnostics.
Step 7
nodename.1.28.VISM8.a > dspds0execdiag 1 1LineNo/Ds0No DSP Exec Status------------ ---------------1/ 1 EnableConfigure Heartbeat Timer
The DSP has a heartbeat mechanism that sends an "I'm alive and well" message at regular intervals. If a heartbeat does not reach the host, the DSP is considered failed. The host displays the heartbeat messages and the interval at which it receives the messages.
For the DSP to generate a heartbeat message within a specified period of time, the heartbeat timer value must be set on the VISM-PR card. To set that value, complete the following steps:
Step 1
Step 2
nodename.1.28.VISM8.a > cnfdspheartbeattimer <Heart_beat_interval>Replace <Heart_beat_interval> with a timeout value of 0 or a value in the range 100-65535. The recommended timer is 0 (disabled). The following example shows the timeout value of 0.
nodename.1.28.VISM8.a > cnfdspheartbeattimer 0Step 3
nodename.1.28.VISM8.a > dspheartbeattimerDSP Heartbeat timer value: 0History Statistics Collection
Collecting history statistics can assist you with troubleshooting performance issues and fault conditions on the VISM and VISM-PR cards.
The following statistics are collected for a 24-hour duration at 15-minute intervals:
•
•
•
When a particular interval does not contain valid data, the interval is marked as invalid in the Valid Flag field. When the card is reset, all intervals are marked as invalid. When the data for an interval is available, the interval is marked as valid.
Note
An interval can be marked invalid in the Valid Flag field, and the Last Reset Uptime Ticks field can contain a nonzero value. This value indicates a time in ticks when the statistics are cleared by the clrhistorystats command. This time is relative to the time the card is reset.
Also, an interval might be marked as invalid due to a system clock time change or a data collection error.
The statistics are automatically collected and are available for display through the CLI. Some of the statistics are specific to a mode or functionality. For example, statistics with AAL2 in the name are not relevant if the connection is configured as AAL5.
Note
To display the history statistics, complete the following steps:
Step 1
Step 2
nodename.1.5.VISM8.a > dsphistorystats <StatsType> <Interval> <InterfaceIndex> |InterfaceIndex2|Replace the above arguments with the values listed in Table 9-25.
Example 9-14 shows PVC statistics that are collected at interval 0. The display shows the total of all valid interval data available, representing statistics for the previous 24 hours.
Example 9-14 Displaying Statistics Collected Over 24 Hours
nodename.1.5.VISM8.a > dsphistorystats 1 0 13124 Hour Total LCN 131 History Statistics---------------------------------------24 Hour Total ATM Xmt Cells = 1718550024 Hour Total ATM Rcv Cells = 024 Hour Avg Per Sec ATM Xmt Cells = 20024 Hour Avg Per Sec ATM Rcv Cells = 024 Hour Peak Per Sec ATM Xmt Cells = 21924 Hour Peak Per Sec ATM Rcv Cells = 024 Hour Total OAM Xmt End-to-End Lpbk Req Cells = 8549824 Hour Total OAM Rcv End-to-End Lpbk Rsp Cells = 024 Hour Total OAM Xmt Segment Lpbk Cells = 024 Hour Total OAM Rcv Segment Lpbk Cells = 024 Hour Total OAM End-to-End Lpbk Lost Cells = 8549824 Hour Total Discarded Rcv OAM Cells = 024 Hour Total AIS Suppress Cnts = 024 Hour Total Xmt AIS Cnts = 024 Hour Total Rcv AIS Cnts = 024 Hour Total Xmt FERF Cnts = 024 Hour Total Rcv FERF Cnts = 024 Hour Total Xmt AIS Cells = 024 Hour Total Rcv AIS Cells = 024 Hour Total Xmt FERF Cells = 8549824 Hour Total Rcv FERF Cells = 024 Hour Total AAL2 CPS Sent Pkts = 024 Hour Total AAL2 CPS Rcvd Pkts = 024 Hour Total AAL2 HEC Errors = 024 Hour Total AAL2 CRC Errors = 024 Hour Total AAL2 Invalid OSF Cells = 024 Hour Total AAL2 Invalid Parity Cells = 024 Hour Total AAL2 Invalid Cid Pkts = 024 Hour Total AAL2 Invalid UUI Pkts = 024 Hour Total AAL2 Invalid Length Pkts = 024 Hour Total AAL5 PDU Sent Pkts = 024 Hour Total AAL5 PDU RcvdPkts = 024 Hour Total AAL5 Invalid CPI PDUs = 024 Hour Total AAL5 Oversized SDU Rcvd PDUs = 024 Hour Total AAL5 Invalid Length PDUs = 024 Hour Total AAL5 CRC32 Errored PDUs = 024 Hour Total AAL5 Reassembly Timer Expiry PDUs = 0Last Completed Interval Number is 47Number of valid intervals is 95nodename.1.5.VISM8.a >Example 9-15 shows PVC statistics that are collected from the interval 00:15 to 00:30. For the descriptions of the PVC statistics, see Table 9-43.
Example 9-15 Displaying PVC History Statistics
nodename.1.5.VISM8.a > dsphistorystats 1 2 131PVC History Statistics: interval = 2, LCN = 131--------------------------------------------Valid Flag = VALIDLast Reset Uptime Ticks = 0Total ATM Xmt Cells = 180902Total ATM Rcv Cells = 0Avg Per Sec ATM Xmt Cells = 201Avg Per Sec ATM Rcv Cells = 0Peak Per Sec ATM Xmt Cells = 202Peak Per Sec ATM Rcv Cells = 0Total OAM Xmt End-to-End Lpbk Req Cells = 900Total OAM Rcv End-to-End Lpbk Rsp Cells = 0Total OAM Xmt Segment Lpbk Cells = 0Total OAM Rcv Segment Lpbk Cells = 0Total OAM End-to-End Lpbk Lost Cells = 900Total Discarded Rcv OAM Cells = 0Total AIS Suppress Cnts = 0Total Xmt AIS Cnts = 0Total Rcv AIS Cnts = 0Total Xmt FERF Cnts = 0Total Rcv FERF Cnts = 0Total Xmt AIS Cells = 0Total Rcv AIS Cells = 0Total Xmt FERF Cells = 900Total Rcv FERF Cells = 0Total AAL2 CPS Sent Pkts = 0Total AAL2 CPS Rcvd Pkts = 0Total AAL2 HEC Errors = 0Total AAL2 CRC Errors = 0Total AAL2 Invalid OSF Cells = 0Total AAL2 Invalid Parity Cells = 0Total AAL2 Invalid Cid Pkts = 0Total AAL2 Invalid UUI Pkts = 0Total AAL2 Invalid Length Pkts = 0Total AAL5 PDU Sent Pkts = 0Total AAL5 PDU RcvdPkts = 0Total AAL5 Invalid CPI PDUs = 0Total AAL5 Oversized SDU Rcvd PDUs = 0Total AAL5 Invalid Length PDUs = 0Total AAL5 CRC32 Errored PDUs = 0Total AAL5 Reassembly Timer Expiry PDUs = 0Last Completed Interval Number is 42nodename.1.5.VISM8.a >Example 9-16 shows CID history statistics for the interval 00:00 to 00:15 on CID 8 with LCN 131. For descriptions of the CID statistics, see Table 9-44.
Example 9-16 Displaying CID History Statistics
nodename.1.5.VISM8.a > dsphistorystats 2 1 131 8CID History Statistics: interval = 1, LCN = 131, CID = 8--------------------------------------------------------------Valid Flag = VALIDLast Reset Uptime Ticks = 0Total Avg Per Second Sent Pkts = 201Total Avg Per Second Rcvd Pkts = 0Total Sent Pkts = 180976Total Rcvd Pkts = 0Total Sent Octets = 7748631Total Rcvd Octets = 0Total Sent Peak Per Second Pkts = 202Total Rcvd Peak Per Second Pkts = 0Total Ext AIS Rcvd Pkts = 0Total Ext RAI Rcvd Pkts = 0Total Ext Conn AIS Rcvd Pkts = 0Total Ext Conn RDI RcvdPkts = 0Total Ext AIS Rcv Cnts = 0Total Ext RAI Rcv Cnts = 0Total Ext Conn AIS Cnts = 0Total Ext Conn RDI Cnts = 0Total Ext AIS Xmt Cnts = 0Total Ext RAI Xmt Cnts = 0Last Completed Interval Number is 45nodename.1.5.VISM8.a >
Step 3
nodename.1.5.VISM8.a > clrhistorystats <StatsType> <Hours> <InterfaceIndex> |InterfaceIndex2|Replace the above arguments with the values listed in Table 9-26. The clrhistorystats command invalidates the intervals. The actual statistics are not cleared, but the 24-hour total statistics are cleared.
Display ATM Statistics
To display the real-time ATM statistics, use the dspconcnt command. Example 9-17 shows sample output from the dspconcnt command.
Example 9-17 Displaying ATM Statistics
nodename.1.5.VISM8.a > dspconcnt 131ChanNum: 131Chan State: okayChan XMT ATM State: NormalChan RCV ATM State: NormalChan Status Bit Map: 0x0OAM Lpb Lost Cells: 0AAL2 HEC Errors: 0AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 0AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 0AAL2 CPS Packet Rcv: 0AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0AAL5 PDU Packet Xmt: 0AAL5 PDU Packet Rcv: 0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0AIS Successful Suppression Count: 0AIS Alarm Transmitted Count: 0AIS Alarm Received Count: 0FERF Alarm Transmitted Count: 0FERF Alarm Received Count: 0Chan 24 Hr Peak Xmt Cell Rate(CPS): 0Chan Current Xmt Cell Rate (CPS): 0Chan 24 Hr Peak Rcv Cell Rate(CPS): 0Chan Current Rcv Cell Rate (CPS): 0Display Cells Per Second
To display CPS usage, use the commands listed in the following steps:
Step 1
Step 2
nodename.1.5.VISM8.a > dspcidcps <LCN>Replace <LCN> with a value in the range 131-510.
Example 9-18 shows the cell rates for LCN 131.
Example 9-18 Displaying CPS for a Connection
nodename.1.5.VISM8.a > dspcidcps 131LCN CID Endpt 24Hr Peak Xmit 24Hr Peak Rcv Current Xmit Current RcvNum Num Num cell Rate(CPS) cell Rate(CPS) Cell Rate(CPS) Cell Rate(CPS)--- --- ----- -------------- -------------- -------------- --------------131 8 1 204 201Step 3
nodename.1.5.VISM8.a > dsplncidcps <line_number>Replace the <line_number> argument with the line number in the range 1-8.
Example 9-19 shows CPS usage for line 1.
Example 9-19 Displaying CPS Usage for All CIDs on a Line
nodename.1.5.VISM8.a > dsplncidcps 1LCN CID Endpt 24Hr Peak Xmit 24Hr Peak Rcv Current Xmit Current RcvNum Num Num cell Rate(CPS) cell Rate(CPS) Cell Rate(CPS) Cell Rate(CPS)--- --- ----- -------------- -------------- -------------- --------------131 8 1 219 201Step 4
nodename.1.5.VISM8.a > dspmngcidcnt <endpt_num>Replace <endpt_num> with one of the following values:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Example 9-20 shows sample output for endpoint number 1.
Example 9-20 Displaying Managed CID Cell Rates
nodename.1.5.VISM8.a > dspmngcidcnt 1EndptNum: 1Lcn: 131Cid: 11SentPkts: 0RcvdPkts: 0SentOctets: 8RcvdOctets: 8LostPkts: 0Jitter: 0Latency: 0Ext AIS Rcvd: 0Ext RAI Rcvd: 0Ext Conn AIS Rcvd: 0Ext Conn RDI Rcvd: 0Ext AIS Rcvd Cnt: 0Ext RAI Rcvd Cnt: 0Ext Conn AIS Rcvd Cnt: 0Ext Conn RDI Rcvd Cnt: 0Ext Conn AIS Xmit Cnt: 0Ext Conn RAI Xmit Cnt: 124Hr Peak Xmt Cell Rate (CPS): 204Type <CR> to continue, Q<CR> to stop:Current Xmt Cell Rate (CPS): 20124Hr Peak Rcv Cell Rate (CPS): 0Current Rcv Cell Rate (CPS): 0Static and Real-Time Configuration Display
To troubleshoot VISM/VISM-PR issues, you can use the dspall command to display static configurations, run-time statistics, and real-time dynamic data.
The dspall command is available in all operating modes. This command displays all of the individual display command data for each operating mode. The display data differs depending on the mode.
Use dspall -config to display only the static configurations. Use dspall -runtime to display the static configurations, run-time statistics, and real-time dynamic data.
Example 9-21 shows a sample of static data from the dspall -config command in the AAL2 trunking mode.
Example 9-21 Display Static Data
nodename.1.28.VISM8.a > dspall -config-------------------- Displaying Card Level Configuration --------------------dspaal2params---------------AAL2 DTMF RELAY: OffAAL2 CAS BITS TRANSPORT: OffAAL2 TYPE3 REDUNDANCY: OnAAL2 VAD TIMER: 250AAL2 CID FILL TIMER: 30dspaissuppression---------------ConnId ChanNum AIS Suppression Status AIS Delay Time------ ------- ---------------------- --------------milwwi03.17.1.0.131 131 DISABLED 30milwwi03.17.1.0.132 132 DISABLED 30dspcarddsp---------------IdlePattern: 54IdleDirection: BothPacketSize: 80 bytesDB loss: sixdbJitter buffer mode: fixedJitter buffer size: forty msecAdaptive Gain Control: offExample 9-22 shows sample of real-time data using the dspall -runtime command in the AAL2 trunking mode.
Example 9-22 Display All Run-time Data
nodename.1.28.VISM8.a > dspall -runtime-------------------- Displaying Card Level Runtime Configuration --------------------dspcacfailcntrs---------------PVC Addition Failures: 0SVC Addition Failures: 0VC CAC Failures for PVCs: 0PVC Upspeed Failures: 0SVC Upspeed Failures: 0-------------------- Displaying PVC Level Runtime Configuration --------------------dspconcnt 131---------------ChanNum: 131Chan State: okayChan XMT ATM State: NormalChan RCV ATM State: NormalChan Status Bit Map: 0x0OAM Lpb Lost Cells: 122AAL2 HEC Errors: 0AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 0AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 26732AAL2 CPS Packet Rcv: 5245AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0Chan 24Hr Peak Xmt Cell Rate (CPS): 2082Chan Current Xmt Cell Rate (CPS): 120Chan 24Hr Peak Rcv Cell Rate (CPS): 58Chan Current Rcv Cell Rate (CPS): 51AAL5 PDU Packet Xmt: 0AAL5 PDU Packet Rcv: 0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0AIS Successful Suppression Count: 0AIS Alarm Transmitted Count: 0AIS Alarm Received Count: 0FERF Alarm Transmitted Count: 7FERF Alarm Received Count: 5dspsarcnt 141---------------SarShelfNum: 1SarSlotNum: 4SarChanNum: 141Tx Rx------------------- ---------------Total Cells: 36564 5370Total CellsCLP: 0 0Total CellsAIS: 0 0Total CellsFERF: 47 17Total CellsEnd2EndLpBk: 342 241Total CellsSegmentLpBk: 0 0RcvCellsDiscOAM: 0dspslipcnt 1---------------Line 1 Slip Counters: Tx Slip Rx Slip--------- ---------Uncontrolled Slip: 0 0Frame Slip: 0 136The following sections list the display commands that are applicable to the dspall -config and the dspall -runtime commands. For more information on these commands, see Chapter 10, "CLI Commands.".
VoIP Switching/VoIP Trunking
In the VoIP switching/VoIP trunking (mode 1), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-27.
In addition to the data from the commands listed in Table 9-27, the dspall -runtime command shows the run-time data listed in Table 9-28.
AAL2 Trunking
In the AAL2 trunking (mode 2), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-29.
In addition to the data from the commands listed in Table 9-29, the dspall -runtime command shows the run-time data listed in Table 9-30.
AAL1 Switching
In the AAL1 switching (mode 3), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-31.
In addition to displaying the data from the commands listed in Table 9-31, the dspall -runtime command shows the run-time data listed in Table 9-32.
Switched AAL2 SVC
In the switched AAL2 SVC (mode 7), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-33.
In addition to displaying the data from the commands listed in Table 9-33, the dspall -runtime command shows the run-time data listed in Table 9-34.
Switched AAL2 PVC
In the switched AAL2 PVC (mode 8), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-35.
In addition to displaying the data from the commands listed in Table 9-35, the dspall -runtime command shows the run-time data listed in Table 9-36.
VoIP and AAL1 SVC
In the VoIP and AAL1 SVC mode 9, issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-37.
In addition to displaying the data from the commands listed in Table 9-37, the dspall -runtime command shows the run-time data listed in Table 9-38.
VoIP Trunking/AAL2 Trunking
In the VoIP trunking/AAL2 trunking (mode 10), issuing the dspall -config command shows the static configuration data from the commands listed in Table 9-39.
In addition to displaying the data from the commands listed in Table 9-39, the dspall -runtime command shows the run-time data listed in Table 9-40.
Trap Filtering
When the VISM-PR card is initially configured, many traps are sent to Cisco WAN Manager (CWM) that could lower CWM performance. To reduce the load on CWM, you can filter the VISM-PR traps while the card is being configured. After the VISM-PR is configured, you can disable the trap filtering feature, so CWM can be in sync with the card.
By default the trap filtering feature is disabled.
To display either all the traps or traps per group on the card, use the dsptraphelp command. This command can be used to help you obtain trap number information that you need to add trap filters.
nodename.1.28.VISM8.a > dsptraphelp <trapHelpOpt>Replace the <trapHelpOpt> argument with one of the following values of the trap group:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Example 9-23 shows the list of the card traps.
Example 9-23 Displaying Trap Help
nodename.1.28.VISM8.a > dsptraphelp 2TrapNumber TrapDescription========== ===============50680 TRAP_AVAIL_FREE_DS0_LOW50681 TRAP_CPU_UTIL_EXCEEDED50682 TRAP_MEM_UTIL_EXCEEDED50687 TRAP_CALL_THROTTLE_THRESHOLD_90_PERCENT50688 TRAP_CALL_THROTTLE_THRESHOLD_EXCEEDED50689 TRAP_CALL_THROTTLE_THRESHOLD_90_PERCENT_CLEARED50690 TRAP_CALL_THROTTLE_THRESHOLD_EXCEEDED_CLEARED50691 TRAP_FILTER_ON50692 TRAP_FILTER_OFF50693 TRAP_FILTER_ADDED50694 TRAP_FILTER_REMOVED50695 TRAP_FILTER_MODIFIED50700 TRAP_VISMIP_CHANGED50743 TRAP_VISM_CODECTEMPLATE_CHG50744 TRAP_VISM_MODE_CHG50745 TRAP_VISM_SCALAR_CHANG50746 TRAP_VISM_TABLE_CHANG50760 TRAP_VISM_SUBCELL_MUXING_CHANG50790 TRAP_VISM_FEATURE_CHGFor a list of the traps and traps numbers for each group, see "VISM-PR Traps."
Configure Trap Filtering
To configure trap filtering on the VISM-PR card, complete the following steps:
Step 1
Step 2
nodename.1.28.VISM8.a > cnftrapfilterfeature <trapFilteringEn>Replace the <trapFilteringEn> argument with one of the following values:
•
•
Example 9-24 shows the command to enable trap filtering.
Example 9-24 Configuring Trap Filtering
nodename.1.28.VISM8.a > cnftrapfilterfeature 1nodename.1.28.VISM8.a >Step 3
nodename.1.28.VISM8.a > addtrapfilter <trapNumber> |<trapFilterTimer>|Replace the <trapNumber> argument with a trap value in the range 50650-50799.
Replace the optional |trapFilterTimer| argument with a trap filter timer value in the range 0-65536 minutes. A value of 0 indicates forever. If this argument is not specified, a default value of 15 minutes is used.
Example 9-25 shows the command to add to the filter list the card trap TRAP_AVAIL_FREE_DS0_LOW with a 20-minute interval.
Example 9-25 Adding a Trap to the Filter List
nodename.1.28.VISM8.a > addtrapfilter 50680 20nodename.1.28.VISM8.a >Step 4
nodename.1.28.VISM8.a > deltrapfilter <trapNumber> |<trapNumber> <trapNumber> <trapNumber> <trapNumber>|Replace the <trapNumber> argument with trap numbers in the range 50650-50799. Use the optional <trapNumber> arguments to delete up to five traps from the trap filter list.
Example 9-26 shows the command to delete the card trap TRAP_CPU_UTIL_EXCEEDED from the filter list.
Example 9-26 Deleting a Trap from the Filter List
nodename.1.28.VISM8.a > deltrapfilter 50681nodename.1.28.VISM8.a >Step 5
nodename.1.28.VISM8.a > delalltrapfiltersThis command does not have any arguments.
Step 6
nodename.1.28.VISM8.a > cnftrapfiltertimer <trapFilterTimer> |<trapNumber> <trapNumber> <trapNumber> <trapNumber> <trapNumber>Replace the <trapFilterTimer> argument with the timer value for the trap filter in the range 0-65536 minutes. A value of 0 indicates forever.
Replace the optional <trapNumber> arguments with trap numbers in the range 50650-50799. If these values are not specified, all traps in the filter list take the new timer value. A maximum of five trap numbers can be specified at one time.
Example 9-27 shows the command to configure a timer value of 15 minutes for the card traps TRAP_MEM_UTIL_EXCEEDED and TRAP_AVAIL_FREE_DS0_LOW.
Example 9-27 Configuring Trap Filter Timer
nodename.1.28.VISM8.a > cnftrapfiltertimer 15 50682 50680nodename.1.28.VISM8.a >Step 7
nodename.1.28.VISM8.a > dsptrapfilter <trapNumber> |<trapNumber> <trapNumber> <trapNumber> <trapNumber>|Replace the <trapNumber> argument with trap numbers in the range 50650-50799. Use the optional <trapNumber> arguments to display the details for up to five traps.
Example 9-28 shows the details for card traps TRAP_AVAIL_FREE_DS0_LOW and TRAP_MEM_UTIL_EXCEEDED.
Example 9-28 Displaying Trap Details
nodename.1.28.VISM8.a > dsptrapfilter 50680 50682Trap Filtering Feature: EnabledTrapNumber Filter Time Configured(minutes) Filter Time Left(minutes)========== =============================== ========================50680 15 1350682 15 13nodename.1.28.VISM8.a >Step 8
nodename.1.28.VISM8.a > dspalltrapfiltersThis command does not have any arguments.
Example 9-29 shows the filter times for the all of the trap filters on the VISM-PR card.
Example 9-29 Displaying All Trap Filters
nodename.1.28.VISM8.a > dspalltrapfiltersTrap Filtering Feature: EnabledTrapNumber Filter Time Configured(minutes) Filter Time Left(minutes)========== =============================== ========================50680 15 1450681 15 1550682 15 14nodename.1.28.VISM8.a >VISM-PR Bulk Statistics Upload to CWM
Statistics provide a history of network monitoring over a period of time. You can upload history statistics collected on a VISM-PR card to CWM.
Statistics are collected periodically on the VISM-PR card and are written to statistics files. Statistics files are transferred or uploaded to network management stations through FTP.
You can enable VISM-PR statistics with the CWM GUI. For information about how to enable statistics with CWM, refer to the "Collecting Statistics" section of the Cisco WAN Manager User's Guide, Release 15.
To view the general status of the statistics upload functionality by means of the VISM-PR CLI, use the dspstatparms command. This command is applicable in all operating modes.
Example 9-30 shows the sample output of the dspstatparms command. This command does not take any arguments.
Example 9-30 Statistics Upload Output
nodename.1.28.VISM8.a > dspstatparmsTFTP Retry Count: 1TFTP ACK time-out (sec): 60Bucket Interval: 15File Interval: 15Peak Enable Flag: DisabledObject Count: 2 STATS COLLECTION: EnabledObject Subtype Counts: 2 2 0 0Total File Memory Used: 8685Number of File Allocated: 5Current File Size: 123176Stat Memory Allocated: 96832Auto Memory Allocated: 105517Auto Mem Rgn Size: 5242880The results from the dspstatparms command also include the list of statistics you have enabled using CWM. The next sections discuss three categories of statistics that are collected by the VISM-PR card:
Line Statistics
Table 9-41 lists the T1 line statistics that are collected by the VISM-PR card.
Table 9-42 lists the E1 line statistics that are collected by the VISM-PR card.
ATM Connection Statistics
Table 9-43 lists the permanent virtual circuit (PVC) statistics that are collected by the VISM-PR card.
CID Statistics
Table 9-44 lists the CID statistics that are collected by the VISM-PR card.
RTP Connection Statistics
Real-Time Transport Protocol (RTP) connection statistics are collected for individual endpoints and sent to the call agent. Use the new dsprtpconnstat command to display collected RTP connection statistics.
Jitter delay data collection at call completion is on a per call basis. Jitter delay data, number of packets sent and received, and number of octets sent and received are reported to the call agent through MGCP.
Clock Slip Counters
The clock counter information feature allows you to clear the current frame slip counters for a specified VISM or VISM-PR card line and display the current frame slip counters for a specified VISM or VISM-PR card line. Use the clrslipcnt and dspslipcnt commands to work with this feature.
Channel Alarm Enhancement
The channel alarm enhancement feature uses the modified dspconcnt command, which allows you to view the channel status bit map data.
VISM TDM Line Statistics Collection
This release allows you to configure VISM to collect time division multiplexing (TDM) line statistics. Use the dspalmcnt command to collect and display TDM line statistics. Use the cnfalmcnt command to configure the thresholds for TDM line statistics.
Loopbacks for Lines and Connections
To diagnose problems on lines and connections, you can set lines, DS0s, and connections for the loopback state.
Step 1
nodename.1.28.VISM8.a > addlnloop <line_number>Replace <line_number> with the line in which you want the local loopback, in the range 1-8.
Use the dellnloop command to remove the local loopback state on a VISM/VISM-PR line.
Note
Step 2
nodename.1.28.VISM8.a > addendptloop <endpt_num>Replace <endpt_num> with one of the following values:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Step 3
nodename.1.28.VISM8.a > cnfds0loop <line_number> <ds0_number> <lineloopback_type>Replace the above arguments with the values listed in Table 9-45.
Step 4
nodename.1.28.VISM8.a > addconloop <LCN>Replace <LCN> with a value in the range 131-510.
Note
TDM Features
This section contains the VISM/VISM-PR TDM features described in the following sections:
•
•
•
•
•
E1 CAS Idle Code Configuration
When VISM/VISM-PR is configured for E1 CAS transport in AAL2 trunking mode, the default idle signaling pattern is 13.
This section contains the following topics:
•
•
Idle Code Configuration
You can change the default idle ABCD CAS code on an endpoint basis on the VISM/VISM-PR E1 cards. ABCD refers to the robbed-bit signaling bits that are sent in CAS lines.
Step 1
Step 2
Step 3
Note
nodename.1.14.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> |endpts_num|Replace the arguments with the values listed in Table 9-46.
The following example shows the idle CAS code as 4 on endpoints 1-6. Seized code is not used for AAL2 trunking.
nodename.1.14.VISM8.a > cnfcascode 1 4 6 5NOTE:In order for VISM card to use the new Idle Code :Either Reset the Card OR re-add the CidsStep 4
nodename.1.14.VISM8.a > dspds0cascode <line_number> <ds0_number>Replace the line_number argument with a value in the range 1-8 and ds0_number with a value in the range 1-24 for T1 lines or 1-31 for E1 lines.
The following example shows the idle CAS code on endpoint 1 that you configured in Step 3.
nodename.1.14.VISM8.a > dspds0cascode 1 1Ds1 line number: 1ds0 number: 1Ds0 If Index: 1Ds0 Idle Code : 4Ds0 Seized Code: 6Step 5
nodename.1.14.VISM8.a > dsplndsx0s <line_number>The following example shows the idle code you configured using the cnfcascode command on line 2.
nodename.1.14.VISM8.a > dsplndsx0s 1Ds0 If Robbed Bit Idle Seized EndPt If Variant Cadence CadenceIndex Signaling Code Code Num Type Name OnTime OffTime------ ---------- ----- ------- ------ -------------- --------- -------- --------1 False 4 6 1 bearer 75 752 False 4 6 2 bearer 75 753 False 4 6 3 bearer 75 754 False 4 6 4 bearer 75 755 False 4 6 5 bearer 75 756 False 4 6 6 bearer 75 757 False 2 4 7 bearer 75 758 False 2 4 8 bearer 75 759 False 2 4 9 bearer 75 7510 False 2 4 10 bearer 75 7511 False 13 15 -1 - 75 7512 False 13 15 -1 - 75 7513 False 13 15 -1 - 75 7514 False 13 15 -1 - 75 7515 False 13 15 -1 - 75 7516 False 13 15 -1 - 75 7517 False 13 15 -1 - 75 7518 False 13 15 -1 - 75 7519 False 13 15 -1 - 75 7520 False 13 15 -1 - 75 7521 False 13 15 -1 - 75 7522 False 13 15 -1 - 75 7523 False 13 15 -1 - 75 7524 False 13 15 -1 - 75 7525 False 13 15 -1 - 75 7526 False 13 15 -1 - 75 7527 False 13 15 -1 - 75 7528 False 13 15 -1 - 75 7529 False 13 15 -1 - 75 7530 False 13 15 -1 - 75 7531 False 13 15 -1 - 75 75Step 6
CAS Code Sent When a CID is Added
If the local end CID is added first, the VISM/VISM-PR continues to provide the configured idle code on the DS0 (TDM interface) until the remote AAL2 CID is added and starts sending CAS traffic over the ATM network.
If the local end CID is added after the remote end CID is added, the VISM/VISM-PR is already receiving a CAS pattern from the remote AAL2 CID. The VISM/VISM-PR begins propagating the received signaling code on the line side (TDM interface).
Note
CAS Code Sent When a CID is Deleted
If the remote end AAL2 CID is deleted first, the VISM/VISM-PR continues to send the last received CAS pattern from the remote CID to the line side (TDM interface).
If the local end CID is deleted first, the VISM/VISM-PR sends the idle code (configured on this endpoint) to the line side (TDM interface).
Programmable Tone Plans
You can provision a tone plan in a CAS independent scenario so that any inband call progress tone can be played on any endpoint (CAS, CCS, or clear channel).
Example 9-31 contains the built-in (preconfigured) version 1 tone plans, which you cannot modify or remove from the system. You can obtain the list of these tone plans by using the dsptonebuiltinplans command.
Example 9-31 Built-in (Preconfigured) Tone Plans
PXM1E_SJ.1.28.VISM8.a > dsptonebuiltinplansStatus Tone Plan Region Version Tone Plan File Name--------- ----------------------------------- ------ -------------------------configure ITU1 1 1 BUILTINconfigure NorthAmerica 1 BUILTINconfigure Argentina 1 BUILTINconfigure Australia 1 BUILTINconfigure Austria 1 BUILTINconfigure Belgium 1 BUILTINconfigure Brazil 1 BUILTINconfigure Canada 1 BUILTINconfigure China 1 BUILTINconfigure Cyprus 1 BUILTINconfigure CzechRepublic 1 BUILTINconfigure Denmark 1 BUILTINconfigure Finland 1 BUILTINconfigure France 1 BUILTINconfigure Germany 1 BUILTINconfigure Greece 1 BUILTINconfigure HongKong 1 BUILTINconfigure Hungary 1 BUILTINconfigure Iceland 1 BUILTINconfigure India 1 BUILTINconfigure Indonesia 1 BUILTINconfigure Ireland 1 BUILTINconfigure Israel 1 BUILTINconfigure Italy 1 BUILTINconfigure Japan 1 BUILTINconfigure KoreaRepublic 1 BUILTINconfigure Luxembourg 1 BUILTINconfigure Malaysia 1 BUILTINconfigure Mexico 1 BUILTINconfigure Netherlands 1 BUILTINconfigure NewZealand 1 BUILTINconfigure Norway 1 BUILTINconfigure Philippines 1 BUILTINconfigure Poland 1 BUILTINconfigure Portugal 1 BUILTINconfigure Russia 1 BUILTINconfigure Singapore 1 BUILTINconfigure Slovakia 1 BUILTINconfigure Slovenia 1 BUILTINconfigure SouthAfrica 1 BUILTINconfigure Spain 1 BUILTINconfigure Sweden 1 BUILTINconfigure Switzerland 1 BUILTINconfigure Taiwan 1 BUILTINconfigure Thailand 1 BUILTINconfigure Turkey 1 BUILTINconfigure UnitedKingdom 1 BUILTINconfigure UnitedStates 1 BUILTINYou can configure provisional tone plans if the built-in tone plans do not meet your application needs. To create a provisional tone plan assign new region/country, version, and file names, and configure the following call progress tones:
•
•
•
•
•
•
Call Progress Tones
In a VoIP network, a call agent can originate a call to an analog network. The call supervision information from the analog switch might be sent back as special information tones. A voice gateway can detect the subscriber line tones and pass the tones to the remote gateway as telephony events.
This section contains the following topics:
•
The VISM-PR detects a subset of commonly used call progress tones and reports these tones to the call agent. Table 9-47 lists the supported call progress tones.
Table 9-47 Call Progress Tones
Ringing
70
Special Ringing
71
Busy
72
Congestion
73
Special Information
74
These tones are applicable only to a VISM-PR card with PXM1, PXM1E, or PXM45 processor cards. The tones are only supported in VoIP switching mode.
Note
Although the NTE is sent regardless of the codec, we recommend that you use codec G.711u. Using any codec other than G.711u can cause distortion in the in-band propagated tone on the other end.
The call progress tones are supported on all of the templates.
Default Values
This section contains the VISM-PR default values for each of the call progress tones. We recommend that you use these values for configuration.
Dual Tones
This section contains the recommended values for the four dual tones:
•
•
•
•
When the two frequency components of a dual-frequency tone are less than 60 Hz apart, the frequency pair must be configured according to the following formula:
frequency pair (F1 + F2)/2, 0
For example, suppose that the ring-back tone has the following frequency components: F1= 440 Hz and F2 = 480 Hz. The frequency must be configured as Freq1 = 460, Freq2 = 0.
The cadences of the tones are used to differentiate between tones that have overlapping frequencies.
Note
Example 9-32 shows the values for the ring-back tone.
Example 9-32 Ring-back Tone
nodename.1.28.VISM8.a > dspdualtonedet 1Tone Index: 1Event Number: 70Freq1: 460 HzFreq2: 0 HzOncadence: 2000 msOffCadence: 4000 msCadenceMatch: 1FreqMaxDeviation: 30 HzToneMaxPower: -3 dBToneMinPwr: -35 dBTonePwrTwist: 10FreqMaxDelay: 100 msMinOnCadence: 200 msMaxOffCadence: 4500 msExample 9-33 shows the values for the special ring-back tone.
Example 9-33 Special ring-back Tone
nodename.1.28.VISM8.a > dspdualtonedet 2Tone Index: 2Event Number: 71Freq1: 460 HzFreq2: 0 HzOncadence: 1000 msOffCadence: 3000 msCadenceMatch: 1FreqMaxDeviation: 30 HzToneMaxPower: -3 dBToneMinPwr: -35 dBTonePwrTwist: 10FreqMaxDelay: 100 msMinOnCadence: 200 msMaxOffCadence: 4500 msExample 9-34 shows the values for the busy tone.
Example 9-34 Busy Tone
nodename.1.28.VISM8.a > dspdualtonedet 3Tone Index: 3Event Number: 72Freq1: 480 HzFreq2: 620 HzOncadence: 500 msOffCadence: 500 msCadenceMatch: 1FreqMaxDeviation: 30 HzToneMaxPower: -3 dBToneMinPwr: -35 dBTonePwrTwist: 10FreqMaxDelay: 100 msMinOnCadence: 200 msMaxOffCadence: 4500 msExample 9-35 shows the values for the Congestion tone.
Example 9-35 Congestion Tone
nodename.1.28.VISM8.a > dspdualtonedet 4Tone Index: 4Event Number: 73Freq1: 480 HzFreq2: 620 HzOncadence: 250 msOffCadence: 250 msCadenceMatch: 1FreqMaxDeviation: 30 HzToneMaxPower: -3 dBToneMinPwr: -35 dBTonePwrTwist: 10FreqMaxDelay: 100 msMinOnCadence: 200 msMaxOffCadence: 4500 msSpecial Information Tone
The following values are recommended for a sequential tone.
nodename.1.28.VISM8.a > dspseqtonedetseqToneNumOfFrequencies 3seqToneEventID 74seqToneDurationOfEachTone 330 msseqToneGapBetweenEachTone 10 msseqToneDurationDeviation 20 msseqToneMaximumGapDuration 150 msseqToneGapDurationDeviation 20seqToneFreqDeviation 40 HzseqTonePowerLevelCeiling -3 dBseqTonePowerLevelFloor -35 dBseqToneFrequency1 950 HzseqToneFrequency2 1400 HzseqToneFrequency3 1800 HzseqToneFrequency4 280 HzseqToneFrequency5 280 HzseqToneFrequency6 280 HzseqToneFrequency7 280 HzseqToneFrequency8 280 HzseqToneFrequency9 280 HzseqToneFrequency10 280 HzCall Progress Tone Configuration
This section contains the following call progress tone configuration information:
•
Configuring Dual Tones
To add dual tones, complete the following steps:
Step 1
Step 2
nodename.1.28.VISM8.a > adddualtonedet <dttoneId> <dteventId> <dtfreq1> <dtfreq2> <onCadence> <offCadence> |<cadMatch> <maxFreqDev> <maxPwr> <minPwr> <pwrTwist> <maxDelay> <minOnCad> <maxOffCad>|Replace the above arguments with the values listed in Table 9-48.
Note
Step 3
nodename.1.28.VISM8.a > dspdualtonedet <tone_det_num>Replace <tone_det_num> with the dual-tone ID.
nodename.1.28.VISM8.a > dspdualtonedet 1Step 4
PXM1E_SJ.1.28.VISM8.a > deldualtonedet <vismConfigToneDetectNum>
Replace <vismConfigToneDetectNum> with the dual tone-ID.
PXM1E_SJ.1.28.VISM8.a > deldualtonedet 1
Configuring Sequential Tones
A sequential tone is a series of single frequencies. Sequential tones can be configured, but they cannot be deleted.
Note
To change the default settings of a sequential tone, complete the following steps:
Step 1
Step 2
nodename.1.28.VISM8.a > cnfseqtonedet <numfreq> <eventid> <tonedur> <tonegap> <durdev> <maxgap> <gapdev> <freqdev> |<maxpwr> <minpwr>| <freq1>,|<freq2>, <freq3>... <freq10>|Replace the above arguments with the values listed in Table 9-49.
Step 3
PXM1E_SJ.1.28.VISM8.a > dspseqtonedet
Wireless Tones
This release supports the addition of wireless tones to the set of call progress tones. These wireless tones are required for alerts sent to the mobile stations.
VISM-PR supports programmable tones through 48 built-in country tone plans. Also, VISM supports 32 user-defined tones through an external text file that is downloaded through a TFTP server. This feature adds wireless tones to the set of existing tone plans: dial tone, stutter tone, ring-back tone, busy tone, fast busy tone, alert tone.
Wireless tones are supported on the VISM-PR only in the switched VoIP mode. Also, wireless tones are only supported for the TDM interface and for MGC signaling.
This section contains the following topics:
List of Supported Tones
VISM provides the following wireless tones for the built-in tone plans:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Up to 28 additional custom tones are supported for each user-configurable tone plan.
Tone Plan File Description
Tone definitions are specified in ASCII files, one file per tone plan. These files are stored on a TFTP server in the directory /tftpboot.
Example 9-36 shows a tone plan file named UnitedStates_2_tone_plan_file.txt. Descriptions of the fields are listed below the example.
Example 9-36 Tone Plan Definition File
//////////////////////////////////////////////////////////////////////// Comments : Text after `//' through the end of the line are ignored.//////////////////////////////////////////////////////////////////////System Section//////////////////////////////////////////////////////////////////////version 2description "Tone Plan Defined for CompanyX"//////////////////////////////////////////////////////////////////////Tones Section//////////////////////////////////////////////////////////////////////dial_tone 1 14656 0 0 400 0 65535 0 65535stutter_tone 2 4000 4000 0 350 440 100 100 1ring_back_tone 2 3681 3681 0 440 480 2000 4000 1busy_tone 2 2070 2070 45000 480 620 500 500 1fast_busy_tone 2 2070 2070 16000 440 620 250 250 1alert_tone 1 14656 0 45000 400 0 65535 0 1intercept_tone 2 2070 2070 2000 440 620 250 250 1confirmation_tone 1 8241 0 2000 440 0 100 150 1answer_tone 1 8241 0 6000 440 0 100 100 1 440 0 100 900 1call_waiting_tone 1 8241 0 6000 440 0 100 100 1 440 0 100 900 1recall_dial_tone 1 14656 0 45000 400 0 65535 0 1berge_in_tone 1 4634 0 0 1004 0 65535 0 65535ppc_insuffice_tone 1 4000 4000 0 480 0 100 100 3ppc_warn1_tone 1 4000 4000 0 480 0 200 65535 1ppc_warn2_tone 1 4000 4000 0 480 0 100 200 2ppc_warn3_tone 1 4000 4000 0 480 0 100 200 3ppc_disc_tone 1 4000 4000 0 480 0 400 65535 1ppc_redirect_tone 1 4000 4000 0 480 0 200 200 2all_tone_off 1 0 0 0 0 0 65535 0 1 0 0 0 0 0pip_tone 1 14656 0 0 480 0 100 900 1warning_tone 1 4634 0 0 1004 0 65535 0 1denial_tone 1 4634 0 0 1004 0 65535 0 1custom1_tone 1 14656 0 0 480 0 100 900 1 // Click Tonecustom2_tone 1 4634 0 0 1004 0 65535 0 65535 // Milliwatt Tone -20dBmcustom3_tone 1 46348 0 0 1004 0 65535 0 65535 // Milliwatt Tone 0dBmcustom4_tone 1 0 0 0 0 0 65535 0 65535 // Scilence// custom5_tone// custom6_tone// custom7_tone// custom8_tone// custom9_tone// custom10_tone// custom11_tone// custom12_tone// custom13_tone// custom14_tone// custom15_tone// custom16_tone// custom17_tone// custom18_tone// custom19_tone// custom20_tone// custom21_tone// custom22_tone// custom23_tone// custom24_tone// custom25_tone// custom26_tone// custom27_tone// custom28_tonedtmf_digit 16384 16384mf_r1_digit 16384 16384//////////////////////////////////////////////////////////////////////File Name—The name of the tone plan file is restricted to 64 characters.
System Section includes mandatory keywords. Use this section to define tone plans. This section can contain only the following two lines:
•
•
Tones Section includes mandatory keywords. Use this section to define the call progress tones. Specify each tone on a separate line, and use white spaces as delimiters.
The syntax of the tone plan definition file must be specified in the following order and on the same line:
<tone_name> <number_of_freq_components> <amp_of_first> <amp_of_second> <timeout> <freq_1st_cadence1> <freq_2nd_cadence1> <ontime_cadence1> <offtime_cadence1> <repeat_count_cadence1>
[<freq_1st_cadence2> <freq_2nd_cadence2> <ontime_cadence2> <offtime_cadence2> <repeat_count_cadence2>]
[<freq_1st_cadence3> <freq_2nd_cadence3> <ontime_cadence3> <offtime_cadence3> <repeat_count_cadence3>]
[<freq_1st_cadence4> <freq_2nd_cadence4> <ontime_cadence4> <offtime_cadence4> <repeat_count_cadence4>]Table 9-50 lists the mandatory values for defining the call tones.
Table 9-50 Mandatory Values for Defining Tones
tone_name
Identifies the tone as one of the following values:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
number_of_freq_
componentsNumber of frequency components. Use one of the following values:
•
•
amp_of_first1
Peak-to-peak amplitude of the first frequency according to the following formula:
46348 * 10 to the power of (dBm/20)
Value range is 0-65535.
amp_of_second 1
Peak-to-peak amplitude of the second frequency according to the following formula:
46348 * 10 to the power of (dBm/20)
Value range is 0-65535.
timeout
Time when tone generation is stopped. Range is 0-65535 ms.
A value of 0 means no timeout, and thus the tone is stopped explicitly by the call agent.
freq_1st_cadence1
First frequency in cadence 1. Range is 0-3999 Hz.
freq_2nd_cadence1
Second frequency in cadence 1. Range is 0-3999 Hz.
ontime_cadence1
First on time that the tone plays in cadence 1. Range is 0-65535 ms.
offtime_cadence1
First off time that the tone does not play in cadence 1. Range is 0-65535 ms.
repeat_count_cadence1
Repeat count for cadence 1. Range is 1-65535 ms.
1 To specify amplitudes of DTMF and MFR1 tones, you must use the following syntax: dtmf_digit amp-low amp-high or mf_r1_digit amp-low amp-high. The amp-low value = low group frequency. The amp-high value = high group frequency.
Table 9-51 describes the optional parameters you can use to define the tones.
Tone Plan Addition
To add a tone plan to the VISM-PR card, complete the following steps:
Step 1
Note
Step 2
Step 3
nodename.1.28.VISM8.a > adddn <mg_domain_num> <mg_domain_name> |Resolution_Type|This example shows the addition of the TFTP server domain name tftp_server.
nodename.1.28.VISM8.a > adddn 1 tftp_server 1Replace the above values with the values listed in Table 9-52.
Step 4
nodename.1.28.VISM8.a > adddnip <Resolution_index> <DomainName> <IpAddress> <preference>This example shows the addition of the IP address of the TFTP server with the name tftp_server.
nodename.1.28.VISM8.a > adddnip 1 tftp_server 172.29.52.18 1Replace the above arguments with the values listed in Table 9-53.
Step 5
nodename.1.28.VISM8.a > cnftftpdn <domain_name>Replace <domain_name> with the name of your TFTP server. This example shows parameters configured for the server named tftp_server.
nodename.1.28.VISM8.a > cnftftpdn tftp_serverStep 6
Also check that the TFTP functionality is enabled on the TFTP server.
Step 7
nodename.1.28.VISM8.a > addtoneplan <tone_plan_region> <tone_plan_version> <tone_plan_file>The following example shows the addition of the custx2_tone.txt to the United States country tone plan.
nodename.1.28.VISM8.a > addtoneplan UnitedStates 2 custx2_tone.txtTFTP: Transferred file='custx2_tone.txt', size=3108 bytes, sec=0, nsec=80000000Replace the above arguments with the values listed in Table 9-54.
Step 8
nodename.1.28.VISM8.a > dsptoneplansStatus Tone Plan Region Version Tone Plan File Name--------- ----------------------------------- ------ -------------------------configure UnitedStates 2 custx2_tone.txtconfigure ITU 1 BUILTINconfigure NorthAmerica 1 BUILTINconfigure Argentina 1 BUILTINconfigure Australia 1 BUILTINconfigure Austria 1 BUILTINconfigure Belgium 1 BUILTINconfigure Brazil 1 BUILTINconfigure Canada 1 BUILTINconfigure China 1 BUILTINconfigure Cyprus 1 BUILTINconfigure CzechRepublic 1 BUILTINconfigure Denmark 1 BUILTINconfigure Finland 1 BUILTINconfigure France 1 BUILTINconfigure Germany 1 BUILTINconfigure Greece 1 BUILTINconfigure HongKong 1 BUILTINconfigure Hungary 1 BUILTINconfigure Iceland 1 BUILTINconfigure India 1 BUILTINconfigure Indonesia 1 BUILTINconfigure Ireland 1 BUILTINconfigure Israel 1 BUILTINconfigure Italy 1 BUILTINconfigure Japan 1 BUILTINconfigure KoreaRepublic 1 BUILTINconfigure Luxembourg 1 BUILTINconfigure Malaysia 1 BUILTINconfigure Mexico 1 BUILTINconfigure Netherlands 1 BUILTINconfigure NewZealand 1 BUILTINconfigure Norway 1 BUILTINconfigure Philippines 1 BUILTINconfigure Poland 1 BUILTINconfigure Portugal 1 BUILTINconfigure Russia 1 BUILTINconfigure Singapore 1 BUILTINconfigure Slovakia 1 BUILTINconfigure Slovenia 1 BUILTINconfigure SouthAfrica 1 BUILTINconfigure Spain 1 BUILTINconfigure Sweden 1 BUILTINconfigure Switzerland 1 BUILTINconfigure Taiwan 1 BUILTINconfigure Thailand 1 BUILTINconfigure Turkey 1 BUILTINconfigure UnitedKingdom 1 BUILTINconfigure UnitedStates 1 BUILTINTotal number of Tone Plans = 50.Step 9
The following example shows the elements of a tone plan. (Some parts of the example here are truncated.)
nodename.1.28.VISM8.a > dsptoneplan UnitedStates 2Region Name : UnitedStatesVersion : 2Description : Tone Plan defined for CustXFile name : cust2_tone.txtDTMF Amplitude (Low Group) : 16384DTMF Amplitude (High Group) : 16384MF R1 Amplitude (Low Group) : 16384MF R1 Amplitude (High Group) : 16384---------------------------------------------------------------------------Name Defined No.Freq. Amp1 Amp2 Timeout(ms)---------------------------------------------------------------------------dial_tone YES 1 14656 0 0stutter_tone YES 2 4000 4000 0ring_back_tone YES 2 3681 3681 0busy_tone YES 2 2070 2070 45000fast_busy_tone YES 2 2070 2070 16000alert_tone YES 1 14656 0 45000intercept_tone YES 2 2070 2070 2000confirmation_tone YES 1 8241 0 2000answer_tone YES 1 8241 0 6000call_waiting_tone YES 1 8241 0 6000recall_dial_tone YES 1 14656 0 45000berge_in_tone YES 1 4634 0 0ppc_insuffice_tone YES 1 4000 4000 0ppc_warn1_tone YES 1 4000 4000 0ppc_warn2_tone YES 1 4000 4000 0ppc_warn3_tone YES 1 4000 4000 0ppc_disc_tone YES 1 4000 4000 0ppc_redirect_tone YES 1 4000 4000 0all_tone_off YES 1 0 0 0pip_tone YES 1 14656 0 0warning_tone YES 1 4634 0 0denial_tone YES 1 4634 0 0custom1_tone YES 1 14656 0 0custom2_tone YES 1 4634 0 0custom3_tone YES 1 46348 0 0custom4_tone YES 1 0 0 0custom5_tone NO - - - -custom6_tone NO - - - -custom7_tone NO - - - -custom8_tone NO - - - -custom9_tone NO - - - -custom10_tone NO - - - -custom11_tone NO - - - -custom12_tone NO - - - -custom13_tone NO - - - -custom14_tone NO - - - -custom15_tone NO - - - -custom16_tone NO - - - -custom17_tone NO - - - -custom18_tone NO - - - -custom19_tone NO - - - -custom20_tone NO - - - -custom21_tone NO - - - -custom22_tone NO - - - -custom23_tone NO - - - -custom24_tone NO - - - -custom25_tone NO - - - -custom26_tone NO - - - -custom27_tone NO - - - -custom28_tone NO - - - --------------------------------------------------------------------------------Cadence 1 CadeName Freq1 Freq2 OnTm1 OffTm2 Repeat Freq1 Freq2 OnTtHz Hz ms ms count1 Hz Hz ms2-------------------------------------------------------------------------------dial_tone 400 0 65535 0 65535 0 0 0stutter_tone 350 440 100 100 1 0 0 0ring_back_tone 440 480 2000 4000 1 0 0 0busy_tone 480 620 500 500 1 0 0 0fast_busy_tone 440 620 250 250 1 0 0 0alert_tone 400 0 65535 0 1 0 0 0intercept_tone 440 620 250 250 1 0 0 0confirmation_tone 440 0 100 150 1 0 0 0answer_tone 440 0 100 100 1 440 0 11call_waiting_tone 440 0 100 100 1 440 0 11recall_dial_tone 400 0 65535 0 1 0 0 0berge_in_tone 1004 0 65535 0 65535 0 0 0ppc_insuffice_tone 480 0 100 100 3 0 0 0ppc_warn1_tone 480 0 200 65535 1 0 0 0ppc_warn2_tone 480 0 100 200 2 0 0 0ppc_warn3_tone 480 0 100 200 3 0 0 0ppc_disc_tone 480 0 400 65535 1 0 0 0ppc_redirect_tone 480 0 200 200 2 0 0 0all_tone_off 0 0 65535 0 1 0 0 0pip_tone 480 0 100 900 1 0 0 0warning_tone 1004 0 65535 0 1 0 0 0denial_tone 1004 0 65535 0 1 0 0 0custom1_tone 480 0 100 900 1 0 0 0custom2_tone 1004 0 65535 0 65535 0 0 0custom3_tone 1004 0 65535 0 65535 0 0 0custom4_tone 0 0 65535 0 65535 0 0 0custom5_tone - - - - - - - -custom6_tone - - - - - - - -custom7_tone - - - - - - - -custom8_tone - - - - - - - -custom9_tone - - - - - - - -custom10_tone - - - - - - - -custom11_tone - - - - - - - -custom12_tone - - - - - - - -custom13_tone - - - - - - - -custom14_tone - - - - - - - -custom15_tone - - - - - - - -custom16_tone - - - - - - - -custom17_tone - - - - - - - -custom18_tone - - - - - - - -custom19_tone - - - - - - - -custom20_tone - - - - - - - -custom21_tone - - - - - - - -custom22_tone - - - - - - - -custom23_tone - - - - - - - -custom24_tone - - - - - - - -custom25_tone - - - - - - - -custom26_tone - - - - - - - -custom27_tone - - - - - - - -custom28_tone - - - - - - - -TDM Companding Law Configuration
In standard companding law, T1 lines support Mu Law, and E1 lines support A-Law.
VISM-PR supports companding law on the TDM interface. T1 lines support A-Law, and E1 lines support Mu Law.
The support for A-Law and Mu Law on both T1 and E1 lines is typically used when one end of the network has VISM-PR E1 lines connected to the PBX on the TDM side. The other end of the network has VISM-PR T1 lines connected to the PBX on the TDM side. Both the VISM-PR E1 and T1 lines are connected via the ATM cloud through the use of AAL2 channel identifiers (CIDs).
This feature is applicable to VoIP trunking and AAL2 trunking modes.
Configure Companding Law
To configure companding law for a T1 or E1 line, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.5.VISM8.a >cnflncompanding <line_number> <companding>Replace the <line_number> argument with a value in the range 1-8.
Replace the <companding> argument with one of the following values:
•
•
The following example shows the configuring of a VISM-PR E1 line 1 as Mu-Law:
nodename.1.5.VISM8.a >cnflncompanding 1 1Step 4
Step 5
nodename.1.5.VISM8.a >dsplncompanding <line_number>Replace the <line_number> argument with the line number on which you configured companding law in Step 3.
nodename.1.5.VISM8.a >dsplncompanding 1Line/Ds0 Companding-------- ----------1/ 1 U-Law1/ 2 U-Law1/ 3 U-Law1/ 4 U-Law1/ 5 U-Law1/ 6 U-Law1/ 7 U-Law1/ 8 U-Law1/ 9 U-Law1/10 U-Law1/11 U-Law1/12 U-Law1/13 U-Law1/14 U-Law1/15 U-Law1/16 U-Law1/17 U-Law1/18 U-Law1/19 U-Law1/20 U-Law1/21 U-Law1/22 U-Law1/23 U-Law1/24 U-Law1/25 U-Law1/26 U-Law1/27 U-Law1/28 U-Law1/29 U-Law1/30 U-Law1/31 U-LawProgrammable CAS Bit Mapping (ABCD CAS bits)
International connections include both T1 and E1 trunk interfaces. Channel-associated signaling (CAS) bits, ABCD, differ on T1 and E1 interfaces. These CAS bits carry signaling information that describe events, for example off-hook, on-hook, idle, and so forth. Typically, an external device (PBX) is used to map the ABCD signaling bits across the interfaces.
The CAS mapping feature allows you to map the output ABCD bits to input ABCD bits on a signaling channel on the VISM-PR card instead of using a PBX or another external device.
This feature is supported in AAL2 trunking mode.
The VISM-PR stores the CAS mapping information in a table. This table can be downloaded to the transmit and/or receive signaling channel of the endpoint on the TDM line.
Configure CAS Bit Mapping Templates
To create a CAS table and apply it to the appropriate endpoint, complete the following steps:
Step 1
Step 2
Step 3
nodename.1.5.VISM8.a > addcastranstbl <table_name> <format> <abcd0> <abcd1> <abcd2> <abcd3> <abcd4> <abcd5> <abcd6> <abcd7> <abcd8> <abcd9> <abcd10> <abcd11> <abcd12> <abcd13> <abcd14> <abcd15>Replace the above arguments with the values listed in Table 9-55.
The following example shows adding the table, T1andE1trans, with the standard T1 and E1 seize and Idle conversions:
nodename.1.5.VISM8.a > addcastranstbl T1andE1trans 1 9 12 2 3 4 5 6 7 8 0 10 11 1 13 14 1Step 4
nodename.1.5.VISM8.a > dspcastranstbl <table_name>Replace <table_name> with the name of the table you created in Step 3.
The following example shows the CAS bit mapping configurations in table T1andE1trans.
nodename.1.5.VISM8.a > dspcastranstbl T1andE1transCAS translation name = T1andE1trans-------A--B--C--D--------0 1 0 0 11 1 1 0 02 0 0 1 03 0 0 1 14 0 1 0 05 0 1 0 16 0 1 1 07 0 1 1 18 1 0 0 09 0 0 0 010 1 0 1 011 1 0 1 112 0 0 0 113 1 1 0 114 1 1 1 015 0 0 0 1Step 5
nodename.1.5.VISM8.a > dspcastranstblsIndex CasTblName0 E1toT1trans1 T1andE1transStep 6
nodename.1.5.VISM8.a > cnfcastransendpt <endpt_number> <table_name> <direction>Replace the above arguments with the values listed in Table 9-56.
Table 9-56 Parameters for the cnfcastransendpt Command
endpt_number
Endpoint number of which you want to apply the mapping table. Value is one of the following ranges:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
table_name
Name of the table you created in Step 3. Range is 1-64 characters.
direction
Direction to or from the TDM interface where you want to apply the CAS mapping table.
•
•
•
•
The following example shows the T1andE1trans table is applied to endpoint number 1 in the receive and transmit direction:
nodename.1.5.VISM8.a > cnfcastransendpt 1 T1andE1trans 3
The following example shows the E1toT1trans table is applied to endpoint number 2 in the receive direction:
nodename.1.5.VISM8.a > cnfcastransendpt 2 E1toT1trans 2Step 7
nodename.1.5.VISM8.a > dspcastranstblendpts <table_name>Replace <table_name> with the name of the table you created in Step 3.
The following example shows the endpoints associated with the table T1andE1trans:
nodename.1.5.VISM8.a > dspcastranstblendpts T1andE1transendptNum: 1Number of endpoints configured with CAS translation table name:T1andE1trans: 1Step 8
Note
nodename.1.5.VISM8.a > dspcastransendptsEndpt LineNum Ds0Num TX to TDM RX fr TDM Direction----- ------- ------ ------------- ----------- ---------1 1 1 T1andE1trans T1andE1trans bidirectional2 1 2 E1toT1trans none receiveStep 9
nodename.1.5.VISM8.a > delcastranstbl <table_name>Replace <table_name> with the name of the table you want to delete.
Step 10
Step 11
nodename.1.5.VISM8.a > delcastransendpt <endpt_number> |<endpts_num>|Replace <endpt_number> with the endpoint number from which you want to delete the mapping table. This value can also be the first endpoint number of a range of consecutive endpoints. Value is one of the following ranges:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Replace the optional |endpts_num| with the number of endpoints you want to delete. Ranges are
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Line Trunk Conditioning
You can enable and disable trunk conditioning on a T1 and an E1 line.
To enable or disable trunk conditioning on a line, enter the cnflntrunkcond command.
Note
nodename.1.28.VISM8.a > cnflntrunkcond <line_number> <trunkCondType>Replace <line_number> with a value in the range 1-8.
Replace <trunkCondType> with one of the following values:
•
•
If you enable trunk line conditioning, VISM/VISM-PR conditions the affected DS0 when an alarm indication signal (AIS) is detected on the ATM side. Trunk line conditioning consists of transmitting an idle code pattern for 2.5 seconds followed by the seized code specified in the cnfcascode command.
Note
Adjustable Gain
The adjustable gain feature allows you to adjust gain for the input and output signals on a per-DS0 channel basis. The adjustable gain can be set when there is active call going on at the DS0 channel, and at both bounded non-active and unbounded endpoints.
Adjustable Music On-Hold Threshold
The adjustable music on-hold threshold feature allows you to adjust the decibel level, on a DS0 basis, when DSPs interpret silence or voice from the TDM side.
CAS Features
You can configure different CAS packages on different endpoints. The CAS features described in the following sections are supported in this release.
Configuring TDM Side Signaling for Applications Using CAS
Complete the following steps to add and configure CAS for E1.
Step 1
nodename.1.28.VISM8.a > cnfcasparamsource <endpt_num> <ParamSource>Replace the above arguments with the values listed in Table 9-57.
Note
Step 2
nodename.1.28.VISM8.a > cnfcasonhooktime <endpt_num> <OnHookMinTime>Replace the above arguments with the values listed in Table 9-58.
Table 9-58 Parameters for cnfcasonhooktime Command
endpt_num
Type the value used in Step 1.
OnHookMinTime
On-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 300 ms.
Step 3
nodename.1.28.VISM8.a > cnfcasoffhooktime <endpt_num> <OffHookMinTime>Replace the above arguments with the values listed in Table 9-59.
Table 9-59 Parameters for cnfcasoffhooktime Command
endpt_num
Type the value used in Step 1.
OffHookMinTime
Off-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 20 ms.
Step 4
nodename.1.28.VISM8.a > cnfcaswinktime <endpt_num> <WinkMinTime> <WinkMaxTime> <WinkBreakTime>Replace the above arguments with the values listed in Table 9-60.
Table 9-60 Parameters for cnfcaswinktime Command
endpt_num
Type the value used in Step 1.
WinkMinTime
Minimum make duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 100 ms.
WinkMaxTime
Maximum make duration time (defined in milliseconds) of the wink. Range is 10-3000 ms. Default is 1000 ms.
WinkBreakTime
Minimum break duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 20 ms.
A wink is composed of the following sequential events:
1.
2.
3.
Step 5
nodename.1.28.VISM8.a > cnfcasglaretime <endpt_num> <GlareTime>Replace the above arguments with the values listed in Table 9-61.
Table 9-61 Parameters for cnfcasglaretime Command
endpt_num
Type the value used in Step 1.
GlareTime
Glare time (defined in milliseconds). Range is 10-1000 ms. Default is 500 ms.
Step 6
nodename.1.28.VISM8.a > cnfcasguardtime <endpt_num> <GuardTime>Replace the above arguments with the values listed in Table 9-62.
Table 9-62 Parameters for cnfcasguardtime Command
endpt_num
Type the value used in Step 1.
GuardTime
Guard time (defined in milliseconds). Range is 10-1000 ms. Default is 800 ms.
Step 7
nodename.1.28.VISM8.a > cnfcasdialdelay <endpt_num> <DialDelayTime>Replace the above arguments with the values listed in Table 9-63.
Table 9-63 Parameters for cnfcasdialdelaytime Command
endpt_num
Type the value used in Step 1.
DialDelayTime
Wait time (defined in milliseconds) before outpulsing digits are sent to the PBX after an off-hook event. Range is 10-1000. Default is 500.
Dial delay is the time that VISM waits before sending dialing digits after an off-hook event.
Note
Step 8
To configure CAS for the AAL2 trunking operating mode, proceed to Step 9.
Step 9
nodename.1.28.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> |<endpts_num>|Replace the above arguments with the values listed in Table 9-64.
Table 9-64 Parameters for cnfcascode Command
endpt_num
Type the value used in Step 1.
Note
idle_code
The 4-bit idle code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.
seized_code
The 4-bit seized code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.
|endpts_num|
(Optional) The last endpoint in a consecutive range of endpoints. Ranges are
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Step 10
nodename.1.28.VISM8.a > cnfds0localcas <line_number> <ds0_number> <cas_value> <cas_bit_pattern>Replace the above arguments with the values listed in Table 9-65.
The cnfds0localcas command is not applicable if you have one of the following conditions:
•
•
•
Step 11
Note
nodename.1.28.VISM8.a > addcasvar <variant_name> <file_name> |<cas_var_source>|Replace the above arguments with the values listed in Table 9-66.
Step 12
nodename.1.28.VISM8.a > cnfcasvar <variant_name> <country_code> <Tring> <Tpart> <Tcrit> <TMF>Replace the above arguments with the values listed in Table 9-67.
Table 9-67 Parameters for cnfcasvar Command
variant_name
Name of the CAS variant. Type the value used in Step 11.
country_code
Country code of the variant. The value must be a two-character text string.
Tring
Ringing time (defined in seconds). Range is 10-600 sec.
Tpart
Partial dial time (defined in seconds). Range is 10-10000 sec—in increments of 10 sec.
Tcrit
Critical timing (defined in seconds). Range is 0-10000 sec—in increments of 10 sec.
TMF
Interdigit timeout value for MF digits (defined in seconds). Range is 1-10 sec.
Step 13
nodename.1.28.VISM8.a > cnfcasendpt <endpt_number> <casVariantName>Replace the above arguments with the values listed in Table 9-68.
Table 9-68 Parameters for cnfcasendpt Command
endpt_number
Type the value used in Step 9.
casVariantName
Type the value used in Step 11.
Loop Start, DID, and Dial Delay
The exchange side (FXO) of the loop start protocol is implemented with this release. VISM can accept calls from, and terminate calls to, loop start PBXs. When a PBX sends a subscriber call to the gateway, it sends the loop-close signal through the CAS channel. To hang up, it sends the loop-open signal.
Direct inward dial (DID) enables a caller outside a company to call internal extensions without having to go through an operator or an attendant. VISM has this ability—it outpulses the digit stream handed down by the call agent.
Dial delay is an E&M signaling protocol similar to wink start. The originating VISM, on receiving a seize (AB = 11) from the PBX, responds by sending the delay-dial (AB = 11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends a start-dial (AB = 00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB = 11 (as an acknowledgment that the trunk is operational). Subsequently when it receives the start signal (AB = 00) from the connected PBX, it should outpulse the digits. The rest of the operation is similar to wink start.
Feature Group D
Feature Group D (FGD) enables long distance calls through one of the following methods:
•
•
FGD supports the following protocols:
•
•
•
Configure Flash Hook and Glare Condition Attributes
You can configure flash hook and glare condition attributes. The flash hook configuration allows you to modify the duration of a flash hook. Any duration shorter or longer than what you configured is interpreted as an incoming call, and the call disconnects. Glare condition attribute configuration allows you to control the CAS direction—incoming, outgoing, or bidirectional—and the glare handling policy—controlling or releasing.
Configure ANI and DNIS Digit Order
You can configure the order in which a call agent sends automatic number identification (ANI) digits (the caller's number) and dial number identification service (DNIS) digits (the called number) to VISM during an outgoing FGD call for VISM endpoints.
CAS Immediate Start and Ground Start Glare Handling
The CAS variants immediate start and immediate start, multifrequency are supported. Use the addcasvar command to configure CAS variants.
Note
This release supports CAS glare condition handling according to RFC 3064. The VISM sends a NACK message in response to the call agent's request for ringing with error code 401 (off hook) in the event of a glare condition.
On receiving a request for ringing from call control, CAS transmits a seize signal to the PBX and starts the glare timer, returning a provisional response code to call control indicating that CAS is still processing the request. If the timer expires (normal case) or an incoming seizure is observed on the endpoint, CAS generates an asynchronous response code to call control that is comparable to an MGCP response code of 200 or 401.
RFC 3064 Package Support
This release fully supports the following packages from RFC 3064:
•
•
•
•
•
VISM Network Continuity Test
You can configure VISM network continuity testing with this release.
Posted: Mon Apr 16 14:36:38 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
