Cisco VG350, Cisco VG310, and Cisco VG320 Configuration Examples

This appendix presents the following sample configurations for the Cisco VG350, Cisco VG310, and Cisco VG320:

 

Loop-length configuration

The following configuration shows the use of the loop-length command:

 
vg350#config t
Enter configuration commands, one per line. End with CNTL/Z.
vg350(config)#voice-port 2/0/0
vg350(config-voiceport)#loop-length ?
long long loop length
short short loop length
 
vg350(config-voiceport)#loop-length long
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
vg350(config-voiceport)#
*Mar 21 21:19:17.790: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:19:19.094: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#
 
default to loop-length short.

ren configuration

In the ren x configuration, x is the actual REN specified on the analog phone. It is important to enter a proper value for x that should match with the actual REN required on the analog phone in use. Normally, this REN number is specified on the back label of the analog phone.

The following example shows the ren command:
 
vg350(config-voiceport)#loop-length short
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
vg350(config-voiceport)#
*Mar 21 21:20:23.242: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:20:24.122: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#ren ? <<< with short loop FXS, ren 1-5 is supported
<1-5> REN Value
vg350(config-voiceport)#ren 5
vg350(config-voiceport)#loop-length long <<<< change loop-legnth from short to long when ren 5 is configured, warning msg is printed out
The existing ren configuration is changed to 2 due to loop-legnth long is configured
vg350(config-voiceport)#sh
vg350(config-voiceport)#no sh
vg350(config-voiceport)#
*Mar 21 21:20:44.354: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:20:45.242: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#ren ? <<<< with long loop FXS, ren 1 - 2 is supported
<1-2> REN Value

 

ring dc-offset configuration

The following example shows how to configure the dc-offset command. Default is no ring dc-offset:

vg350(config-voiceport)#loop-length long
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
vg350(config-voiceport)#
*Mar 21 21:34:28.370: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:34:29.274: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#ring dc-offset ? <<< this CLI is only existed for loop-length long FXS
10-volts Ring DC offset 10 volts
20-volts Ring DC offset 20 volts
24-volts Ring DC offset 24 volts
30-volts Ring DC offset 30 volts
35-volts Ring DC offset 35 volts
 
vg350(config-voiceport)#ring dc-offset 10
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
*Mar 21 21:34:42.986: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
vg350(config-voiceport)#
*Mar 21 21:34:44.478: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#loop-length short <<< change loop-length from long to short when ring dc-offset is configured, warning msg is printed out
The existing ring dc-offset configuration is removed due to loop-length short is configured
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
vg350(config-voiceport)#
*Mar 21 21:34:55.362: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:34:56.322: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up

 

cm-current-enhance configuration

note.gif

Noteblank.gif The cm-current-enhance command is used to improve immunity to extreme levels of longitudinal noise on the long loop-length FXS and the command should not be used under normal conditions.

The following example shows how to configure the cm-current-enhance command:

vg350(config-voiceport)#loop-length long
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
*Mar 21 21:41:05.362: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
vg350(config-voiceport)#
*Mar 21 21:41:06.778: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up
vg350(config-voiceport)#cm-current-enhance <<<< this CLI is only existed for loop-length long FXS
vg350(config-voiceport)#shut
vg350(config-voiceport)#no shut
vg350(config-voiceport)#
*Mar 21 21:41:18.778: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to Administrative Shutdown
*Mar 21 21:41:19.658: %LINK-3-UPDOWN: Interface Foreign Exchange Station 2/0/0, changed state to up

 

Default is no cm-current-enhance.

vmwi configuration

VMWI CLI is only applicable to loop start signaling FXS. Default is vmwi fsk.

This CLI is only applicable to analog FXS voice ports on SM-D-72FXS and SMD-48FXS-E modules. It is not applicable to FXS voice ports on motherboard slot (slot 0).

The following shows a sample configuration showing the vmwi command:

vg350(config-voiceport)#vmwi ?
dc-voltage Enable DC Voltage VMWI on this FXS port
fsk Enable FSK VMWI on this FXS port
 
vg350(config-voiceport)#vmwi dc-voltage
vg350(config-voiceport)#vmwi fsk
vg350(config-voiceport)#no vmwi

 

Configuring multiple ports and dial-peers in one instance

The following example shows how to configure multiple ports and dial-peers in one instance for Cisco VG350:

!
Voice-port 2/0/0 - 2/0/0-71
Caller-id enable
!
dial-peer group configuration <tag> pots
port all
service stcapp
 
!
Dial-peer voice 1 - 160
Service stcapp
!
!
note.gif

Noteblank.gif This example is also applicable to the Cisco VG310 and Cisco VG320 platforms that enable you to configure multiple ports and dial peers in one instance.

Configuring EnergyWise

The following shows how to configure the EnergyWise feature on the module:

xfr_cube(config)#energywise ?
allow Configure which EnergyWise settings are allowed on this domain
member
domain Set the EnergyWise domain this entity should join
endpoint Set the EnergyWise endpoint access options
importance A rating of the importance this EnergyWise parent entity has in
the network
keywords EnergyWise keywords associated with this parent entity
level Set the EnergyWise level of this parent entity
management energywise management access options
name EnergyWise name for this parent entity
neighbor Specify a static neighbor
role The role this EnergyWise entity has in the network
 
note.gif

Noteblank.gif This feature is not supported on Cisco VG310 and Cisco VG320 platforms.