The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This appendix describes the software, features, and platforms supported by the Cisco VG350, Cisco VG310, and Cisco VG320 Analog Voice Gateway and contains the following sections:
This feature provides the capability to capture the PCM data flow through the ISR G2 motherboard TDM switch.
You can find additional information about this feature at the following URL: http://www.cisco.com/en/US/docs/ios-xml/ios/fundamentals/command/monitor_event-trace_
through_Q.html
This feature detects the presence of a cable that is connected between analog FXS and FXO VICs.
This feature only supports the following VIC/EM:
Note This feature is applicable on Cisco VG350, Cisco VG310 and VG320 platforms. However, it is not supported on Direct-Inward-Dial (DID-IN) and E/M voice port.
You can find additional information about this feature at the following URLs:
The Cisco VG350 Voice Gateway is loaded with image (vg350-universalk9_npe-mz) and the Cisco VG310 and Cisco VG320 are loaded with image (vg3xx-universalk9_npe-mz) that enables the
no payload encryption capabilities—no VPN, no SRTP, no TLS, no crypto features.
The Cisco VG350, Cisco VG310, and Cisco VG320 Analog Voice Gateways are designed to allow the management of CiscoWorks, CiscoView, Cisco Security Manager, and other enterprise and service provider management platforms.
From a platform perspective, the following MIBs will be supported in Cisco VG350, Cisco VG310, and Cisco VG320 Analog Voice Gateways:
Cisco VG350 also supports the following MIBs:
Cisco VG310 and Cisco VG320 also use the following OIDs from Cisco Active Network Abstraction (CANA) for new chassis type, CPU type, new onboard analog voice port, and AC and DC power supply.
Cisco VG310 and Cisco VG 320 are supported from CUCM Release 10.5 and CUCM Release 9.1.2SU2 version onwards. Existing Cisco IOS CUCM code changes implemented for Cisco ISR G2 platforms are leveraged to support the voice gateway auto configuration requirement for Cisco VG310 and Cisco VG320 platforms. CUCM supports both Media Gateway Control Protocol (MGCP) an Skinny Client Control Protocol (SCCP) protocols for Cisco VG310 and Cisco VG320 platforms. You must configure both CUCM and Cisco VG310 and Cisco VG320. For MGCP protocol, you can configure ccm-manager config command on Cisco VG310 and Cisco VG320 for CUCM to download platform configuration.
Cisco IOS CUCM depends on the following information to generate an XML configuration file to support the new platforms:
Qualification and Evaluation of Devices support is required for new platforms to perform SCCP and MGCP voice gateway configuration via the CUCM administration GUI web interface.
The QED changes for the Cisco VG350, Cisco VG310, and Cisco VG320 Analog platforms support the following configuration alternatives:
The CUCM Bulk Administration Tool (BAT) is a web-based application that allows administrators to perform and automate bulk transactions, such as adding, updating, or deleting, on a large number of phones, users, and ports on the Cisco VG350, Cisco VG310, Cisco VG320 Analog and other Cisco Catalyst FXS analog interface modules in the CUCM database.
BAT is supported on Cisco VG350, Cisco VG310, and Cisco VG320 Analog Voice Gateways, but it should be requested for targeted CUCM releases to update the device templates and the default Excel bat.xls spreadsheet for the new platforms associated with Cisco VG350, Cisco VG310, and Cisco VG320.
From CUCME Release 10.5 and CUCM Release 9.1.2.SU2 onwards, BAT will be supported on Cisco VG310 and Cisco VG320.
Note BAT is independent of QED support, and thus needs to be requested separately.
Existing Cisco IOS CUCME code changes implemented for Cisco ISR G2 platforms are leveraged to support the voice gateway auto configuration requirement for Cisco VG350, Cisco VG310, and Cisco VG320 Analog platforms.
Cisco IOS CUCME depends on the following information to generate an XML configuration file to support the new platforms:
The following example shows how to execute the CUCME command under the voice-gateway system, for Cisco VG310 and Cisco VG320:
The Hunt Group feature on Cisco VG310 and Cisco VG320 platforms, allows an analog phone user to enter a predefined access code to log in to a hunt group to receive calls or to log out from a hunt group and not to receive any calls from that hunt group. The default Forced Authorization Code (FAC) for hunt group login and logout is 9. User should dial ** 9 to get connected to a specific hunt group.
The Cisco VG310 and Cisco VG320 platforms support one HWIC slot. This HWIC slot is intended to provide TDM line-side extensions for connecting TDM PBX (over T1/PRI), and legacy key systems (over FXO ports).
Note This feature is not applicable to Cisco VG350.
The HWIC slot has the flexibility to support voice cards such as T1/E1 PRI, BRI, FXS, FXS-E, E/M and FXO. Both VG310 and VG320 will support existing analog VICs and digital T1/E1/BRI VWIC, and their voice port numbers are 0/2/0-x. The voice card list is as follows:
T1/E1 data link is not supported that is no data feature are supported on VWIC3-1MFT-T1/E1, VIWC3-2MFT-T1E1 and VIC2-2BRI-NT/TE.
Cisco Unified Communications Management Suite (CUCMS) is a suite of applications developed to help enterprise customers configure, deploy, and manage their unified communications networks.
CUOM and CUPM require certain MIBs to be present in Cisco VG350 IOS image. See the
“MIB Support” section for additional information regarding MIB support for CUOM and CUPM.
The SM-D-72FXS and the SM-D-48FXS-E service module supports 72 and 48 regular or OPX-lite analog FXS voice ports. They can be configured as loop-start and ground-start signaling types.
Note Cisco VG350, Cisco VG310, and Cisco VG320 Analog platforms can be configured as loop-start and ground-start signaling types. However, DID signaling type is not supported on these platforms.
REN configuration on FXS voice port defaults to 1 REN configuration can be done via existing CLI, ren <1-5> under FXS voice port. For long loop FXS, up to 2 REN can be configured. For short loop FXS, up to 5 REN can be configured.
FXS ports 4-71 on SM-D-72FXS are fixed to short loop length.
The first four (ports 0-3) FXS ports on SM-D-72FXS and all 48 FXS ports on SM-D-48FXS-E can be configured with short or long loop length. A CLI will be used to configure loop-length under these analog FXS voice ports.
The loop-length CLI is only applicable on ports 0 to 3 of SM-D-72FXS and all ports of SM-D-48FXS-E.
For more information and configuration examples, see the “loop-length” section.
Cisco VG350, Cisco VG310, and Cisco VG320 have the following motherboard HW components:
Table B-2 Cisco VG350, Cisco VG310 and Cisco VG320 Hardware Components Cisco VG350, VG310, and VG320 Hardware Components
|
|
|
|
---|---|---|---|
Cisco VG350 platform will leverage EnergyWise Support to support the SM-D-72FXS and the SM-D-48FXS-E modules.
The new modules will be integrated to support the EnergyWise Green initiative to allow configuring of CLI to turn on/off the module.
Note This feature is not supported on Cisco VG310 and Cisco VG320 platforms.
For more information and sample configurations on the EnergyWise support, see the “Configuring EnergyWise” section.
Online Insertion and removal (OIR) is supported, but can only be done one service module at a time.
OIR supports only the same service module type, that is, if you remove an SM-D-72FXS, only another SM-D-72FXS can be inserted.
Note This feature is not supported on Cisco VG310 and Cisco VG320 platforms.
BCN —Backward Congestion Notification.
COS —Class of service, 802.1p.
DA —Ethernet Destination Address.
DSA —Distributed Switch Architecture.
DSP —Digital Signal Processor.
DTMF —Dual-tone multi-frequency.
EVSM —Extended Voice Service Module.
FPGA —Field-Programmable Gate Array.
HDLC —High-level Data Link Control Protocol.
McBSP —Multi-Channel Buffer Serial Port.
MTBF —Mean Time Between Failures.
OIR —Online Insertion and Removal.
PCE —Packet Classification Engine.
PVDM3 —Next generation Packet Voice Data Module.
REA —Ethernet Ready Announcement, like bootp message.
RI —Restart indication from DSP/Device.
RTP —Real-time Transport Protocol.
SGMII —Serial Gigabit Media Independent Interface.
SRTP —Secure Real-time Transport Protocol.
TDM —Time Division Multiplexing.