You are here: CSP Developer’s Guide: Internet Protocols > 3 IP Network Interface Series 2 Card > Differences Between IP Network Interface Series 2 and VDAC-ONE Cards
Differences Between IP Network Interface Series 2 and
VDAC-ONE Cards
The following differences exist between the IP Network Interface Series 2 and VDAC-ONE cards.
VoIP Modules
An IP Network Interface Series 2 card uses two VoIP modules, whereas a VDAC-ONE card uses four VoIP modules. Fewer modules mean fewer IP endpoints, making it easier to configure and maintain.
Important! All host messages need to be updated to address VoIP modules 1 and 2 instead of VoIP modules 1, 2, 3, and 4 on the VDAC-ONE card.
Card Type 101 (0x65) identifies a IP Network Interface Series 2 card.
Card Type 96 (0x60) identifies a VDAC-ONE card.
Card Type 104 (0x6D) identifies a IP Network Interface Series 2 card VoIP module.
Card Type 97 (0x61) identifies a VDAC-ONE card VoIP module.
Card Type 202 (0xCA) identifies a Multi-Function Media I/O card.
Card Type 207 (0xCF) identifies a VDAC I/O card.
The VoIP Resource Profile 2 on IP Network Interface Series 2 is the most similar to VDAC-ONE. The following are some of the major differences:
• The G.727 codec is not supported on the IP Network Interface Series 2 card.
• The base packet rates and maximum payload size for the voice codecs are different for the IP Network Interface Series 2 card. This difference has probably the biggest impact to the host if the default packet rates are not used. Since the base rate is different, the payload size, which is defined in multiples of the base rate, means something different for different codecs. For example, G.711 @ 20 milliseconds on a VDAC-ONE card uses a packet size of 1x (base rate of 20 milliseconds), whereas @ 20 milliseconds on a IP Network Interface Series 2 card uses a packet size of 4x (base rate of 5 milliseconds). Please refer to
Table 3-6, IP Network Interface Series 2 Voice Coder Packet Rate Information for specifics.
• The IP Network Interface Series 2 card is not interoperable with VDAC-ONE card in FAX Bypass Mode. The VDAC-ONE card uses a proprietary implementation.
• The IP Network Interface Series 2 card is not interoperable with VDAC-ONE card using the G.726 Voice codec.
• The Adaptation Rate TLV VoIP Attribute is not supported on the IP Network Interface Series 2 card. The rate at which the Jitter Buffer adapts is not configurable.
• The Fax Compatibility Mode TLV (0x01E1) is not supported.
The IP Network Interface Series 2 card has three external 100 Mbps Ethernet ports that are trunked together to form a single 300 Mbps Ethernet pipe. Automatic link fail-over is supported transparently to the host. This requires a trunking-compatible Ethernet switch in order to take advantage of the increased bandwidth.
Important! The IP Network Interface Series 2 card does not support Ethernet Link Redundancy.
Alarms have been created that notify the host when an Ethernet link failure/recovery occurs, and when a Multi-Function Media I/O card removal/insertion is detected.
Cross Connect Channel Message (0x001A)
The Cross Connect Channel message (0x001A) is supported only on the VDAC-ONE card. The IP Network Interface Series 2 card does not support this message.
Address Resolution Protocol (ARP)
The sending of ARP messages to resolve a channel’s Destination Hardware Address (MAC address) is different. The VDAC-ONE card drops all incoming the UDP packets and generates a single ARP request per second for each VDAC-ONE channel until the Destination Hardware Address (MAC address) is received.
If a destination address is provided in the resource allocation request, the IP Network Interface Series 2 card does not acknowledge the resource allocation request until after the Destination Hardware Address is resolved. Note that the VDAC-ONE card acknowledges the resource allocation request immediately, before the Destination Hardware Address is resolved.
If the Destination Hardware Address can not be resolved, a negative acknowledgement of 0x24 (Outseize Failed Due To No Answer) is returned.
Important! If a destination address change is requested on an existing connection, the request will not be acknowledged until after the Destination Hardware Address is resolved.
Important! The IP Network Interface Series 2 card caches only the VoIP module’s gateway Destination Hardware Address.