Guest

Cisco MGX 8800 Series Switches

Release Notes for Cisco Voice Interworking Service Module Release 3.1(0)

  • Viewing Options

  • PDF (517.5 KB)
  • Feedback
Release Notes for Cisco Voice Interworking Service Module Release 3.1(0)

Table Of Contents

Release Notes for Cisco Voice Interworking Service Module Release 3.1(0)

Contents

VISM Features

Support for the Trunking Gateway Control Protocol

Modified CLIs for TGCP Support

addmgcgrpprotocol

cnfmgcgrpprotocol

delmgcgrpprotocol

Support for MGX 8830 with PXM1E

Dynamic Payload for Voice Codecs

New CLIs for Dynamic Payload for Voice Codecs

cnfdynamicpayload

dspdynamicpayload

Modified CLIs for Dynamic Payload for Voice Codecs

addrtpcon

cnfrtpcon

dsprtpcon

cnfvbdcodec

dspvbdcodec

Important Notes

VISM Management Information Base

MIB Changes for Software Release 3.1(0) for VISM/VISM-PR

Software Release 3.1(0) for VISM/VISM-PR CLI Commands

New, Modified, and Deprecated CLI Commands

VISM Redundancy

VISM Call Rate

Compatibility

Limitations and Restrictions

Installation and Upgrade Procedures

VISM Firmware and Boot Code Download Procedure for PXM1

VISM Firmware and Boot Code Download Procedure for PXM1E and PXM45

VISM/VISM-PR Firmware Upgrade

VISM to VISM-PR Hardware Upgrade

Installing VISM Software Updates with PXM1 Cards

Initial Conditions

Upgrade Procedure

Installing VISM Software Updates with PXM1E or PXM45 Cards

VISM Boot Code Upgrade Procedure with PXM1 Cards

VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

VISM Downgrade Procedure

Caveats

Resolved Caveats

Open Caveats

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco Voice Interworking Service Module Release 3.1(0)


These release notes are part number OL-2785-01 Rev. C0, January 9, 2004.

The Voice Interworking Service Module (VISM) product is supported by MGX Voice Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.

The software Release 3.1(0) for VISM/VISM-PR is an upgrade from the VISM 3.0(0) Release. The new features in VISM Release 3.1(0) are described in the "VISM Features" section. The new, modified, and deprecated MIB objects and CLI commands are listed in the "Important Notes" section.

The software Release 3.1(0) for VISM/VISM-PR is supported by the Cisco VISM Installation and Configuration Guide, which is available on cisco.com.

Contents

These release notes contain the following sections:

"VISM Features" section

"Important Notes" section

"Installation and Upgrade Procedures" section

"Caveats" section

"Related Documentation" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

VISM Features

This section describes the new software features introduced in software Release 3.1(0) for VISM/VISM-PR:

Support for the Trunking Gateway Control Protocol

Support for MGX 8830 with PXM1E

Dynamic Payload for Voice Codecs


Note VISM-PR is supported in combination with SRME on the PXM45 and RPM-XF on the PXM45 with the VISM 3.1(0) release.


Support for the Trunking Gateway Control Protocol

The VISM/VISM 3.1(0) software supports the Trunking Gateway Control Protocol (TGCP) profile. With this support, VISM accepts and generates MGCP 1.0 commands with a profile name of TGCP 1.0.

Use the following modified commands to enable the TGCP 1.0 support:

addmgcgrpprotocol

cnfmgcgrpprotocol

delmgcgrpprotocol

dspmgprotocols

Modified CLIs for TGCP Support

This section describes the modified CLIs for the TGCP support.

addmgcgrpprotocol

To associate a call agent redundancy group with a gateway control protocol (xGCP) and configure call agent group protocol control data, use the addmgcgrpprotocol command in the VoIP switching/trunking and switched AAL2 PVC operating mode.

addmgcgrpprotocol red-mgc-group protocol-num quar-persist default-quar del-negated prov-resp resp-ack disc-proc-enable cancel-grace

Syntax Description

red-mgc-group

Call agent redundancy group number. It can be in the range from 1 to 8.

protocol-num

Protocol number. It can be one of the following values:

1 = MGCP 0.1

2 = SGCP 1.1+

3 = SRCP 1.0.2

4 = SGCP 1.5

5 = MGCP 1.0

6 = TGCP 1.0

quar-persist

(Optional) Sets the quarantine handling method for persistent events. It can be one of the following values:

1 = Quarantine persistent events (Default)

2 = Do not quarantine persistent events

default-quar

(Optional) Sets the default quarantine handling method for each protocol. It can be one of the following values:

1 = Step, process (Default for MGCP 1.0)

2 = Step, discard (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

3 = Loop, process

4 = Loop, discard

Note Step = one notification command is generated per notification request. Loop = multiple notification commands are generated per notification request.

del-negated

(Optional)

1 = Delete events from the previous list which are not present in the current list.

2 = Delete events from the previous list, only if the event is present in the current list with a hyphen (-) as the parameter.

prov-resp

(Optional) Enables or disables the sending of a provisional response. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

resp-ack

(Optional) Enables or disables sending a response acknowledgment. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

disc-proc-enable

(Optional) Enables or disables the disconnect method, which indicates that the endpoint has become disconnected and is now trying to establish connectivity. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

cancel-grace

(Optional) Enables or disables VISM cancelling a previously issued graceful restart in progress command. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)


Command Modes

VoIP switching/trunking and switched AAL2 PVC

Usage Guidelines

This command allows you to add multiple protocols to the same redundancy group.

Examples

The following example shows that call agent redundancy group number 3 is assigned gateway control protocol number 2, SGCP 1.1+:

addmgcgrpprotocol 3 2

Related Commands

Command
Description

addmgcgrpentry

Configures call agents as part of an MGC redundancy group and assigns a priority value for a call agent.

cnfdisctimers

Specifies the wait delay times for the disconnected procedure, restart in progress command—initial, minimum, and maximum timer values.

cnfmgcgrpentry

Modifies the call agent priority level of a call agent within a call agent redundancy group.

cnfmgcgrpparam

Modifies a call agent redundancy group state change notification policy and priority level.

cnfmgcgrpprotocol

Configures call agent group protocol data.

cnfsrcppeer

Configures the SRCP parameters when SRCP is the selected protocol for communication between the VISM card and call agent.

cnfsrcppeergrpparam

Modifies the SRCP heartbeat interval and maximum UDP size for a specified call agent redundancy group.

delmgcgrpentry

Deletes a call agent from a call agent redundancy group.

delmgcgrpprotocol

Deletes an MGCP from a specified call agent redundancy group.

dspdisctimers

Displays the Restart in Progress command disconnect type method wait delay times.

dspmgcgrpparams

Displays all configured call agent redundancy group parameters.

dspmgcgrpprotocols

Displays all configured call agent redundancy group protocols.

dspmgcprps

Displays all configured call agent redundancy groups.

dspsrcppeergrpparams

Displays the SRCP parameters for all call agent redundancy groups that have SRCP added.


cnfmgcgrpprotocol

To configure a call agent redundancy group protocol for a previously configured redundancy group, use the cnfmgcgrpprotocol command in the VoIP switching/trunking, switched AAL1 SVC, switched AAL2 SVC, switched AAL2 PVC, AAL2 trunking, VoIP and switched ATM AAL1 SVC operating modes.

cnfmgcgrpprotocol red-mgc-group protocol-num |quar-persist default-quar del-negated prov-resp resp-ack disc-proc-enable cancel-grace|

Syntax Description

red-mgc-group

Call agent redundancy group number. It can be in the range from 1 to 8.

protocol-num

Protocol number. It can be one of the following values:

1 = MGCP 0.1

2 = SGCP 1.1+

3 = SRCP 1.0.2

4 = SGCP 1.5

5 = MGCP 1.0

6 = TGCP 1.0

You can use 7 and 8—as displayed by the dspmgcgrpprotocols command.

quar-persist

(Optional) Sets the quarantine handling method for persistent events. It can be one of the following values:

1 = Quarantine persistent events (Default)

2 = Do not quarantine persistent events

default-quar

(Optional) Sets the default quarantine event handling method for each protocol. It can be one of the following values:

1 = Step, process (Default for MGCP 1.0)

2 = Step, discard (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

3 = Loop, process

4 = Loop, discard

Note Step = one notification command is generated per notification request. Loop = multiple notification commands are generated per notification request.

del-negated

(Optional)

1 = Delete events from the previous list which are not present in the current list.

2 = Delete events from the previous list, only if the event is present in the current list with a hyphen (-) as the parameter.

prov-resp

(Optional) Enables or disables the sending of a provisional response. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

resp-ack

(Optional) Enables or disables sending a response acknowledgment. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

disc-proc-enable

(Optional) Enables or disables the disconnect method, which indicates that the endpoint has become disconnected and is now trying to establish connectivity. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

cancel-grace

(Optional) Enables or disables VISM cancelling a previously issued graceful restart command. It can be one of the following values:

1 = On (Default for MGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)


Command Modes

VoIP switching/trunking, switched AAL1 SVC, switched AAL2 SVC, switched AAL2 PVC, AAL2 trunking, VoIP and switched ATM AAL1 SVC

Usage Guidelines

Use this command to change the protocol for a redundancy group that has previously been assigned a protocol with the addmgcgrpprotocol command.

Examples

The following example shows that redundancy group number 7 is assigned the SRCP 1.0.2 protocol, and quarantines persistent events with the loop, process handling method. All optional arguments are enabled.

cnfmgcgrpprotocol 7 3 1 3 1 1 1 1 1

Related Commands

Command
Description

addmgcgrpprotocol

Associates a call agent redundancy group to a gateway control protocol.

cnfdisctimers

Specifies the wait delay times for the disconnected procedure, restart in progress command—initial, minimum, and maximum timer values.

cnfxgcppeer

Configures the UDP port number used to send gateway-initiated messages to the call agent.

delmgcgrpprotocol

Deletes an MGCP from a specified call agent redundancy group.

dspdisctimers

Displays the Restart in Progress command disconnect type method wait delay times.


delmgcgrpprotocol

To delete a Media Gateway Control Protocol (MGCP) from a specified call agent redundancy group, use the delmgcgrpprotocol command in the VoIP switching/trunking and switched AAL2 PVC operating modes.

delmgcgrpprotocol mgc-group protocol-num

Syntax Description

mgc-group

Call agent redundancy group number. It can be in the range from 1 to 8.

protocol-num

Protocol number. It can be one of the following values:

1 = MGCP 0.1

2 = SGCP 1.1+

3 = SRCP 1.0.2

4 = SGCP 1.5

5 = MGCP 1.0

6 = TGCP 1.0

You can use 7 and 8, as displayed by the dspmgcgrpprotocols command.


Command Modes

VoIP switching/trunking and switched AAL2 PVC

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example shows that protocol number 2 is deleted from call agent redundancy group number 3:

delmgcgrpprotocol 3 2

Related Commands

Command
Description

addmgcgrpentry

Configures call agents as part of an MGC redundancy group and assigns a priority value for a call agent.

addmgcgrpprotocol

Associates a call agent redundancy group to a gateway control protocol.

cnfdisctimers

Specifies the wait delay times for the disconnected procedure, restart in progress command—initial, minimum, and maximum timer values.

cnfmgcgrpentry

Modifies the call agent priority level of a call agent within a call agent redundancy group.

cnfmgcgrpparam

Modifies a call agent redundancy group state change notification policy and priority level.

cnfmgcgrpprotocol

Configures call agent group protocol data.

cnfsrcppeer

Configures the SRCP parameters when SRCP is the selected protocol for communication between the VISM card and call agent.

cnfsrcppeergrpparam

Modifies the SRCP heartbeat interval and maximum UDP size for a specified call agent redundancy group.

delmgcgrpentry

Deletes a call agent from a call agent redundancy group.

dspdisctimers

Displays the Restart in Progress command disconnect type method wait delay times.

dspmgcgrpparams

Displays all configured call agent redundancy group parameters.

dspmgcgrpprotocols

Displays all configured call agent redundancy group protocols.

dspmgcgrps

Displays all configured call agent redundancy groups.

dspsrcppeergrpparams

Displays the SRCP parameters for all call agent redundancy groups that have SRCP added.


The dspmgprotocols command is modified to display the TGCP 1.0 profile.

Support for MGX 8830 with PXM1E

Table 1 describes the configuration requirements for VISM/VISM-PR in combination with the MGX 8000 Series switches and supported processor modules.

Table 1 VISM/VISM-PR and MGX 8000 Series Switch Support 

VISM Module
MGX 8230 with PXM1
MGX 8830 with PXM1E
MGX 8250 with PXM1
MGX 8850 with PXM1
MGX 8850 with PXM1E
MGX 8850 with PXM45

MGX-VISM-8T1

Yes

No

Yes

Yes

No

No

MGX-VISM-8E1

Yes

No

Yes

Yes

No

No

MGX-VISM-PR-8T1

Yes

Yes

Yes

Yes

Yes

Yes

MGX-VISM-PR-8E1

Yes

Yes

Yes

Yes

Yes

Yes


Refer to the Cisco MGX 8850 Hardware Installation Guide, Release 3 for information on installing and maintaining the PXM1, PXM1E, and PXM45 cards.


Note You cannot use the VISM card in combination with either the PXM1E or PXM45 card. You can use the VISM-PR card with the PXM1, PXM1E, and PXM45 cards.


Dynamic Payload for Voice Codecs

Software Release 3.1(0) for VISM/VISM-PR supports the dynamic payload feature. The dynamic payload feature allows VISM to support dynamic payloads for voice codecs.

The dynamic payload feature introduces the following new CLI commands:

cnfdynamicpayload

dspdynamicpayload

The following CLI commands are modified to enable the dynamic payload feature:

addrtpcon

cnfrtpcon

dsprtpcon

cnfvbdcodec

dspvbdcodec

The dynamic payload feature is supported in the VoIP switching/trunking and the VoIP and switched ATM AAL1 SVC operating modes.

New CLIs for Dynamic Payload for Voice Codecs

This section describes the new CLI commands for the dynamic payload feature.

cnfdynamicpayload

To enable or disable the dynamic payload on the current VISM card, use the cnfdynamicpayload command in the VoIP switching/trunking and the VoIP and switched ATM AAL1 SVC operating modes.

cnfdynamicpayload dynamic-pload

Syntax Description

dynamic-pload

Enables or disables dynamic payload on the current VISM card. It can be one of the following values:

1 = Enable

2 = Disable


Command Modes

VoIP switching/trunking

Usage Guidelines

When 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 cnfvbdcode 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.

Examples

The following example configures the dynamic payload feature on the current VISM card:

cnfdynamicpayload 1

Related Commands

Command
Description

addrtpcon

Adds a static RTP VoIP trunking connection.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfvbdcodec

Configures the VBD upspeed codec.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dspvbdcodec

Displays the upspeed codec used for VBD.


dspdynamicpayload

To display the card level configuration of dynamic payload on the current VISM card, use the dspdynamicpayload command in the VoIP switching/trunking and the VoIP and switched ATM AAL1 SVC operating modes.

dspdynamicpayload

Syntax Description

This command has no arguments or keywords.

Command Modes

VoIP switching/trunking

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example displays the dynamic payload feature configuration of the current VISM card:

dspdynamicpayload

Dynamic Payload flag: disable

Related Commands

Command
Description

addrtpcon

Adds a static RTP VoIP trunking connection.

cnfdynamicpayload

Enables or disables the dynamic payload on the current VISM card.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfvbdcodec

Configures the VBD upspeed codec.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dspvbdcodec

Displays the upspeed codec used for VBD.


Modified CLIs for Dynamic Payload for Voice Codecs

This section describes the modified CLI commands for the dynamic payload feature.

addrtpcon

To add a static Real-Time Transport Protocol (RTP) VoIP trunking connection, use the addrtpcon command in the VoIP switching/trunking operating mode.

addrtpcon conn-num endpt-num local-rtp-port remote-rtp-port remote-ip-addr codec-type |vt-pkt-period bearer-prec bearer-tos conn-mode ecan-enable vad-enable vad-timer cas-trans dtmf-trans idle-code-sup payload-type|

Syntax Description

conn-num

Connection identification number. It can be in the range from 1 to 248.

endpt-num

Endpoint number. It can be a value from one of the following ranges:

For template number 1:

For VISM, from 1 to 145

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 2:

For VISM T1, from 1 to 192

For VISM E1, from 1 to 248

For template number 3:

For VISM, from 1 to 120

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 4:

For VISM-PR, from 1 to 144

local-rtp-port

Static RTP local port number. It can be an even number in the range from 49648 to 50142.

Note The odd numbers within the local-rtp-port range are reserved for Real-Time Control Protocol (RTCP) ports.

remote-rtp-port

Static RTP remote port number. It can be an even number in the range from 16384 to 50142.

Note The odd numbers within the remote-rtp-port range are reserved for RTCP ports.

remote-ip-addr

IP address of the remote VISM card, in dotted decimal format (nnn.nnn.nnn.nnn).

codec-type

The type of coding/decoding to be performed on the data stream. It can be one of the following values:

1 = G.711u

2 = G.711a

3 = G.726-32K

4 = G.729a

5 = G.729ab

6 = Clear channel (VAD must be off)

7 = G.726-16K

8 = G.726-24K

9 = G.726-40K

11 = G.723.1-H

12 = G.723.1a-H

13 = G.723.1-L

14 = G.723.1a-L

vt-pkt-period

(Optional) Packetization period (defined in milliseconds). It can be one of the following values:

10

20

30

40

60

bearer-prec

(Optional) Bearer precedence. It can be in the range from 0 to 7. (Default = 5)

bearer-tos

(Optional) Bearer type of service (ToS). It can be one of the following values:

0 (Default)

1

2

4

8

conn-mode

(Optional) Connection mode. It can be one of the following values:

1 = VISM sends packets

2 = VISM receives packets

3 = VISM sends and receives packets (Default)

4 = Inactive; VISM does not send or receive packets

ecan-enable

(Optional) Enables or disables echo cancellation (ECAN). It can be one of the following values:

1 = On (Default)

2 = Off

vad-enable

(Optional) Enables or disables voice activity detection (VAD). It can be one of the following values:

1 = On

2 = Off (Default)

vad-timer

(Optional) The VAD holdover timer (defined in milliseconds) in the range from 250 to 65535.

cas-trans

(Optional) Enables or disables CAS signaling transport. It can be one of the following values:

1 = On (Default)

2 = Off

dtmf-trans

(Optional) Enables or disables DTMF tone transport. It can be one of the following values:

1 = On (Default)

2 = Off

Note The dtmf-trans argument value must be set to 1 (on) when the codec-type is configured for codecs other than G.711 and G.726.

idle-code-sup

(Optional) Enables or disables idle code suppression for the channel identifier (CID). It can be one of the following values:

1 = On

2 = Off (Default)

payload-type

(Optional) Assigns the payload type. It can be in the range from 0 to 255. Default = 256.

Note If you do not use the payload-type argument to assign the payload type, the dynamic payload is set to the static value of the DSPs codec type.


Command Modes

VoIP switching/trunking

Usage Guidelines

The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.

Examples

The following example shows that the RTP trunking connection 26 is added and configured with endpoint number 200, static RTP local port number 50000, static RTP remote port number 49648, remote IP address 209.165.200.224, G.726/32 codec type, 20-ms packetization period, bearer precedence of 3, bearer ToS of 1, VISM sends and receives packets, ECAN and VAD enabled, 400-ms VAD holdover time, CAS transportation enabled, DTMF tone transportation, idle code suppression for CID enabled, and the 255 payload type:

addrtpcon 26 200 50000 49648 209.165.200.224 3 20 3 1 3 1 1 400 1 1 1 255

Related Commands

Command
Description

addlapdtrunk

Adds an LAPD trunk to a specific VISM card line.

addrudptrunk

Adds an ISDN PRI backhaul RUDP session for an LAPD trunk connection.

clrrtpcnt

Clears the RTP counters (statistics) for a specific static RTP connection.

cnfdynamicpayload

Enables or disables the dynamic payload on the current VISM card.

cnflapdtrunkpvc

Assigns the PVC trunk type that carries LAPD messages for the current VISM card.

cnflntrunkcond

Enables or disables line conditioning on a VISM card line if a network alarm is encountered.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfrudptrunkrmtip

Modifies the remote IP address of VISM used in the ISDN PRI backhaul RUDP trunk for a specified session.

dellapdtrunk

Deletes an LAPD configured line.

delrtpcon

Deletes a static RTP VoIP trunking connection.

delrudptrunk

Deletes an ISDN PRI backhaul RUDP session that is associated with an LAPD.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsplapd

Displays data about an LAPD.

dsplapdtrunkpvc

Displays the assigned PVC trunk type that carries LAPD trunk messages for the current VISM card.

dsplapdtrunks

Displays the configuration data of all LAPD trunks.

dsprtpcnt

Displays the bearer counters (statistics) for a specific RTP VoIP trunking connection.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dsprtpconnstat

Displays the Real-time Transport Protocol (RTP) connection statistics for a specified endpoint.

dsprtpcons

Displays the configuration data of all static RTP VoIP trunking connections.

dsprudptrunk

Displays the configuration data of a specified ISDN PRI backhaul RUDP session.

dsprudptrunks

Displays the configuration data of all ISDN PRI backhaul RUDP sessions.


cnfrtpcon

To modify an existing static Real-Time Transport Protocol (RTP) VoIP trunking connection, use the cnfrtpcon command in the VoIP switching/trunking operating mode.

cnfrtpcon conn-num codec-type conn-mode |vt-pkt-period bearer-prec bearer-tos vad-enable vad-timer ecan-enable cas-trans dtmf-trans idle-code-sup payload-type|

Syntax Description

conn-num

Connection identification number. It can be in the range from 1 to 248.

codec-type

The type of coding/decoding to be performed on the data stream. It can be one of the following values:

1 = G.711u

2 = G.711a

3 = G.726-32K

4 = G.729a

5 = G.729ab

6 = Clear channel (VAD must be off)

7 = G.726-16K

8 = G.726-24K

9 = G.726-40K

11 = G.723.1-H

12 = G.723.1a-H

13 = G.723.1-L

14 = G.723.1a-L

conn-mode

(Optional) Connection mode. It can be one of the following values:

1 = VISM sends packets

2 = VISM receives packets

3 = VISM sends and receives packets (Default)

4 = Inactive; VISM does not send or receive packets

vt-pkt-period

(Optional) Packetization period (defined in milliseconds). It can be one of the following values:

10

20

30

40

60

bearer-prec

(Optional) Bearer precedence. It can be in the range from 0 to 7. (Default = 5)

bearer-tos

(Optional) Bearer type of service (ToS). It can be one of the following values:

0 (Default)

1

2

4

8

vad-enable

(Optional) Enables or disables voice activity detection (VAD). It can be one of the following values:

1 = On

2 = Off (Default)

vad-timer

(Optional) The VAD holdover timer (defined in milliseconds) in the range from 250 to 65535.

ecan-enable

(Optional) Enables or disables echo cancellation (ECAN). It can be one of the following values:

1 = On (Default)

2 = Off

cas-trans

(Optional) Enables or disables CAS signaling transportation. It can be one of the following values:

1 = On (Default)

2 = Off

dtmf-trans

(Optional) Enables or disables DTMF tone transportation. It can be one of the following values:

1 = On (Default)

2 = Off

Note The dtmf-trans argument value must be set to 1 (on) when the codec-type is configured for codecs other than G.711 and G.726.

idle-code-sup

(Optional) Enables or disables idle code suppression for the CID. It can be one of the following values:

1 = On

2 = Off (Default)

payload-type

(Optional) Assigns the payload type. I can be in the range from 0 to 255. Default = 256.

Note If you do not use the payload-type argument to assign the payload type, the dynamic payload is set to the static value of the DSPs codec type.


Command Modes

VoIP switching/trunking

Usage Guidelines

The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.

Examples

The following example shows that the RTP trunking connection 26 is configured (modified) with G.726/32 codec type. VISM is also configured to send and receive packets and has a 20-ms packetization period, a bearer precedence of 3, a bearer ToS of 1, with VAD enabled, and a 400-ms VAD holdover time. Also, ECAN, CAS, DTMF tone transport, idle code suppression for CID, and redundancy are enabled, and the 255 payload type is configured:

cnfrtpcon 26 3 3 20 3 1 1 400 1 1 1 1 255

Related Commands

Command
Description

addlapdtrunk

Adds an LAPD trunk to a specific VISM card line.

addrtpcon

Adds a static RTP VoIP trunking connection.

addrudptrunk

Adds an ISDN PRI backhaul RUDP session for an LAPD trunk connection.

clrrtpcnt

Clears the RTP counters (statistics) for a specific static RTP connection.

cnfdynamicpayload

Enables or disables the dynamic payload on the current VISM card.

cnflapdtrunkpvc

Assigns the PVC trunk type that carries LAPD messages for the current VISM card.

cnflntrunkcond

Enables or disables line conditioning on a VISM card line if a network alarm is encountered.

cnfrudptrunkrmtip

Modifies the remote IP address of VISM used in the ISDN PRI backhaul RUDP trunk for a specified session.

dellapdtrunk

Deletes an LAPD configured line.

delrtpcon

Deletes a static RTP VoIP trunking connection.

delrudptrunk

Deletes an ISDN PRI backhaul RUDP session that is associated with an LAPD.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsplapd

Displays data about an LAPD.

dsplapdtrunkpvc

Displays the assigned PVC trunk type that carries LAPD trunk messages for the current VISM card.

dsplapdtrunks

Displays the configuration data of all LAPD trunks.

dsprtpcnt

Displays the bearer counters (statistics) for a specific RTP VoIP trunking connection.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dsprtpconnstat

Displays the Real-time Transport Protocol (RTP) connection statistics for a specified endpoint.

dsprtpcons

Displays the configuration data of all static RTP VoIP trunking connections.

dsprudptrunk

Displays the configuration data of a specified ISDN PRI backhaul RUDP session.

dsprudptrunks

Displays the configuration data of all ISDN PRI backhaul RUDP sessions.


dsprtpcon

To display the configuration data of a specified static Real-Time Transport Protocol (RTP) VoIP trunking connection, use the dsprtpcon command in the VoIP switching/trunking and VoIP/switched ATM AAL1 SVC operating modes.

dsprtpcon conn-num

Syntax Description

conn-num

Connection identification number. It can be in the range from 1 to 248.


Command Modes

VoIP switching/trunking and VoIP/switched ATM AAL1 SVC

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example shows that the configuration data for the static RTP connection number 106 is displayed:

dsprtpcon 106

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

Related CommandsConnection Index: 1

Related Commands Endpoint Number: 1

Related Commands Local RTP Port: 49648

Related Commands Remote RTP Port: 49648

Related Commands Remote IP Address: 10.1.30.30

Related Commands Codec Type: G.711u

Related Commands Packetization Period: ten msec

Related Commands ECAN Status: Enable

Related Commands VAD: Off

Related Commands VAD Timer: 250 msec

Related Commands CAS Transport: On

Related Commands DTMF Transport: On

Related Commands ICS Enable: Disable

Related Commands Bearer TOS: 160

Related Commands Connection Mode: GW can send and recv packets

Related Commands Conn Alarm State: Active

Related Commands Conn Fail Reason: Not Fail

Related Commands Payload Type: 256

Related Commands Associated PVC: 131

Related Commands

Command
Description

addlapdtrunk

Adds an LAPD trunk to a specific VISM card line.

addrtpcon

Adds a static RTP VoIP trunking connection.

addrudptrunk

Adds an ISDN PRI backhaul RUDP session for an LAPD trunk connection.

clrrtpcnt

Clears the RTP counters (statistics) for a specific static RTP connection.

cnfdynamicpayload

Enables or disables the dynamic payload on the current VISM card.

cnflapdtrunkpvc

Assigns the PVC trunk type that carries LAPD messages for the current VISM card.

cnflntrunkcond

Enables or disables line conditioning on a VISM card line if a network alarm is encountered.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfrudptrunkrmtip

Modifies the remote IP address of VISM used in the ISDN PRI backhaul RUDP trunk for a specified session.

dellapdtrunk

Deletes an LAPD configured line.

delrudptrunk

Deletes an ISDN PRI backhaul RUDP session that is associated with an LAPD.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsplapd

Displays data about an LAPD.

dsplapdtrunkpvc

Displays the assigned PVC trunk type that carries LAPD trunk messages for the current VISM card.

dsplapdtrunks

Displays the configuration data of all LAPD trunks.

dsprtpcnt

Displays the bearer counters (statistics) for a specific RTP VoIP trunking connection.

dsprtpconnstat

Displays the Real-time Transport Protocol (RTP) connection statistics for a specified endpoint.

dsprtpcons

Displays the configuration data of all static RTP VoIP trunking connections.

dsprudptrunk

Displays the configuration data of a specified ISDN PRI backhaul RUDP session.

dsprudptrunks

Displays the configuration data of all ISDN PRI backhaul RUDP sessions.


cnfvbdcodec

To configure the voiceband data (VBD) upspeed codec on the current VISM card, use the cnfvbdcodec command in the VoIP switching/trunking operating mode.

cnfvbdcodec upspeed-codec payload-type

Syntax Description

upspeed-codec

Upspeed codec. It can be one of the following values:

1 = G.711u (Default for T1 VISM cards)

2 = G.711a (Default for E1 VISM cards)

3 = G.726-32K

4 = Clear channel

5 = G.723.1-H (Valid for template number 4 only)

6 = G.723.1-L (Valid for template number 4 only)

7 = G.726-16K

8 = G.726-24K

9 = G.726-40K

payload-type

Assigns the payload type—provides a mechanism for a codec to upspeed using a particular payload type. I can be in the range from 0 to 255. Default = 256.


Command Modes

VoIP switching/trunking

Usage Guidelines

VISM uses the configured codec even if, for example, the configured codec is G.726-32K and VISM is preconfigured with G.711. In this case, an actual downspeed would be performed.

If you configure clear channel, VISM does support a mixed system clock—VISM cannot be originated at a T1 line and terminated at an E1 line, or originated at an E1 line and terminated at a T1 line.

When VISM is configured with clear channel, the codec is not used in the fax/modem upspeed session because VISM cannot detect any tones using clear channel.

AAL2 modes obtain the upspeed codec from the AAL2 profile table. AAL1 does not support compression and therefore does not require upspeed.

The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.


Note Cisco recommends that you do not use upspeed-codec argument values 5 or 6 with this command.


Examples

The following example shows that the VBD upspeed codec is configured as G.711u and the 255 payload type:

cnfvbdcodec 1 255

Related Commands

Command
Description

addrtpcon

Adds a static RTP VoIP trunking connection.

cnfdynamicpayload

Enables or disables the dynamic payload on the current VISM card.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dspvbdcodec

Displays the upspeed codec used for VBD.


dspvbdcodec

To display the upspeed codec used for voiceband data (VBD), use the dspvbdcodec command in the VoIP switching/trunking operating mode.

dspvbdcodec

Syntax Description

This command has no arguments or keywords.

Command Modes

VoIP switching/trunking

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example shows that the upspeed codec used for VBD and the default payload type is displayed:

dspvbdcodec

VBD UpSpeed Codec:   G.711u
Payload Type     :   256

Related Commands

Command
Description

addrtpcon

Adds a static RTP VoIP trunking connection.

cnfdynamicpayload

Enables or disable the dynamic payload on the current VISM card.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfvbdcodec

Configures the VBD upspeed codec.

dspdynamicpayload

Displays the card level configuration of dynamic payload on the current VISM card.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.


Important Notes

This section describes the following elements of software Release 3.1(0) for VISM/VISM-PR:

"VISM Management Information Base" section

"Software Release 3.1(0) for VISM/VISM-PR CLI Commands" section

"VISM Redundancy" section

"VISM Call Rate" section

"Compatibility" section

"Limitations and Restrictions" section

VISM Management Information Base

The VISM Management Information Base (MIB) Version 0.0.30 is provided with the delivery of software Release 3.1(0) for VISM/VISM-PR, which bundles with the Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8830, and Cisco MGX 8850 software and is located on the Web at the following location:

http://www.cisco.com/kobayashi/sw-center/beta/

When the selected FW *.tar file or FW*.zip file is downloaded, untar or unzip the file and you will find all the latest MIBs bundled with this release.

The MIB is in standard ASN.1 form and can be compiled with most standards-based MIB compilers. Refer to the MIB release notes on CCO.

MIB Changes for Software Release 3.1(0) for VISM/VISM-PR

This section describes new, modified, and deprecated MIB objects, and new and modified traps for software Release 3.1(0) for VISM/VISM-PR. There are no new, modified, or deprecated traps for this release.

New MIB Objects

The following MIB objects are added for software Release 3.1(0) for VISM/VISM-PR:

MIB object contained in vismRtpConnGrpTable:

vismRtpPayloadType

MIB object contained in vismInteropGrp:

vismDynamicPT

MIB object contained in vismDspGrp:

vismPayloadType

MIB object contained in t38FaxRelayGrpTable:

t38T30ECM

Modified MIB Objects

The following MIB objects are modified for software Release 3.1(0) for VISM/VISM-PR:

MIB objects contained in cwVismT38FaxCapability:

t38HsDataPacketSize—range is modified from 10 - 40 to 10 - 30

38LsDataRedundancy

t38HsDataRedundancy

t38FaxInfoFieldSize

t38ErrCorrection

t38NSFCountryCode

t38NSFVendorCode

t38Redundancy

MIB objects contained in vismTrapObjGrp:

vismConfigChangeTypeBitMap

vismConfigChangeTypeBitMap

Deprecated MIB Objects

The following MIB objects are deprecated from software Release 3.1(0) for VISM/VISM-PR:

MIB object contained in t38FaxRelayGrpTable:

t38Redundancy

Software Release 3.1(0) for VISM/VISM-PR CLI Commands

Software Release 3.1(0) for VISM/VISM-PR includes many new, modified, and deprecated Command Line Interface (CLI) commands. See the blahblahblah section for the syntax and use of these commands.

New, Modified, and Deprecated CLI Commands

Table 2 describes the new CLI commands contained in software Release 3.1(0) for VISM/VISM-PR.

Table 2 New CLI Commands for Software Release 3.1(0) for VISM/VISM-PR 

Command
Description

cnfdynamicpayload

To enable or disable the dynamic payload on the current VISM card.

dspdynamicpayload

To display the card level configuration of dynamic payload on the current VISM card.


Table 3 describes the modified CLI commands contained in software Release 3.1(0) for VISM/VISM-PR.

Table 3 Modified CLI Commands for Software Release 3.1(0) for VISM/VISM-PR 

Command
Name

addrtpcon

Adds a static RTP VoIP trunking connection.

cnfrtpcon

Modifies an existing static RTP VoIP trunking connection.

cnfvbdcodec

Configures the VBD upspeed codec.

dsprtpcon

Displays the configuration data of a specific static RTP VoIP trunking connection.

dspvbdcodec

Displays the upspeed codec used for VBD.


VISM Redundancy

Refer to Table 4 for the support level for 1:N Service Module Redundancy (N = 1 through 11).

Table 4 Service Module Redundancy 

Front Card Model Number
Redundancy Support

MGX-VISM-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-8E1

1:N redundancy (bulk mode support for E1 lines only).

MGX-VISM-PR-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-PR-8E1

1:N redundancy (bulk mode support for E1 lines only).



Note You can use a VISM-PR card as a redundant card for a VISM card, but a VISM card cannot be used as a redundant card for a VISM-PR card.


There is support for Bulk Distribution using the SRM-3T3 and SRM-E (OC3) cards.

VISM Call Rate

Software Release 3.1(0) for VISM/VISM-PR handles at least 10 CAS, SS7, or PRI calls per second per VISM card.

Compatibility

VISM software interoperability with MGX 8830, 8850, MGX 8250, and MGX 8230 platform software is listed in Table 5.

Table 5 VISM Software Interoperability 

Product
CW2000 Name
Latest Firmware
Min. Firmware

AUSM-8E1/B

AUSM-8E1/B

20.0.2.0

20.0.2.0

AUSM-8T1/B

AUSM-8T1/B

20.0.2.0

20.0.2.0

AX-CESM-8E1

CESM-8E1

10.2.00

10.0.22

AX-CESM-8T1

CESM-8T1

10.2.00

10.0.22

AX-FRSM-8E1/E1-C

FRSM-8E1

20.0.1.0

10.0.23

AX-FRSM-8T1/T1-C

FRSM-8T1

20.0.1.0

10.0.23

AXSM-1-2488

AXSM-1-2488

3.0.10

3.0.10

AXSM-1-2488/B

AXSM-1-2488/B

3.0.10

3.0.10

AXSM-16-155

AXSM-16-155

3.0.10

3.0.10

AXSM-16-155/B

AXSM-16-155/B

3.0.10

3.0.10

AXSM-16-T3/E3

AXSM-16-T3/E3

3.0.10

3.0.10

AXSM-16-T3/E3/B

AXSM-16-T3/E3/B

3.0.10

3.0.10

AXSM-16-T3E3-E

AXSM-16-T3E3-E

3.0.10

3.0.10

AXSM-2-622-E

AXSM-2-622-E

3.0.10

3.0.10

AXSM-32-T1E1-E

AXSM-32-T1E1-E

3.0.0

3.0.0

AXSM-4-622

AXSM-4-622

3.0.10

3.0.10

AXSM-4-622/B

AXSM-4-622/B

3.0.10

3.0.10

AXSM-8-155-E

AXSM-8-155-E

3.0.10

3.0.10

BPX/IGX

BPX/IGX

9.3.42

9.2.42

CESM-8E1

CESM-8E1

20.0.2.0

20.0.2.0

CESM-8T1/B

CESM-8T1/B

20.0.2.0

20.0.2.0

CWM

11.0.10

10.5.101 patch 1

FRSM-12-T3E3

FRSM-12-T3E3

3.0.10

3.0.10

MGX-AUSM-8E1/B

AUSMB-8E1

10.2.00

10.0.23

MGX-AUSM-8T1/B

AUSMB-8T1

10.2.00

10.0.23

MGX-CESM-8T1/B

CESM-8T1/B

10.2.00

MGX-CESM-E3

CESM-E3

10.2.00

10.0.22

MGX-CESM-T3

CESM-T3

10.2.00

10.0.22

MGX-FRSM-2CT3

FRSM-2CT3

10.2.00

10.0.23

MGX-FRSM-2T3E3

FRSM-2T3

10.2.00

10.0.23

MGX-FRSM-2T3E3

FRSM-2E3

10.2.00

10.0.23

MGX-FRSM-HS1/B

FRSM-HS1/B

10.2.00

10.0.23

MGX-FRSM-HS2

FRSM-HS2

10.2.00

10.0.23

MGX-FRSM-HS2/B

FRSM-HS2/B

20.0.1.0

MGX-RPM-XF-512

MGX-RPM-XF-512

12.2(11)YP

12.2(8)YP

MGX-SRM-3T3/B

SRM-3T3

MGX-SRM-E

SRM-E

MGX-VISM-8E1

VISM-8E1

3.1(0)

1.5

MGX-VISM-8T1

VISM-8T1

3.1(0)

1.5

MGX-VISM-PR-8E1

VISM-PR-8E1

3.1(0)

3.1(0)

MGX-VISM-PR-8T1

VISM-PR-8T1

3.1(0)

3.1(0)

PXM1

PXM-1

1.2.10

1.1.40 and 1.2.0

PXM1-1-622

PXM1-OC12

1.2.10

1.1.40 and 1.2.0

PXM1-2-T3E3

PXM1-2T3E3

1.2.10

1.1.40 and 1.2.0

PXM1-4-155

PXM1-4OC3

1.2.10

1.1.40 and 1.2.0

PXM1E2

PXM1E

3.0.10

3.0.10

PXM452

PXM45

3.0.10

3.0.10

RPM

RPM

12.2(8)T4

12.2(8)T4

RPM IOS

RPM IOS

12.2(8)T4

RPM/B

RPM/B

12.2(8)T4

12.2(8)T4

RPM-PR

RPM-PR

12.2(11)T1

12.2(8)T4

MGX-RPM-XF

RPM-XF

12.2(11)YP

12.2(11)YP

MGX-RPM-PR-256/512

RPM-PR

12.2(11)T1

12.2(11)T1

SES

SES

3.0.10

1.0.14

1 CWM Release 10.5 does not support all of the new MIBs listed in the "VISM Management Information Base" section.

2 This card is not compatible with VISM cards.


VISM software interoperability with other Cisco products is described in Table 6.

Table 6 Software Release 3.1(0) for VISM/VISM-PR Interoperability with Other Cisco Products

Cisco 3810

12.2(8)T1

AS5400

122-10.7

Virtual Switch Controller Software

VSC 9.1.5


Table 7 describes the software images available for Release 3.1(0) for VISM/VISM-PR.

Table 7 Software Images for Release 3.1(0) for VISM/VISM-PR 

Product Name
Software Image
Firmware
Description

MGX-VISM-SW3100

003.001.000.000

vism_8t1e1_003.001.000.000.fw

This image does not support the CALEA1 feature.

MGX-VISM-LISW3100

003.051.000.000

vism_8t1e1_003.051.000.000.fw2

Use this image for CALEA1 feature support.

1 CALEA = Commission on Accreditation for Law Enforcement Agencies.

2 The CALEA implementation supports the CALEA law intercept confirmation interface.


Table 8 describes the software boot code and run-time firmware requirements for software Release 3.1(0) for VISM/VISM-PR.

Table 8 Software Release 3.1(0) for VISM/VISM-PR Software Boot and Run-time Firmware Requirements 

Board Pair
Latest Boot Code Version
Minimum Boot Code Version

MGX-VISM-8T1

vism_8t1e1_VI8_BT_3.1.01.fw

vism_8t1e1_VI8_BT_3.1.00.fw

MGX-VISM-8E1

vism_8t1e1_VI8_BT_3.1.01.fw

vism_8t1e1_VI8_BT_3.1.00.fw

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.1.01.fw

vism_8t1e1_VI8_BT_3.1.00.fw

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.1.01.fw

vism_8t1e1_VI8_BT_3.1.00.fw



Note Loading this release of the backup bootcode is required for existing VISM cards not using this new release.


Limitations and Restrictions

The following limitations and restrictions are valid for software Release 3.1(0) for VISM/VISM-PR:

Software Release 3.1(0) for VISM/VISM-PR requires you to use 64 Mb VISM cards or VISM-PR cards exclusively.

The switched AAL2 PVC operating mode is not supported in software Release 3.1(0) for VISM/VISM-PR.

Cisco recommends that you use the cnfcodecjtrdelay command to configure the jitter-delay argument to 20 msec when using DSP firmware versions 3.4 and 3.6.

Table 9 describes the design constraint which is identified in software Release 3.1(0) for VISM/VISM-PR.

Table 9 Known Design Constraint 

DDTs Issue
Description

CSCdv37382

The addcid command can put VISM into the fail state. If non-AAL5 cells are sent to an AAL5 PVC of VISM, this can cause the VISM SAR chip to hang and VISM to go into failed state. This is because, in case of AAL5, the last bit of the Payload type indicator is used to determine which cell contains the end of that payload. All cells which have this bit set to 0 are held in the reassembly buffer until the cell with this bit set to 1 arrives. In case of non-AAL5 cells, this bit will never get set to 1, and ultimately this buffer will overflow. So, care should be taken that only AAL5 cells are sent to AAL5 PVCs of VISM.


Installation and Upgrade Procedures

This section describes the following installation and upgrade procedures:

"VISM Firmware and Boot Code Download Procedure for PXM1" section

"VISM Firmware and Boot Code Download Procedure for PXM1E and PXM45" section

"VISM/VISM-PR Firmware Upgrade" section

"VISM to VISM-PR Hardware Upgrade" section

"Installing VISM Software Updates with PXM1 Cards" section

"VISM Boot Code Upgrade Procedure with PXM1 Cards" section

"VISM Downgrade Procedure" section

VISM Firmware and Boot Code Download Procedure for PXM1


Step 1 Download the selected revision of service module boot code into the service module in the selected slot by issuing the following commands:

a. tftp <node_name or IP address>

b. bin

c. put <backup boot> POPEYE@SM_1_0.BT

d. quit

Step 2 Proceed to Step 2c. to upgrade all VISM cards or proceed to Step 2d. to upgrade an individual VISM card.

a. tftp <node_name or IP address>

b. bin

c. put <FW file> POPEYE@SM_1_0.FW

quit

d. put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW

quit


Note Do not enter two put commands in the same TFTP session.


Step 3 Proceed to the "Installing VISM Software Updates with PXM1 Cards" section to install the download.


VISM Firmware and Boot Code Download Procedure for PXM1E and PXM45


Step 1 Access the image on the Cisco Web site in order to download the image.

Step 2 Use the ftp node-ip command, where node-ip is the IP address of the node to which you want to download the image, to download the image.

Step 3 Enter your username and password.

Step 4 Type cd C:FW to access the appropriate directory.

Step 5 Type bin.

Step 6 Use the put image-version, where image-version is the downloaded image from Step 1, to download the image to your C:FW directory.

Step 7 Type bye to exit the download procedure.


VISM/VISM-PR Firmware Upgrade

Software Release 3.1(0) for VISM/VISM-PR introduces the new VISM-PR card. Complete the following steps to gracefully upgrade from VISM cards to VISM-PR cards. You must ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_BT_3.1.00.fw.

The following versions of VISM software Release 3.1(0) are available:

300.001.000.000—without CALEA

003.051.000.000—with CALEA


Note You do not have to complete these instructions in order to use software Release 3.1(0) for VISM/VISM-PR; however, see the "VISM Features" section for a list of features that are not available to you if you do not perform this upgrade procedure.


VISM cards and VISM-PR cards use the same back cards. There are no new back cards introduced with this release. In the following procedure:

Perform the firmware upgrade in the following procedure on the VISM cards; do not remove the VISM cards and replace them with VISM-PR cards at this time.

Two VISM cards are involved in a redundancy group, initially with the primary card in the active state and the secondary card in the standby state.

Old-rev refers to the firmware before the upgrade (2.2).

New-rev refers to the firmware after the upgrade (3.1).


Step 1 Log in to the active PXM1 card (slot 7 or 8).

Step 2 Save the existing configuration as a contingency plan by entering:

savesmcnf <SM slot#>


This will save the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure, if necessary.

Step 3 Execute the PXM install command:

install sm <SM slot#> <new-rev>


where:

SM slot# is the slot number of the primary VISM card and new-rev is the file name of the new firmware (for example, vism_8t1e1_300.001.000.000.fw).

This command causes the secondary VISM card to reset and come up in the standby state, running the new-rev firmware. The primary VISM card is unaffected by this command.

Step 4 Execute the PXM newrev command:

newrev sm <SM slot#> <new-rev>


where:

SM slot# is the slot number of the primary VISM card and new-rev is the filename of the new firmware.

This command causes the primary VISM to reset and the secondary VISM card to become the active VISM running the new-rev firmware.

Step 5 Execute the PXM commit command:

commit sm <SMslot#> <new-rev>


where:

SM slot# is the slot number of the primary VISM card and new-rev is the filename of the new firmware.

The two VISM cards are now back to their original condition except that both cards are now running the new-rev firmware.

Step 6 Log in to the active VISM card and use the display commands (dspendpts, dspcasvar, etc.) to confirm that the configuration has been preserved through the upgrade process.


Note For more than one primary VISM card in a redundancy group, ensure that the secondary card is in the standby state and repeat Step 4 and Step 5 for each VISM card in the redundancy group.


It is also recommended that a further verification be performed by making some minor modifications to the configuration, checking that the changes have been executed correctly, and then changing the configuration back again.



Note If the VISM card is not part of a redundancy group, Step 1 to Step 3 are sufficient.


VISM to VISM-PR Hardware Upgrade

Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.


Caution You must install the redundant (standby) VISM-PR card first; failure to follow this recommendation results in traffic loss. In addition, do not remove an active VISM card from your chassis; ensure that you configure an active VISM card to the standby state before you remove it and replace it with a VISM-PR card.


Step 1 Remove the redundant (standby) VISM card from your chassis.

Step 2 Install a VISM-PR card in the slot you removed the VISM card from in Step 1.

Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).

Step 4 Remove the now redundant VISM card from your chassis.

Step 5 Install a VISM-PR card in the slot you removed the VISM card from in Step 4.

Step 6 Log into the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.

Step 7 Log into the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to insure that the correct card type is shown.

Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.

Step 9 Remove a standby VISM card from your chassis.

Step 10 Install a VISM-PR card in the slot you removed the VISM card from in Step 9.

Step 11 Repeat Step 9 and Step 10 to remove any remaining VISM cards in your chassis and replace them with VISM-PR cards.

Step 12 Repeat Step 6 and Step 7 on the remaining VISM-PR cards to insure the correct card type is shown.


Installing VISM Software Updates with PXM1 Cards

Software Release 3.1(0) for VISM/VISM-PR provides a procedure for the graceful upgrade (one in which the existing VISM configuration is preserved throughout the upgrade procedure) from the earlier VISM 2.0 release.


Caution Installing VISM software updates from VISM Release 2.2 with CALEA to VISM Release 3.0 without CALEA is not graceful.


Caution Temporary traffic loss occurs during Step 4 and Step 5 of the VISM graceful upgrade procedure of the Upgrade Procedure for software Release 3.1(0) for VISM/VISM-PR.

Initial Conditions

The following initial conditions are required before the graceful upgrade procedure can be started:

The MGX 8000 Series shelf must be configured with at least two VISM cards in a redundant configuration (refer to the add redundancy, addred, command in the MGX 8830, MGX 8850, MGX 8250, and MGX 8230 command references for more information).

The VISM cards must be running VISM 2.0 and be configured to the desired configuration.

The software Release 3.1(0) for VISM/VISM-PR must have been already downloaded to the MGX shelf.

Ensure that you have the version of VISM software that supports CALEA, if you are using the CALEA feature.

Upgrade Procedure

Upgrades are available for the following releases:

From VISM 1.5 to VISM 3.1

From VISM 2.1 to VISM 3.1

From VISM 2.2 to VISM 3.1

From VISM 3.0 to VISM 3.1

Installing VISM Software Updates with PXM1E or PXM45 Cards

Complete the following steps to update the VISM software when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:


Step 1 Log on to the active PXM1E or PXM45 card.

Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.

Step 3 Use the saveallcnf command to save the existing configuration as a contingency plan.

Step 4 Use the loadrev sm-primary-slot-num new-rev command, where sm-primary-slot-num is the slot number of the VISM/VISM-PR card you to which you want to install the new software, and new-rev is the new firmware version number for the VISM software.

Step 5 Use the runrev sm-primary-slot-num new-rev command to execute the download.

Step 6 Use the commitrev sm-primary-slot-num new-rev command to commit the new download to the VISM/VISM-PR card.

You have completed the steps. Proceed to the VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards.


VISM Boot Code Upgrade Procedure with PXM1 Cards

There is a new backup boot code change from VISM Release 2.2(0) to software Release 3.1(0) for VISM/VISM-PR. Complete the following steps to upgrade the new backup boot code when you are using PXM1 cards in your MGX 8000 Series chassis:


Note This procedure re-programs the VISM boot code for previous VISMs using the VISM runtime image version 1.0 to 2.0.



Step 1 Telnet to MGX shelf and cc to the VISM card.


Note VISM must be in the active state in order to update the VISM boot code.


Step 2 Access the server where the VISM boot code resides and TFTP the VISM boot code to the VISM card with the following procedure:

a. Type tftp <IP address of the MGX shelf>

b. Type bin at the tftp prompt.


Caution Ensure that you perform Step 2 b. If you to not perform Step 2 b. the boot code will be corrupted and not recoverable.

c. Type install [bt] [sm <slot>] <version> at the PXM prompt.


Caution Do not touch the VISM card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation will corrupt the boot code and it will not be recoverable.

When the boot code is being written to PROM, you will see comments displayed at the VISM prompt. This is normal and expected behavior.

Step 3 Use the resetcd command for VISM from the PXM card for the latest boot take effect.

Step 4 Type the version command to verify the correct boot code.


Note Step 4 is optional.


You have completed upgrading the new VISM backup boot code.


VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

There is a new backup boot code change from VISM Release 2.2(0) to software Release 3.1(0) for VISM/VISM-PR. Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:


Step 1 Complete the steps in the VISM Firmware and Boot Code Download Procedure for PXM1E and PXM45.

Step 2 Log on to the PXM1E or PXM45 card.

Step 3 Use the burnboot sm-primary-slot-num new-rev command, where sm-primary-slot-num is the slot number of the VISM/VISM-PR card you want to upgrade and new-rev is the firmware version number of the new VISM software, to upgrade the VISM/VISM-PR boot code.

The VISM/VISM-PR card automatically resets and becomes active with the latest boot code image. You have completed the boot code upgrade procedure.


VISM Downgrade Procedure

Use this procedure to downgrade VISM software from software Release 3.1(0) for VISM to the earlier VISM Releases 3.0, 2.2, 2.1, and 2.0. By following the downgrade procedure described here, the configurations will be retained after downgrade.


Note It is important to note that the configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.


Complete the following steps to downgrade the VISM software from software Release 3.1(0) for VISM/VISM-PR to Release 3.0, 2.2, 2.1, or 2.0:


Step 1 If the VISM card is in a redundancy group, remove the redundancy.

delred <SM slot#>


Step 2 Download the old-rev firmware onto the MGX shelf.

Step 3 Execute the PXM clrsmcnf command:

clrsmcnf <SM slot#>


where:

SM slot# is the slot number of the VISM card to be downgraded.

The VISM card will be reset on executing this command. Wait for the card to come active.

Step 4 Execute the PXM restoresmcnf command:

restoresmcnf -f <filename> -s <SM slot#>


where:

The filename is the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.

The SM slot# is the slot number of the VISM card to be downgraded.

The VISM card will be reset again. When the card comes active, it will have the old-rev firmware running and will have the old configuration.

Step 5 Reconfigure redundancy group, if required.


Caveats

This section describes resolved and open software caveats for this release of VISM. Caveats describe unexpected behavior or defects in VISM software.

Resolved Caveats

Table 10 describes the caveats issued against VISM software that have been resolved in software Release 3.1(0) for VISM/VISM-PR.

Table 10 Resolved Caveats for Software Release 3.1(0) for VISM/VISM-PR 

DDTs Issue
Description

CSCdt62553

Title: XRBK/CO4 does not work with subcell muxing enabled for some calls.

Description: Start calls on 48 endpoints with ground start CAS variant and subcell muxing enabled. Calls were Inter-VISM and Intra-MGX. Some calls failed with the "Network COT test failure" error. When running calls with subcell muxing disabled, it works fine.

Workaround: Disable subcell muxing.

CSCdv51636

ECAN is not bypassed for first VBD connection after a softswitch.

CSCdv60608

DTMF digits are being distorted during DTMF dialing from 4ESS to customer PBX.

CSCdv74047

RI: The tstcon command's result screen contains VISM prompt.

CSCdw78990

Cannot switch back from secondary call agent to primary call agent.

CSCdw88157

Unable to delete line after using the cnfln command from Port Proxy.

CSCdx06692

Symptom: The trap received has different var-binds than the MIB definition.

Conditions: This happens for 507xx channel traps.

Workaround: None.

CSCdx55593

Host can not handle Long IP packet size around 3000 bytes.

CSCdx73578

VISM 1:N redundancy on AAL2 SVC call setup fails when reverting to a VISM-PR card. Calls fail in AAL2 SVC mode after the failed card is returned to primary status.

CSCdx75181

VoIP trunking: With CALEA enabled, unable to add 248 RTP connections on a VISM E1 PR card.

If you are using the VoIP trunking operating mode on a VISM PR E1 card, with CALEA enabled and you try to add 248 RTP connections on two cards, one with CALEA enabled, the other with CALEA disabled, the result may be that on the card with CALEA enabled some of the connections seem to utilize more than 300 + 5% (RTCP) = 315 cells.

CSCdx76297

CAC also needs a minor change for CALEA VAD on calls.

CSCdx84300

While running calls at a high rate with RSVP, the VISM card may crash.

CSCdx86422

VISM does not respond to AUEP if mgcp protocol version mismatch.

CSCdx88658

Headline: The ECAN should be configured to bypass for COT tones.

Conditions: 2010 Hz COT tone is received from the TDM side on an endpoint with ECAN enabled.

Symptom: The echo canceller does not bypass for 2010 Hz COT tone (as well as other COT tones).

Workaround: None.

CSCdx90362

Symptom: IP_FREE_MESSAGE appears on HOST shellConn.

Condition: Problem is seen under heavy control traffic loads. In one particular test bed, due to misconfiguration bearer data is fed in control LCN and this problem shows up.

Workaround: Code is fixed to deal with this problem. To avoid running in this problem keep the control traffic low (6-7 calls per second).

CSCdx90604

HIMR: Bearer failing completely for AAL1 grooming.

CSCdx91260

HIMR: The clrrtpcnt command does not clear RTP packet loss counter for trunked cons.

CSCdx92478

VISM ECAN performance is poor when there are slips.

CSCdx94130

Symptom: If DTMF digits with an on time of less than 45 ms are sent, the VISM randomly fails to detect some of the digits.

Condition: Calls may fail if a network element sends DTMF digits with short durations.

Workaround: If possible, use DTMF digits with ON time greater than or equal to
45 ms.

CSCdx96032

The t38T30ECM object is missing in TFTP file on VISM-PR.

CSCdy00014

VISM 2.2 VDNS is broken if you cnfdnssrvr, resetcd, cnfdnssrvr again.

CSCdy00491

Symptom: IP connectivity to VISM is lost. Ping does not work on VISM and MGCP messages do not reach VISM.

Conditions: Occurs under heavy load from DM (RSVP), and from HOST (CC,IP).

Workaround: Maintain a low call rate when using RSVP.

CSCdy04208

Need to change loopback timeout to 5 seconds.

CSCdy11140

The addccs command leads to VISM card reset.

CSCdy15818

The cnfcanparam command accepts invalid value for the vad_duty_cycle 0.

CSCdy16988

The mg_adminstate and mg_adminstate_ctrl do not get populated in the vism_card table.

CSCdy17177

VoIP trunking: LAPD links do not come up active.

CSCdy20538

VISM connection fails after using the cnfrtpcon command with G.723 and option parameter.

CSCdy22284

NY: VISM cards go to the failed state when high rate E1 SS7 calls are made.

CSCdy23462

VISM resets after PXM45 switchcc with AAL2 SVC calls.

CSCdy23876

Symptom: When a call agent is setup to send and request DTMF digit notification, the VISM does not notify the call agent when it receives DTMF tones, and does not send out DTMF tones when the call agent notifies the VISM of DTMF digits.

Workaround: DTMF Relay does work without call agent notification; however, if interworking is involved. (H.323 / SIP interworking) then call agent notification is required. In this case DTMF digits can still be sent in-band but only if a noncompression codec is used.

CSCdy32004

New t38 MIB t38T3ECM is shown as ? for the dspt38params command.

CSCdy32628

When switchover in 1:N VISM configuration, it does not generate RSIP.

CSCdy33867

Disconnected endpoints should send RSIP when they receive a persistent event.

CSCdy39244

Disconnected endpoint : RSIP should be sent first for AUEP request.

CSCdy41151

Failure to make AAL2 SVC calls after PXM1E switchover.

CSCdy44975

VISM rejects the SDP message when it contains b=AS:80 parameter.

CSCdy49598

SLT: Terminating card crashes when running RSVP calls (both T1 and E1).

CSCdy54517

RSVP: When changing reservation direction VISM deletes all reservations.

CSCdy57347

VISM 1:N switchover the DNS cannot receive the packets properly.

CSCdy57707

SLT: Memory corruption when running announcement calls at 10 cps.

CSCdy58267

NY: DTMF relay not working when VISM used with RPM-XF.

CSCdy59917

M: The conttest command fails when go tone is 2010 Hz.

CSCdy60953

NY: Announcement StopPlay request does not stop announcement.

CSCdy62539

MGCI messages with improper versions handled incorrectly in VISM.

CSCuk34707

When a call agent is setup to send and request DTMF digit notification, the VISM does not notify the call agent when it receives the DTMF tones, and does not send out DTMF tones when the call agent notifies the VISM of the DTMF digits. DTMF Relay does work without call agent notification, however if interworking is involved H.323/SIP interworking), then call agent notification is required. In this case DTMF digits can still be sent in-band but only if a noncompression codec is used.


Open Caveats

Table 11 describes possible unexpected behavior by software Release 3.1(0) for VISM/VISM-PR.

Table 11 Open Caveats for Software Release 3.1(0) for VISM/VISM-PR 

DDTs Issue
Description

CSCds66369

Title: VISM telnet sessions lock, unable to cc to card until reset.

Description: The VISM card allows up to two sessions. Both of these sessions have become locked, which prevents the user from being able to cc to the card. This condition has been reported twice and is not reproducible in the lab.

Workaround: Reset the card.

CSCdt85106

Title: G.726-16k, 24k and 40k cannot be configured as Vbdcodec.

Description for VISM 2.2: G.726-16k, G.726-24k, and G.726-40K should not be configured as Vbdcodec for upspeeding during fax/modem calls. This feature is not available in VISM2.2 release.

Workaround: If configuring with VISM CLI commands, do not configure G.726-16k, G.726-24k, and G.726-40K with cnfvbdcodec. If configuring with SNMP, do not configure G.726-16k, G.726-24k, and G.726-40K for the vismUpspeedCodec MIB object.

Description for VISM 2.1: VISM does not allow G.726-16k, G.726-24k, and G.726-40K to be configured as Vbdcodec for upspeeding during fax/modem calls.

Workaround: None.

CSCdx24153

OAM cells drop in AAL2 trunking with G.711u codec, and VAD disabled in combination with VISM-PR E1 cards.

CSCdx65569

AAL2 SVC upspeed to clear channel fails when there are more than 24 CIDs.

CSCdx68992

AAL1 SVC-DSP failed to detect tones in AAL1 encapsulation. Mid-call DTMF is not working for AAL1 SVC grooming solution. Tones are transmitted to the other end instead of to the call agent.

CSCdx72468

DTMF relay fails between the 5400 and VISM.

CSCdy26382

Headline: VISM encapsulates UDPTL for T.38 over RTP.

Symptom: T.38 Fax will not be successful when VISM interoperates with other gateways like AS5400.

Conditions: VISM wrongly encapsulates the T.38 data packets (UDPTL) over RTP instead of directly encapsulating on UDP.

Workaround: None.

CSCdy36418

Title: VISM-PR card must be reset after initial installation into MGX shelf.

Symptom: Any VISM-PR card must be reset after initial installation into an MGX slot. Although the PXM displays the correct card type for the VISM-PR card (using dspcds command), when logged into the actual VISM-PR card, the dspcd command displays the card type as a VISM legacy card instead of a VISM-PR card. The VISM-PR card must be reset from the PXM in order for the card type to be displayed as a VISM-PR card and also to function as a VISM-PR card.

Conditions: Symptom occurs on MGX 8850 with VISM-PR cards running release 3.1.

Workaround: Complete the following steps:

1. Replace VISM legacy card with VISM-PR card and wait for it to become active.

2. Once active, switch to the VISM-PR card using the cc command.

3. Execute the dspcd command to verify the card type (if problem exists it will be shown as a VISM legacy card).

4. If shown as a VISM legacy card, reset the VISM-PR card from the PXM using the resetcd <slot#> command and wait for it to become active.

5. Once active, switch to the VISM-PR card and execute the dspcd command once again to verify that the card type is now displayed as a VISM-PR card.

CSCdy50084

High SVC Setup Failure—VPI/VCI Not Available.

CSCdy53390

NY: DTMF digits (relay) failing on VoIP connections.

CSCdy67348

AAL2 SVCs: Path confirmation fails on some endpoints with 248 SVCs. Endpoints with 192 SVCs are supported.

CSCdy82778

NY: In AAL2 SVC case, midcall digits sent to call agent and across the network.

CSCdy82951

VISM-PR card reboots when all E1 lines with CIDs goes into alarm.

CSCdz01636

VISM reboots when the domain name has a lengthy name.

Workaround: Use up to 32 characters for domain names.


Related Documentation

The following documents contains information that may be useful to software Release 3.1(0) for VISM/VISM-PR:

Cisco VISM Installation and Configuration Guide, Release 3.0

Cisco MGX 8850 and MGX 8950 Switch Command Reference

Cisco MGX 8850 Hardware Installation Guide, Release 3

Cisco MGX 8850, MGX 8950, MGX 8830 Software Configuration Guide, Release 3 (PXM45, PXM45/B, and PXM1E)

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html