Configuring and Managing the High-Density Packet Voice Feature Card [Support]

Table Of Contents

Configuring and Managing the High-Density Packet Voice Feature Card

Upgrading DSP Firmware on the High-Density Packet Voice Feature Card

Configuring the GSMAMR-NB Codec for the High-Density Packet VFC

Overview and Restrictions for the GSMAMR-NB Codec

How the AMR-NB Codec Works

Feature Limitations or Restrictions

GSMAMR-NB Codec Compliance with RFC 3267

Configuring the GSMAMR-NB Codec on the High-Density Packet VFC

Verifying and Troubleshooting the High-Density Packet VFC

Using Online Insertion and Removal to Replace the High-Density Packet VFC

Configuring and Managing the High-Density Packet Voice Feature Card

The High-Density Packet Voice Feature Card (VGD-FC) supports up to six high-density packet voice and fax digital signal processor (DSP) modules (VGD-PVDM2-64), providing scalability from 64 to 384 channels. The voice feature card (VFC) converts voice and fax calls into IP packets or frames that can be transmitted as voice over IP (VoIP) over a variety of transport technologies on the Cisco VGD 1T3 voice gateway.

You can manage the voice feature card at the slot level, digital signal processor (DSP) level, or channel level by using monitoring and troubleshooting commands. On the Cisco VGD 1T3 voice gateway, the hierarchy designation is slot/dsp and slot/channel.

This section contains the following procedures for configuring and managing the High-Density Packet Voice Feature Card (VFC) on the Cisco VGD 1T3 voice gateway:

•Upgrading DSP Firmware on the High-Density Packet Voice Feature Card

•Configuring the GSMAMR-NB Codec for the High-Density Packet VFC

•Verifying and Troubleshooting the High-Density Packet VFC

•Using Online Insertion and Removal to Replace the High-Density Packet VFC

Upgrading DSP Firmware on the High-Density Packet Voice Feature Card

The High-Density Packet VFC should work without specific modifications to the software configuration on the Cisco VGD 1T3 platform. However, to ensure that you have the latest version of firmware, you can use the Cisco IOS commands in this section to upgrade the firmware.

For more information about GSMAMR-NB DSPware, see the "Overview and Restrictions for the GSMAMR-NB Codec" section. To upgrade the DSP firmware of the High-Density Packet Voice Feature Card, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice dsp slot [/dsp] [slot [/dsp]]

4. firmware {location flash:filename | upgrade [busyout | reboot]}

5. exit

6. end

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
voice dsp slot [/dsp] [slot [/dsp]]
Example:

Router(config)# voice dsp 1/1
Enters config-voicedsp configuration mode and specifies the slot and DSP location or a range of slots and DSPs.

•For the slot argument, specify a value from 1 to 7 to specify the location of the High-Density Packet VFCs.

•For the dsp argument, specify a value from 1 to 24 to specify the location of the DSP.

•To specify a range, enter the first two arguments to specify the first slot and DSP in the range. The second two arguments specify the last slot and DSP in the range.

•Where slash marks appear in the command syntax, they are required.
Step 4
firmware {location flash:filename | upgrade 
[busyout | reboot]}
Example:

Router(config-voicedsp)# firmware location flash:123
Specifies the location and filename of firmware and timing for the upgrade.

•flash:—Loads the firmware from the flash NVRAM located within the router.

•filename—The firmware filename.

Note The maximum number of DSPware versions permitted in flash memory is nine.

•busyout—Starts the firmware upgrade immediately.

•reboot—Delays the firmware upgrade until the next reboot.
Step 5
exit
Example:

Router(config-voicedsp)# exit
Exits config-voicedsp configuration mode and returns to global configuration mode.
Step 6
end
Example:
Router(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Configuring the GSMAMR-NB Codec for the High-Density Packet VFC

This section provides information about the following:

•Overview and Restrictions for the GSMAMR-NB Codec

•GSMAMR-NB Codec Compliance with RFC 3267

•Configuring the GSMAMR-NB Codec on the High-Density Packet VFC

Overview and Restrictions for the GSMAMR-NB Codec

The Adaptive Multirate Narrow Band (AMR-NB) codec is a high complexity multimode codec that supports eight narrowband speech encoding modes with bit rates between 4.75 and 12.2 kbps. The sampling frequency used in AMR-NB is 8000 Hz and the speech encoding is performed on 20 ms speech frames. Therefore, each encoded AMR-NB speech frame represents 160 samples of the original speech.

The AMR-NB codec was originally developed and standardized by the European Telecommunications Standards Institute (ETSI) for Groupe Speciale Mobile (GSM) cellular systems. and chosen by the Third Generation Partnership Project (3GPP) as the mandatory codec for third generation (3G) cellular systems.

Note You must buy a license to access the DSPware that supports the AMR-NB codec. It is recommended that you purchase a Cisco SMARTnet contract in order to streamline the process of getting the AMR-NB codec DSPware. When obtaining your license, use the following part numbers:

•FRVGD-AMR-LIC for the Cisco VGD 1T3

•FRVGD-AMR-LIC for the Cisco VGD 1T3

For more information, contact your Cisco representative or visit the following Cisco.com website to obtain a Cisco SMARTnet contract:
http://www.cisco.com/en/US/partner/products/svcs/ps3034/ps2827/ps2978/serv_datasheet09186a0080 092491.html.

Table 1 contains codec mode and bit rate information for the AMR codec.

Table 1 AMR Codec Modes and Bit Rates

Codec Mode

Bit Rate (kbps)

0

4.75

1

5.15

2

5.90

3

6.70

4

7.40

5

7.95

6

10.2

7

12.2

8¹

1.80

¹Used for Silence Indication Detection (SID) frames.

How the AMR-NB Codec Works

The multirate encoding (or multimode) capability of AMR-NB is designed for preserving high speech quality under a wide range of transmission conditions. Unlike other codecs, the AMR-NB codec can adapt to different bit rates (see Table 1) based on channel conditions during the call.

To perform mode adaptation, the decoder (speech receiver) sends a signal to the encoder (speech sender) to indicate which new mode it prefers. This mode-change signal is called codec mode request (CMR). Because speech is sent in both directions between the two ends in most sessions, the mode requests from the decoder at one end to the encoder at the other end are sent in a piggyback form over the speech frames in the reverse direction; there is no out-of-band signaling needed for sending CMRs. The Cisco VGD 1T3 cannot initiate CMRs and received CMRs can be processed. For more information about AMR-NB codecs, see RFC 3267.

Feature Limitations or Restrictions

•All the DSPs in the system must be upgraded with the GSMAMR-NB DSPware.

•The following message is displayed when an upgrade takes place if a version of DSPware other than the recommended version is uploaded:
WARNING: Recommended GSM AMR-NB supported DSPware for this Cisco IOS image is X.Y.Z 
Where X.Y.Z changes depending on the Cisco IOS image that is used by the customer.
This warning has no impact on the firmware upgrade and calls can be brought up with a version of DSPware that is not the recommended version.

GSMAMR-NB Codec Compliance with RFC 3267

GSMAMR-NB codec support is compliant with RFC 3267. Specifications for RFC 3267 are supported by the High-Density Packet Voice Feature Card:

•The Cisco VGD 1T3 does not initiate CMRs. However, these platforms can process the received CMRs.

•RFC 3267 allows for the sending of redundant voice frames with the same sequence number and time stamp. The Cisco VGD 1T3 platforms do not send redundant packets, but they can receive redundant frames. When redundancy is used, RFC 3267 allows for different compression modes to be used for redundant frames. The standard recommends that when two redundant frames are received accurately, the frame with the lower compression (highest bit rate) be used. The

•Cisco VGD 1T3 instead uses the frame that is first received.

•The following apply to the codec gsmamr-nb command used to configure the GSMAMR-NB codec:

–Cisco VGD 1T3 does not support any of the parameter changes after the call is up.

–Support is provided for both octet-aligned and bandwidth-efficient frame formats.

–Support is provided for all eight modes of AMR-NB codec.

–The gateway can change to any mode at any time, which translates to mode-change-period of 20 ms and mode-change-neighbor value of 0.

–CRC is supported.

–Only supported value for maxptime and ptime arguments is 20 ms.

–Robust sorting and interleaving are not supported.

•The only supported value for the channels argument is 1.

Configuring the GSMAMR-NB Codec on the High-Density Packet VFC

To configure GSMAMR-NB codec support on the High-Density Packet VFC for Cisco VGD 1T3 voice gateways, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice tag {pots | mmoip | voip}

4. codec gsmamr-nb [packetization-period 20] [encap rfc3267] [frame-format {bandwidth-efficient | octet-aligned [crc | no-crc]}] [modes modes-value]

5. rtp payload-type cisco-codec-gsmamrnb number

6. exit

7. end

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
dial-peer voice tag {pots | mmoip | voip}
Example:

Router(config)# dial-peer voice 10 voip
Defines a particular dial peer, specifies the method of voice encapsulation, and enters dial-peer configuration mode:

•tag—Digits that define a particular dial peer. Range is from 1 to 2147483647.

•pots—Indicates that this is a POTS peer that uses VoIP encapsulation on the IP backbone.

•mmoip—Indicates that this is a POTS peer that uses MMoIP encapsulation on the IP backbone.

•voip—Indicates that this is a VoIP peer that uses voice encapsulation on the POTS network.
Step 4
codec gsmamr-nb [packetization-period 20][encap 
rfc3267] [frame-format {bandwidth-efficient | 
octet-aligned [crc | no-crc]}] [modes 
modes-value]
Example:

Router(config-dial-peer)# codec gsmamr-nb packetization-period 20 encap rfc3267 frame-format octet-aligned crc
Specifies the GSMAMR-NB codec for a dial peer:

•packetization-period 20—Sets the packetization period to 20 ms.

•encap rfc3267—Sets the encapsulation value to comply with RFC 3267.

•frame-format—Specifies a frame format. Supported values are octet-aligned and bandwidth-efficient. The default is octet-aligned.

•crc | no-crc—CRC is applicable only for octet-aligned frame format. If you enter bandwidth-efficient frame format, the crc | no-crc options will not be available because they are inapplicable.

•modes—Valid values are from 0 to 7. You can specify modes as a range (for example, 0-2), or individual modes separated by commas (for example, 2,4,6), or a combination of the two (for example, 0-2,4,6-7). Applicable only to GSMAMR-NB codec support.
Step 5
rtp payload-type cisco-codec-gsmamrnb number 
Example:

Router(config-dial-peer)# rtp payload-type cisco-codec-gsmamrnb 110
Configures a dynamic payload-type value for the GSMAMR-NB codec.

•The default value is 117.

•There are other options available with this command, but an abbreviated syntax is shown here to clearly indicate the keywords and options for the GSMAMR-NB codec.
Step 6
exit
Example:

Router(config-dial-peer)# exit
Exits dial-peer voice configuration mode and returns to global configuration mode.
Step 7
end
Example:
Router(config)# end
Exits global configuration mode and returns to privileged EXEC mode.
Verifying and Troubleshooting the High-Density Packet VFC

To verify the configuration of the High-Density Packet VFC, use the show running-config command. Sample output is located in the "Configuration Examples for the High-Density Packet Voice Feature Card" chapter.

For troubleshooting, steps 1 through 7 are useful to obtain status and statistics on network operation. Steps 8 through 10 can be used to obtain debugging information for the High-Density Packet VFC.

SUMMARY STEPS

1. show voice dsp [active | channel {operational-status | statistics | traffic [slot [/dsp [/channel]]]} | crash-dump | detailed | error | group | signaling | summary | version | voice]

2. show voice dsp summary

3. show voice hpi capture

4. show call active fax

5. show call active voice

6. show chassis slot slot

7. show diag

8. debug voice dsp crash-dump {detail | keepalive}

9. debug dsp-resource-manager flex {all | detail | download | dspfarm | dspstats | error | function}

10. debug voice hpi {all | capture | command | default | detail | error | function | inout | nack | notification | response | stats}

DETAILED STEPS

Step 1 show voice dsp [active | channel {operational-status | statistics | traffic [slot [/dsp [/channel]]]} | crash-dump | detailed | error | group | signaling | summary | version | voice]

The following example shows the operational status for slot 3, dsp 2, channel 15 on a Cisco VGD 1T3 gateway:
Router# show voice dsp channel operational-status 3/2/15
Slot/DSP/channel -- 3/2/15
Service Type                        : Fax-relay service
Max. transmission rate              : 14400 bps
: 20 ms
TCF generation                      : transparent
Transmit level                      : -10 dBm
Encapsulation protocol              : UDPTL
ECM Disable                         : Not disabled
Current playout delay               : 13 ms
Min/Max playout delay               : 1/240 ms
Buffer underflow discard            : 0
Buffer overflow discard             : 0
End-point detection errors          : 0
Tx/Rx Fax packets                   : 979/35
Tx/Rx duration                      : 20549/4412 ms
Tx/Rx pages                         : 0/0
Out of sequence packets             : 0
Bad protocol headers                : 0
Fax state                           : V.17 demodulation - short train 14400 bps
Current signal level                : 4.5 dBm
Phase jitter                        : 253 degrees
Frequency offset                    : 0 Hz
Packet loss concealment count       : 0
TX/RX Byte Count                    : 0/23
Recent HS Modulation                : V.17 modulation - short train 14400 bps
Number of SSRC changes              : 0
Number of payload violations        : 0
Note If the GSMAMR-NB codec has been configured, and there are calls using this codec, the following statistics will be included in the output for the show voice dsp channel operational-status command.
CodecEncodeRate=7
CodecDecodeRate=7
CodecEncodeChanges=0
CodecDecodeChanges=0
CodecCrcFails=0
CodecBadFrameQuality=0
CodecInvalidCMRs=0
CodecInvalidFrameType=0
Step 2 show voice dsp summary

This command generates a display of the DSP status and summary information for each DSP. The following is sample output from this command:
Router# show voice dsp summary
Total number of DSPs = 24
Codectype       Calls    Codectype       Calls    Codectype       Calls
g729r8              1    
Legend       :
======
Channel state: (s)shutdown   (a)active call (d)download pending
               (b)busiedout  (B)bad         (p)busyout pending
Call type    : (v)voice      (f)fax-relay   (_)not in use
Summary   :
=======
Channels  :  Total 384  In-Use    001  
Calls     :  Total 001  Voice     001  Fax  000
Credits   :  Free  350  Disabled  032 
      DSP      DSP        DSP    Channel            Call            
DSP#  State    Complexity Resets State              Type
3/1   ACTIVE   FLEXI      0      a_______ ________  v_______ ________
3/2   B-OUT    FLEXI      0      bbbbbbbb bbbbbbbb  ________ ________
3/3   OOS      FLEXI      0      ssssssss ssssssss  ________ ________
3/4   ACTIVE   FLEXI      1      ________ ________  ________ ________
3/5   ACTIVE   FLEXI      0      ________ ________  ________ ________
3/6   ACTIVE   FLEXI      0      ________ ________  ________ ________
3/7   ACTIVE   FLEXI      0      ________ ________  ________ ________
3/8   ACTIVE   FLEXI      0      ________ ________  ________ ________
3/9   ACTIVE   FLEXI      0      ________ ________  ________ ________
3/10  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/11  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/12  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/13  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/14  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/15  ACTIVE   FLEXI      0      ________ ________  ________ ________
3/16  ACTIVE   FLEXI      0      ________ ________  ________ ________
4/5   ACTIVE   FLEXI      0      ________ ________  ________ ________
4/6   ACTIVE   FLEXI      0      ________ ________  ________ ________
4/7   ACTIVE   FLEXI      0      ________ ________  ________ ________
4/8   ACTIVE   FLEXI      0      ________ ________  ________ ________
4/9   ACTIVE   FLEXI      0      ________ ________  ________ ________
.
.
.
Step 3 show voice hpi capture

In the following example, the show voice hpi capture command is used in privileged EXEC mode to check on the status of the logger before, during, and after configuration:
Router# show voice hpi capture 
HPI Capture is on and is logging to URL ftp://10.23.184.216/d:\test_data.dat
1 messages sent to URL, 0 messages dropped
Message Buffer (total:inuse:free)  2134:0000:2134Buffer 
Memory:699952 bytes, Message size:328 bytes
Step 4 show call active fax

The following is sample output from the command that shows no fax activity on the router:
Router# show call active fax
Telephony call-legs: 0
SIP call-legs: 0
H323 call-legs: 0
Call agent controlled call-legs: 0
SCCP call-legs: 0
Multicast call-legs: 0
Total call-legs: 0
Step 5 show call active voice

The following is sample output from the command that shows statistics for active voice calls on the router:
Router# show call active voice
GENERIC:
SetupTime=94523746 ms
Index=448
PeerAddress=##73072
PeerSubAddress=
PeerId=70000
PeerIfIndex=37
LogicalIfIndex=0
ConnectTime=94524043
DisconectTime=94546241
CallOrigin=1
ChargedUnits=0
InfoType=2
TransmitPackets=6251
TransmitBytes=125020
ReceivePackets=3300
ReceiveBytes=66000
VOIP:
ConnectionId[0x142E62FB 0x5C6705AF 0x0 0x385722B0]
RemoteIPAddress=171.68.235.18
RemoteUDPPort=16580
RoundTripDelay=29 ms
SelectedQoS=best-effort
tx_DtmfRelay=inband-voice
SessionProtocol=cisco
SessionTarget=ipv4:171.68.235.18
OnTimeRvPlayout=63690
GapFillWithSilence=0 ms
GapFillWithPrediction=180 ms
GapFillWithInterpolation=0 ms
GapFillWithRedundancy=0 ms
HiWaterPlayoutDelay=70 ms
LoWaterPlayoutDelay=30 ms
ReceiveDelay=40 ms
LostPackets=0 ms
EarlyPackets=1 ms
LatePackets=18 ms
VAD = disabled
CoderTypeRate=g729r8
CodecBytes=20
cvVoIPCallHistoryIcpif=0
SignalingType=cas
Step 6 show chassis slot

The following example shows the hardware information for all the slots (1 through 7) on a Cisco VGD 1T3:
vgd 1t3# show chassis slot
Slot 1:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Slot 2:
DFC type is VGD VGD-FC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
Slot 3:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Slot 4:
DFC type is VGD CT3 DFC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
Slot 5:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Slot 6:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Slot 7:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Step 7 show chassis slot slot

The following examples show the hardware information for slot 2 and for slot 4 individually on the Cisco VGD 1T3 voice gateway:
vgd 1t3# show chassis slot 2
Slot 2:
DFC type is VGD VGD-FC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
vgd 1t3# show chassis slot 4
Slot 4:
DFC type is VGD CT3 DFC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
Step 8 show diag

The following example shows diagnostic information on a per-slot basis for a Cisco VGD 1T3:
Router# show diag
Slot 0:
VGD Motherboard
Manufacture Cookie Info:
        Board ID                 : 0x603
        Hardware Revision        : 2.6
        Top Assy. Part Number    : 800-25673-01
        Part Number              : 73-9526-02
        Board Revision           : C0
        Fab Part Number          : 28-6926-02
        Platform features        : 00 00 00 00 
        Processor type           : AA 
        Product (FRU) Number     :                   
        PCB Serial Number        : JAE09148V9A
        Chassis MAC Address      : 0013.803e.8b44
        MAC Address block size   : 2
        CLEI Code                : 
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : V01 
 EEPROM contents (hex):
          0x00: 04 FF 40 06 03 41 02 06 C0 46 03 20 00 64 49 01
          0x10: 82 49 25 36 02 42 43 30 85 1C 1B 0E 02 C9 84 00
          0x20: 00 00 00 09 AA CB 92 20 20 20 20 20 20 20 20 20
          0x30: 20 20 20 20 20 20 20 20 20 C1 8B 4A 41 45 30 39
          0x40: 31 34 38 56 39 41 C3 06 00 13 80 3E 8B 44 43 00
          0x50: 02 C6 8A FF FF FF FF FF FF FF FF FF FF 03 00 81
          0x60: 00 00 00 00 04 00 89 56 30 31 20 FF FF FF FF FF
 FRU NUMBER : VGD
Slot 1:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Master PLD/FPGA Rev 0x0006
Slot 2:
DFC type is VGD VGD-FC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Cookie Info:
Manufacture Cookie Info:
        Board ID                 : 0x4BE
        Hardware Revision        : 1.1
        Part Number              : 73-9527-01
        Board Revision           : A0
        Fab Part Number          : 28-6928-01
        Product (FRU) Number     : 
        PCB Serial Number        : JAE09096VWJ
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : V01 
 EEPROM contents (hex):
          0x00: 04 FF 40 04 BE 41 01 01 82 49 25 37 01 42 41 30
          0x10: 85 1C 1B 10 01 CB 92 00 00 00 00 00 00 00 00 00
          0x20: 00 00 00 00 00 00 00 00 00 C1 8B 4A 41 45 30 39
          0x30: 30 39 36 56 57 4A 03 00 81 00 00 00 00 04 00 89
          0x40: 56 30 31 20 FF FF FF FF FF FF FF FF FF FF FF FF
DFC Cookie Info:
Manufacture Cookie Info:
        Board ID                 : 0x4CF
        Hardware Revision        : 1.0
        Part Number              : 73-9980-01
        Board Revision           : 03
        Fab Part Number          : 28-7322-01
        Product (FRU) Number     : aa
        PCB Serial Number        : JAB091100N2
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : VP1
 EEPROM contents (hex):
          0x00: 04 FF 40 04 CF 41 01 00 82 49 26 FC 01 42 30 33
          0x10: 85 1C 1C 9A 01 CB 82 61 61 C1 8B 4A 41 42 30 39
          0x20: 31 31 30 30 4E 32 03 00 81 00 00 00 00 04 00 89
          0x30: 56 50 31 00 D9 02 40 C1 FF FF FF FF FF FF FF FF
 FRU NUMBER : VGD-FC=
        PVDM Slot 3:
        64-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card
        Hardware Revision        : 3.2
        Part Number              : 73-8541-04
        Board Revision           : A0
        Deviation Number         : 0
        Fab Version              : 03
        PCB Serial Number        : FOC09040A93
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Processor type           : 00 
        Product (FRU) Number     : PVDM2-64
        Version Identifier       : NA  
        EEPROM format version 4
        EEPROM contents (hex):
          0x00: 04 FF 40 03 EC 41 03 02 82 49 21 5D 04 42 41 30
          0x10: 88 00 00 00 00 02 03 C1 8B 46 4F 43 30 39 30 34
          0x20: 30 41 39 33 03 00 81 00 00 00 00 04 00 09 00 CB
          0x30: 88 50 56 44 4D 32 2D 36 34 89 4E 41 20 20 D9 02
          0x40: 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
          0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Carrier Card Master PLD/FPGA Rev 0x0006
VGD-FC FPGA Rev 0x0008
Slot 3:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Cookie Info:
Manufacture Cookie Info:
        Board ID                 : 0x4BE
        Hardware Revision        : 1.1
        Part Number              : 73-9527-01
        Board Revision           : A0
        Fab Part Number          : 28-6928-01
        Product (FRU) Number     : 
        PCB Serial Number        : JAE09096VWJ
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : V01 
 EEPROM contents (hex):
          0x00: 04 FF 40 04 BE 41 01 01 82 49 25 37 01 42 41 30
          0x10: 85 1C 1B 10 01 CB 92 00 00 00 00 00 00 00 00 00
          0x20: 00 00 00 00 00 00 00 00 00 C1 8B 4A 41 45 30 39
          0x30: 30 39 36 56 57 4A 03 00 81 00 00 00 00 04 00 89
          0x40: 56 30 31 20 FF FF FF FF FF FF FF FF FF FF FF FF
Carrier Card Master PLD/FPGA Rev 0x0006
Slot 4:
DFC type is VGD CT3 DFC
OIR events:
        Number of insertions = 0, Number of removals = 0
DFC State is DFC_S_OPERATIONAL
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Cookie Info:
Manufacture Cookie Info:
        Board ID                 : 0x4BE
        Hardware Revision        : 1.1
        Part Number              : 73-9527-01
        Board Revision           : A0
        Fab Part Number          : 28-6928-01
        Product (FRU) Number     : 
        PCB Serial Number        : JAE09117JXB
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : V01 
 EEPROM contents (hex):
          0x00: 04 FF 40 04 BE 41 01 01 82 49 25 37 01 42 41 30
          0x10: 85 1C 1B 10 01 CB 92 00 00 00 00 00 00 00 00 00
          0x20: 00 00 00 00 00 00 00 00 00 C1 8B 4A 41 45 30 39
          0x30: 31 31 37 4A 58 42 03 00 81 00 00 00 00 04 00 89
          0x40: 56 30 31 20 FF FF FF FF FF FF FF FF FF FF FF FF
DFC Cookie Info:
Manufacture Cookie Info:
 EEPROM Type 0x0001, EEPROM Version 0x04, Board ID 0x01,
 Board Hardware Version 6.0, Item Number 73-4089-07,
 Board Revision A0, Serial Number JAE08127CMG,
 PLD/ISP Version 48.53,  Manufacture Date 11-Jun-2004.
 RMA Number1 <unset>, RMA Number2 <unset>
 EEPROM format version 0x1
 EEPROM contents (hex):
  0x00: 00 01 04 01 06 00 00 49 00 0F F9 07 41 00 4A 41
  0x10: 45 30 38 31 32 37 43 4D 47 00 00 00 00 00 14 04
  0x20: 06 0B 30 35 FF FF FF FF FF FF FF FF FF FF FF FF
  0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
 FRU NUMBER : VGD-DFC-CT3=
Trunk DFC Info:
 PLD Version 0x6, PLX9054 Revision 0xC,
 Boot ROM Version 0x2.
Carrier Card Master PLD/FPGA Rev 0x0006
Slot 5:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Cookie Info:
Manufacture Cookie Info:
        Board ID                 : 0x4BE
        Hardware Revision        : 1.1
        Part Number              : 73-9527-01
        Board Revision           : A0
        Fab Part Number          : 28-6928-01
        Product (FRU) Number     : 
        PCB Serial Number        : JAE09117JXB
        RMA Test History         : 00
        RMA Number               : 0-0-0-0
        RMA History              : 00
        Version Identifier       : V01 
 EEPROM contents (hex):
          0x00: 04 FF 40 04 BE 41 01 01 82 49 25 37 01 42 41 30
          0x10: 85 1C 1B 10 01 CB 92 00 00 00 00 00 00 00 00 00
          0x20: 00 00 00 00 00 00 00 00 00 C1 8B 4A 41 45 30 39
          0x30: 31 31 37 4A 58 42 03 00 81 00 00 00 00 04 00 89
          0x40: 56 30 31 20 FF FF FF FF FF FF FF FF FF FF FF FF
Carrier Card Master PLD/FPGA Rev 0x0006
Slot 6:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Master PLD/FPGA Rev 0x0006
Slot 7:
DFC type is VGD Empty DFC
DFC is not powered
OIR events:
        Number of insertions = 0, Number of removals = 0
Error events (Bus errors, PCI errors):
        Number of errors recovered = 0
Carrier Card Master PLD/FPGA Rev 0x0006
Step 9 debug voice dsp crash-dump {detail | keepalive}

Use this command to turn on the function for detailed DSP crash-dump debugging or to debug DSP crash-dump keepalives.

Step 10 debug dsp-resource-manager flex {all | detail | download | dspfarm | dspstats | error | function}

To turn on error debugging for the DSP resource manager function for flexible codec complexity, use the following command (a response from the command-line interface indicates that the function is turned on):
Router# debug dsp-resource-manager flex error
flexdsprm error debugging is on
To turn off error debugging for the DSP resource manager function for flexible codec complexity, use the following command (a response from the command-line interface indicates that the function is turned off):
Router# undebug dsp-resource-manager flex error
flexdsprm error debugging is off
Step 11 debug voice hpi {all | capture | command | default | detail | error | function | inout | nack | notification | response | stats}

Use this command to debug voice hpi functions. Use the available keywords to customize the output and focus the debug capability.

Using Online Insertion and Removal to Replace the High-Density Packet VFC

High-Density Packet VFCs are hot-swappable and replaceable (using online insertion and removal [OIR]). However, you should complete the following steps before removing the card:

SUMMARY STEPS

1. enable

2. busyout slot

3. show busyout slot

4. show chassis slot slot

5. clear voice dsp {channels | error} [slot[/dsp][/channel]] [slot[/dsp][/channel]]

6. Remove the High-Density Packet VFC from the slot.

7. Insert the new High-Density Packet VFC in the slot.

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

busyout slot
Example:

Router# busyout 2

Disconnects calls on the card.

•The slot argument identifies the location of the High-Density Packet VFC in the chassis.

Step 3

show busyout slot
Example:

Router# show busyout 2

Shows information that indicates when busyout is complete and all calls are disconnected.

•The slot argument identifies the location of the High-Density Packet VFC in the chassis.

•The associated configuration of the High-Density Packet VFC is automatically removed from the system configuration.

Step 4

show chassis slot slot
Example:

Router# show chassis slot 2

During the busyout process, the show chassis slot displays the state of the High-Density Packet VFC as DFC_S_REMOVING.

•The slot argument identifies the location of the High-Density Packet VFC in the chassis.

•Confirm the completion of the busyout by repeating the show chassis slot slot command until the status changes to DFC_S_REMOVED.

Step 5

clear voice dsp {channels | error} [slot[/dsp][/channel]] [slot[/dsp][/channel]]

(Optional) Forces a busyout of all calls on a channel. Use this command to forcefully busyout any remaining calls on specific channels, slots, or DSPs.

•channels—Clears DSP calls on a specific channel or a range of channels.

•errors—Clears DSP error statistics.

•/slot—(Optional) Specifies either a single slot or the first slot in a range. To specify a range of slots, you can enter a second slot in the syntax of this argument. The second slot specifies the end of the range. All slots in the range are affected by the command.

•/dsp—(Optional) Specifies either a single DSP on the slot or the first DSP in a range. To specify a range of DSPs, you can enter a second DSP in the syntax of this argument. The second DSP specifies the end of the range. All DSPs in the range are affected by the command.

•/channel—(Optional) Specifies either a single channel on the DSP or the first channel in a range. To specify a range of channels, you can enter a second channel in the syntax of this argument. The second channel specifies the end of the range. All channels in the range are affected by the command.

Step 6

Remove the High-Density Packet VFC from the slot.

The High-Density Packet VFC is physically removed from the chassis.

Step 7

Insert the High-Density Packet VFC in the slot.

When the High-Density Packet VFC is reinserted in the chassis, the card is automatically detected and activated.

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2008-2009 Cisco Systems, Inc. All rights reserved.

Hierarchical Navigation

Support

Configuring and Managing the High-Density Packet Voice Feature Card

Downloads

Table Of Contents

Configuring and Managing the High-Density Packet Voice Feature Card

Upgrading DSP Firmware on the High-Density Packet Voice Feature Card

SUMMARY STEPS

DETAILED STEPS

Configuring the GSMAMR-NB Codec for the High-Density Packet VFC

Overview and Restrictions for the GSMAMR-NB Codec

How the AMR-NB Codec Works

Feature Limitations or Restrictions

GSMAMR-NB Codec Compliance with RFC 3267

Configuring the GSMAMR-NB Codec on the High-Density Packet VFC

SUMMARY STEPS

DETAILED STEPS

Verifying and Troubleshooting the High-Density Packet VFC

SUMMARY STEPS

DETAILED STEPS

Using Online Insertion and Removal to Replace the High-Density Packet VFC

SUMMARY STEPS

DETAILED STEPS

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)