|
Table Of Contents
Configuring the Operating Mode
Configuring the ATM Network Side
Configuring Domain Names and IP Addresses
Configuring TDM Side Signaling for Applications That Use CCS
Configuring TDM Side Signaling for Applications That Use CAS
VoIP Trunking Mode
The Voice over IP (VoIP) trunking feature allows the VISM card to connect to the PBX, or central office digital systems. VISM uses T1/E1 digital interfaces, converts the TDM bit stream into Real-time Transport Protocol (RTP) packets after echo cancellation and compression, and transports the bits over the IP network.
No call agent is required for setting up and tearing down calls.
This section contains the following tasks for configuring the VISM/VISM-PR card for VoIP trunking:
• Configuring the Operating Mode
• Configuring the ATM Network Side
• Configuring Domain Names and IP Addresses
• Configuring TDM Side Signaling for Applications That Use CCS
• Configuring TDM Side Signaling for Applications That Use CAS
• Adding DS0 Endpoints to Lines
Sample VoIP trunking configurations are shown in the "Sample Configuration" section.
Configuring the Operating Mode
To configure your VISM/VISM-PR card for the VoIP trunking mode, complete the following steps:
Step 1 To configure the VISM/VISM-PR operating mode, enter the cnfvismmode command.
nodename.1.28.VISM8.a > cnfvismmode <mode_number>
Replace <mode_number> with value of 1.
•1 = VoIP switching/VoIP trunking (default)
•2 = AAL2 trunking
•3 = AAL1 switching
•7 = Switched AAL2 SVC
•8 = Switched AAL2 PVC
•9 = VoIP and AAL1 SVC
•10 = VoIP trunking and AAL2 trunking
Step 2 Type a y at the following message:
WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? y
A message about the number of available commands displays before the card returns the prompt. The following example shows the number of available commands for the VoIP trunking mode:
INFORMATION: The new 'voipSwitching' mode has 355 CLI commands.
Step 3 To display the current VISM/VISM-PR operating mode, enter the dspvismparam command.
nodename.1.28.VISM8.a > dspvismparam
VISM mode: voipSwitching/voipTrunking
VISM features Bit Map: 0x5bc
FunctionModuleType: VISM-PR-8T1
CAC flag: enable
DS0s available: 192
Template number: 2
Percent of functional DSPs: 100
IP address: 10.31.19.99
Subnet mask: 255.255.255.0
Bearer IP address: 0.0.0.0
Bearer Subnet mask: 0.0.0.0
RTCP report interval: 5000 msec
RTCP receive multiplier: 3
RTP receive timer: disable
ControlPrecedence/Tos: 0x60
BearerPrecedence/Tos: 0xa0
Aal2 muxing status: disable
Tftp Server Dn TFTPDOMAIN
Aggregate Clipping enable
Aggregate Svc Bandwidth 0
Type <CR> to continue, Q<CR> to stop:
Codec negotiation option 1
Profile negotiation option 1
VAD Duty Cycle 61
VAD Tolerance 100
VISM Initiated NW COT Off
VISM CO4 Timer 1000 msec
CALEA flag disable
SupportdModuleType: VISM-PR-8T1.
VismNSAP: 47009181000000000142265b99000001079bff00
Configuring the ATM Network Side
Configuring the ATM network side consists of setting up ATM PVCs across the network and providing the mechanism by which calls are routed over the correct PVC.
The Voice over IP trunking operating mode requires you to set up an AAL5 PVC for bearer transmission between the VISM/VISM-PR card and the PXM card or RPM. The router extracts the IP frames from the ATM cells and routes the frames.
If ISDN signaling is used, a separate control PVC might also be required.
Use the following guidelines when you set up the ATM side in the VoIP trunking mode.
•The master and slave connection base parameters, PCR, SCR, and MBS values must match.
If these values do not match, PXM1E and PXM45 cards display an error. PXM1 cards do not display an error.
•If the connections are through a physical loopback on an OC-3, make sure that the VPI and VCI values are the same on both ends of the loopback.
Complete the following tasks to configure the ATM side:
• Connection CAC Configuration
Configuring PVC Connections
The VoIP trunking mode has the following two types of PVCs:
•AAL5 Bearer PVCs—Support both bearer data and control data.
•Control PVCs—Support only control data.
Complete the following steps to configure PVC connections:
Note You must add the slave connection first before adding the master connection. Retain the remote connection ID to use when setting up the master connection.
Step 1 To add an ATM PVC between the VISM/VISM-PR card and the MGX 8000 Series platform PXM card, enter the addcon command.
nodename.1.28.VISM8.a > addcon <localVCI> <preference> <pvcType> <application> <PCR> <mastership> |<remoteConnId> <serviceType> <scr> <mbs> <priority> <prefrte> <direct>|
Replace the above arguments with the values listed in Table 8-1.
Step 2 If you need to refine the configuration parameters of the connection added in Step 1, enter the cnfcon command.
nodename.1.28.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress> <priority> <prefrte> <direct>|
Replace the above arguments with the values listed in Table 8-2.
Table 8-2 Parameters for cnfcon Command
Parameter DescriptionLCN
Type the value you entered for the localVCI argument in Step 1.
PCR
PCR described in cells per second.
Note The PCR argument value cannot be changed if the calls or connections for signaling and control are active.
Ranges are
•1-400 = Signaling PVCs in AAL2 trunking mode
•1-20000 = AAL5 control PVC
•1-50000 = T1 AAL2 bearer PVCs
•1-60000 = E1 AAL2 bearer PVCs
•1-96000 = AAL5 bearer PVC
Note If the service_type argument value is a VBR, the PCR argument value must be 15 or greater.
service_type
Service type. Values are
•1 = Constant bit rate (CBR)
•2 = Variable bit rate real time—rt-VBR
•3 = Variable bit rate non-real time—nrt-VBR
•4 = rt-VBR3
•5 = rt-VBR2
•6 = nrt-VBR
•7 = nrt-VBR
Note For VISM-PR to RPM-PR connections, use one of the values 4-7.
|SCR_ingress|
(Optional) SCR. Range is from 15 to the value you configured for the PCR argument.
Note This argument value is required if the service_type argument value is in the range 2-7.
|MBS_ingress|
(Optional) MBS. Maximum number of cells transmitted at the peak cell rate. Range is from 1 cell to 10 times the value you configured for the SCR_ingress argument.
Note This argument value is required if the service_type argument value is in the range 2-7.
|priority|
(Optional) Route priority is the priority number assigned to the PVC during configuration of the connection.
Range is 1-15. Default is 8.
A value of 1 indicates highest priority, and a value of 15 indicates the lowest priority.
Note This parameter is applicable only to VISM-PR cards.
|prefrte|
(Optional) Unique identifier of the preferred route to which this connection is associated.
Range is 0-65535. Default is 0.
When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection.
Note This parameter is applicable only to VISM-PR cards.
|direct|
(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take.
•1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified.
•2 = No (Default)—The connection is allowed to try another alternate route if the preferred route is unavailable.
If the directed preferred route is unavailable, the connection is failed.
Note This parameter is applicable only to VISM-PR cards.
Step 3 To configure primary and secondary PVCs to provide protection in the event of a PVC failure, enter the cnfconprotect command.
nodename.1.28.VISM8.a > cnfconprotect <LCN> <protection> <lock_state> <fallback_LCN>
Replace the above arguments with the values listed in Table 8-3.
Step 4 To display the details of the connection, enter the dspcon command.
nodename.1.11.VISM8.a > dspcon <LCN>
Replace the <LCN> argument with a value in the range 131-510.
The following example shows sample configuration for a bearer PVC in VoIP trunking mode.
mgxa-pxm1e.1.30.VISM8.a > dspcon 132
ChanNum: 132
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 us
ChanPortNum: 255
ChanPvcType: AAL5
ChanConnectionType: PVC
ChanLocalVpi: 30
ChanLocalVci: 132
ChanLocalNSAP: 470091810000000007856e136300000107f3ff00
ChanRemoteVpi: 104
ChanRemoteVci: 131
ChanRemoteNSAP: 470091810000000007856e1363000001073b0400
ChanMastership: Master
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
Type <CR> to continue, Q<CR> to stop:
ChanConnPCR: 58000
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 58000
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: bearer
ChanServiceType: cbr
ChanScrIngress: 58000
ChanMbsIngress: 58000
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
ChanPrefRouteId: 0
ChanDirectRoute: False
Type <CR> to continue, Q<CR> to stop:
ChanUserPcrNumber: User BW Off
ChanUserMinPCRBW: 10
ChanUserMaxPCRBW: 58000
ChanUserMaxScrBW: 0
ChanUserMaxMbsBW: 0
ChanNumNextAvailable: 133
The following example shows sample configuration for a signaling connection with CCS.
nodename.1.5.VISM8.a > dspcon 231
ChanNum: 231
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 us
ChanPortNum: 255
ChanPvcType: AAL5
ChanConnectionType: PVC
ChanLocalVpi: 5
ChanLocalVci: 231
ChanLocalNSAP: 4700918100000000059a3f9761000001072bff00
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction
Type <CR> to continue, Q<CR> to stop:
ChanConnPCR: 400
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 400
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: signaling
ChanServiceType: cbr
ChanScrIngress: 400
ChanMbsIngress: 400
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
ChanPrefRouteId: 0
ChanDirectRoute: False
Type <CR> to continue, Q<CR> to stop:
ChanUserPcrNumber: User BW Off
ChanUserMinPCRBW: 10
ChanUserMaxPCRBW: 0
ChanUserMaxScrBW: 0
ChanUserMaxMbsBW: 0
ChanNumNextAvailable: 133
Step 5 To verify the integrity or continuity of a connection, enter the tstcon command.
nodename.1.11.VISM8.a > tstcon
The following example shows a connection test for LCN 131.
nodename.1.11.VISM8.a > tstcon 131
test type is..... 1
TestCon in progress.
TestCon Passed.
Connection CAC Configuration
Note CAC must be enabled on the card.
To configure VAD tolerance and VAD duty cycle for a specific logical connection number (LCN) used for PVCs, enter the cnfconcacparams command.
nodename.1.28.VISM8.a > cnfconcacparams <LCN> <VADTolerance> <VADDutyCycle>
Replace the above arguments with the values listed in Table 8-4.
Configuring Domain Names and IP Addresses
Complete the following steps to configure domain names and IP addresses for VISM cards and call agents:
Step 1 To specify a domain name for the VISM card, enter the cnfvismdn command.
nodename.1.28.VISM8.a > cnfvismdn <domain_name>
Replace the domain_name argument value with a text string of up to 64 alphanumeric characters; spaces are not allowed. Default name is cisco.com as shown in the following example:
nodename.1.28.VISM8.a > cnfvismdn cisco.com
Step 2 To specify the IP address and a subnet mask for the VISM card, type the cnfvismip command.
nodename.1.28.VISM8.a > cnfvismip <vismIpAddr> <netMask> |<vismBearerIpAddr> <bearerNetMask>|
Replace the above arguments with the values listed in Table 8-5.
The following example shows the IP address and subnet mask configured for the VISM card and the output of the command.
nodename.1.28.VISM8.a > cnfvismip 172.29.52.003 255.255.255.248
Attaching network interface atm0... done.
Configuring TDM Side Signaling for Applications That Use CCS
Common channel signaling (CCS) uses a dedicated channel on a DS1 line to carry the signaling for the other channels on the line. Signaling is transported across the trunk as Q.931 messages in ATM cells using AAL5.
You must identify the signaling channel to the VISM/VISM-PR card.
Complete the following steps to add and configure CCS:
Step 1 To add a Reliable User Datagram Protocol (RUDP) trunk for a Link Access Protocol D Channel (LAPD) trunk connection, enter the addrudptrunk command.
nodename.1.21.VISM8.a > addrudptrunk <session_number> <local_port> <remote_port> <Remote_Gw_IP>
Replace the above arguments with the values listed in Table 8-6.
Step 2 To add an LAPD trunk to a specific VISM card line, enter the addlapdtrunk command.
nodename.1.21.VISM8.a > addlapdtrunk <Line_Num> <Lapd_Rudp_Index>
Replace the above arguments with the values listed in Table 8-7.
Table 8-7 Parameters for addlapdtrunk Command
Parameter DescriptionLine_Num
Line number in the range 1-8.
Lapd_Rudp_Index
LAPD RUDP index in the range 1-64.
Step 3 To add an ISDN PRI channel on a DS1/DS0 line, enter the addlapd command.
nodename.1.28.VISM8.a > addlapd <line_number> <ds0_number> |<lapd_side> <lapd_application_type>|
Replace the above arguments with the values listed in Table 8-8.
Step 4 To specify the LAPD stack type, enter the cnflapdtype command.
nodename.1.28.VISM8.a > cnflapdtype <line_number> <ds0_number> <lapd_type>
Replace the above arguments with the values listed in Table 8-9.
Configuring TDM Side Signaling for Applications That Use CAS
In VoIP trunking mode basic CAS configurations are not required.
For advanced CAS configurations, see the "CAS Features" section on page 9-125.
Adding DS0 Endpoints to Lines
The number of DS0s you can add depends on the template that you are using.
Complete the following steps to add DS0 endpoints to lines:
Step 1 To add multiple endpoints with one command, enter the addendpts command.
nodename.1.12.VISM8.a > addendpts <endpt_num> <ds1_num> <ds0_num> <endpts_num>
Replace the above arguments with the values listed in Table 8-10.
Step 2 To add a single DS0 to a line, enter the addendpt command.
nodename.1.28.VISM8.a > addendpt <endpt_num> <ds1_num> <ds0_num>
Replace the above arguments with the values listed in Table 8-10.
Step 3 To validate the endpoints that you added, enter the dspendpts command.
nodename.1.28.VISM8.a > dspendpts
EndptNum Ena/Speed
-------- --- -----
1 act/ 64k
2 act/ 64k
3 act/ 64k
4 act/ 64k
5 act/ 64k
6 act/ 64k
7 act/ 64k
8 act/ 64k
9 act/ 64k
10 act/ 64k
11 act/ 64k
12 act/ 64k
13 act/ 64k
14 act/ 64k
15 act/ 64k
16 act/ 64k
17 act/ 64k
18 act/ 64k
19 act/ 64k
20 act/ 64k
Type <CR> to continue, Q<CR> to stop:
Adding RTP Connections
A Real-Time Protocol (RTP) connection must be associated with each of the endpoints being utilized in VoIP trunking. The RTP connection binds an endpoint to a UDP port.
To add an RTP connection, complete the following steps:
Step 1 To add a static RTP VoIP trunking connection, use the addrtpcon command.
nodename.1.28.VISM8.a > addrtpcon <rtp_conn_index> <rtp_endpt_num> <rtp_local_port> <rtp_remote_port> <rtp_remote_GW_IP_Addr> <voice_codec_type> |<voice_packet_period> <bearer_prec> <bearer_tos> <conn_mode> <ecan> <VAD_OnOff> <VAD_Timer> <CAS_Transport> <DTMF_Transport> <ICS> <payload>
Replace the above arguments with the values listed in Table 8-11.
Note Ensure that the local RTP port and remote RTP port have matching port numbers on the remote gateway.
Step 2 To display the configuration of the RTP trunking connection you added, use the dsprtpcon command.
nodename.1.28.VISM8.a > dsprtpcon <rtp_conn_index>
Replace <rtp_conn_index> with a value in the range 1-248. The following example shows the information for RTP connection 1.
nodename.1.28.VISM8.a > dsprtpcon 1
Connection Index: 1
Endpoint Number: 1
Local RTP Port: 49648
Remote RTP Port: 49648
Remote IP Address: 10.1.30.30
Codec Type: G.711u
Packetization Period: ten msec
ECAN Status: Enable
VAD: Off
VAD Timer: 250 msec
CAS Transport: On
DTMF Transport: On
ICS Enable: Disable
Bearer TOS: 160
Connection Mode: GW can send and recv packets
Conn Alarm State: Active
Conn Fail Reason: Not Fail
Payload Type: 256
Associated PVC: 131
Sample Configuration
This section provides examples of configuring VoIP trunking between two VISM/VISM-PR cards.
Near-End Card Configuration
The following steps show the set up for VoIP trunking on the near-end VISM/VISM-PR card.
1. Set the VISM/VISM-PR mode to VoIP switching and codec template to 1.
cnfvismmode 1
cnfcodectmpl 1
Note When you make changes to the codec template, the VISM/VISM-PR card resets.
2. Add a resource partition to communicate to the PXM card.
addport
addrscprtn 1
3. Add the line, configure the line, and configure the line signaling as CCS.
addln 3
cnfln 3 2 10 2 1 1
cnflnsig 3 2
4. Add the slave connection on the VISM/VISM-PR card.
addcon 150 1 1 2 80000 1 sol-mgx2.0.1.200.220
cnfconvbdpol 150 1 2
5. Set the domain name and IP address.
cnfvismdn vism19
cnfvismip 10.60.7.1 255.255.255.0
6. Add the RUDP session for ISDN Backhaul.
addrudptrunk 3 7000 7000 10.60.8.1
7. Add the LAPD on line 3.
addlapdtrunk 3 3
addlapd 3 24 2 1
8. Add the endpoints to the line.
addendpts 21 3 1 10
9. Add the RTP connections to the far-end VISM/VISM-PR card.
addrtpcon 21 21 49688 49736 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 22 22 49690 49738 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 23 23 49692 49740 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 24 24 49694 49742 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 25 25 49696 49744 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 26 26 49698 49746 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 27 27 49700 49748 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 28 28 49702 49750 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 29 29 49704 49752 10.60.8.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 30 30 49706 49754 10.60.8.1 1 10 5 0 3 2 1 250 2 1
Far-End Card Configuration
The following steps show the set up for VoIP trunking on the far-end VISM/VISM-PR card.
1. Set the VISM/VISM-PR mode to VoIP switching and codec template to 1.
cnfvismmode 1
cnfcodectmpl 1
Note When you make changes to the codec template, the VISM/VISM-PR card resets.
2. Add a resource partition to communicate to the PXM card.
addport
addrscprtn 1
3. Add the line, configure the line, and configure the line signaling as CCS.
addln 3
cnfln 3 2 10 2 1 1
cnflnsig 3 2
4. Add the connection on the VISM/VISM-PR card.
addcon 150 1 1 2 80000 1 sol-mgx2.0.2.200.220
cnfconvbdpol 150 1 2
5. Set the domain name and IP address.
cnfvismdn vism20
cnfvismip 10.60.8.1 255.255.255.0
6. Add the RUDP session for ISDN Backhaul.
addrudptrunk 3 7000 7000 10.60.7.1
addlapdtrunk 3 3
7. Add the LAPD on line 3.
addlapd 3 24 2 1
8. Add the endpoints to the line.
addendpts 21 3 1 10
9. Add the RTP connections to the far-end VISM/VISM-PR card.
addrtpcon 21 21 49736 49688 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 22 22 49738 49690 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 23 23 49740 49692 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 24 24 49742 49694 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 25 25 49744 49696 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 26 26 49746 49698 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 27 27 49748 49700 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 28 28 49750 49702 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 29 29 49752 49704 10.60.7.1 1 10 5 0 3 2 1 250 2 1
addrtpcon 30 30 49754 49706 10.60.7.1 1 10 5 0 3 2 1 250 2 1
Posted: Mon Apr 16 14:12:03 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.