All contents of this document are furnished for informational use only and are subject to change without notice
and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries (“Dialogic”).
Reasonable effort is made to ensure the accuracy of the information contained in the document. However,
Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors,
inaccuracies or omissions that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE,
EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY
THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC
ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING
TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL
PROPERTY RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems,
or in nuclear facility applications.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use
only in specific countries, and thus may not function properly in other countries. You are responsible for ensuring
that your use of such products occurs only in the countries where such use is suitable. For information on specific
products, contact Dialogic Corporation at the address indicated below or on the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this
document, in marketing collateral produced by or on web pages maintained by Dialogic may inf ringe one or more
patents or other intellectual property rights owned by third parties. Dialogic does not provide any intellectual
property licenses with the sale of Dialogic products other than a license to use such product in accordance with
intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a
signed agreement with Dialogic. More detailed information about such intellectual property is available from
Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Dialogic
encourages all users of its products to procure all necessary intellectual property licenses required to
implement any concepts or applications and does not condone or encourage any intellectual property
infringement and disclaims any responsibility related thereto. These intellectual property licenses
may differ from country to country and it is the responsibility of those who develop the concepts or
applications to be aware of and comply with different national license requirements.
Any use case(s) shown and/or described herein represent one or more examples of the various ways, scenarios
or environments in which Dialogic® products can be used. Such use case(s) are non-limiting and do not
represent recommendations of Dialogic as to whether or how to use Dialogic products.
Dialogic, Dialogic Pro, Brooktrout, Diva, Cantata, SnowShore, Eicon, Eicon Networks, NMS Communications, NMS
(stylized), Eiconcard, SIPcontrol, Diva ISDN, TruFax, Exnet, EXS, SwitchKit, N20, Making Innovation Thrive,
Connecting to Growth, Video is the New Voice, Fusion, Vision, PacketMedia, NaturalAccess, NaturalCallControl,
NaturalConference, NaturalFax and Shiva, among others as well as related logos, are either registered
trademarks or trademarks of Dialogic Corporation or its subsidiaries. Dialogic's trade marks may be used publicly
only with permission from Dialogic. Such permission may only be granted by Dialogic’s legal department at 9800
Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized use of Dialogic's trademarks will
be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of
Dialogic’s trademarks requires proper acknowledgement.
The names of actual companies and product mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible
for your decision to use open source in connection with Dialogic products (including without limitation those
referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including
without limitation effects on your products, your business, or your intellectual property rights.
Revision history
Revision Release date Notes
64-0403-02 Rev B December 2009 BK, Dialogic® Vision™ CX Video Gateway 4.2 and Dialogic®
64-0403-02 Rev A August 2009 BK, Dialogic® Vision™ CX Video Gateway 4.2 and Dialogic®
64-0403-01 Rev A June 2009 DEH/BK, Dialogic® Vision™ CX Video Gateway 4.1 and
Last modified: November 12, 2009
Refer to www.dialogic.com for product updates and for information about support policies, warranty
information, and service offerings.
Vision™ VX Integrated Media Platform 4.2.
Vision™ VX Integrated Media Platform 4.2.
Dialogic® Vision™ VX Integrated Media Platform 4.1.
The Dialogic® Vision™ CX Video Gateway Administration Manual describes how to
configure and manage the Dialogic
CX Video Gateway in this manual).
For information about installing the Dialogic
relevant hardware installation manual (listed in Related documentation on page
The term Vision™ Server is used in this manual to refer to both the CX Video
Gateway and the VX Integrated Media Platform collectively.
Note: Products to which this document pertains are part of the NMS
Communications Platforms business that was sold by NMS Communications
Corporation (“NMS”) to Dialogic Corporation (“Dialogic”) on December 8, 2008.
Accordingly, certain terminology relating to the products has been changed. Below is
a table indicating terminology that was formerly associated with the products, as well
as the new terminology by which the products are now known.
Former terminology Current terminology
Vision CX Gateway Dialogic® Vision™ CX Video Gateway
Vision VoiceXML Server Dialogic® Vision™ VX Integrated Media Platform
Introduction
®
Vision™ CX Video Gateway (also referred to as
®
Vision™ Server hardware, see the
24).
Dialogic 9
2
2
Overview of the CX Video
Gateway
CX Video Gateway overview
The CX Video Gateway is a CCXML-based call server that provides call control and
transaction capabilities for calls made between the PSTN and IP networks. The
gateway provides the following functionality:
•Supports the SIP telecommunications protocol and the ISDN or ISUP
protocols.
•Processes audio information, or both audio and video information, depending
on the model.
• Terminates T1/E1 TDM audio trunks.
• Defines routes using CCXML applications.
• Optionally provides in-band DTMF support.
• Optionally connects incoming faxes to a third-party T.38 server.
• Optionally provides fast call setup techniques to speed up 3G-324M call setup
time.
• Produces detailed event logs with multiple information levels.
• Provides a web-based console, called the Vision™ Console, to configure and
manage the gateway.
•Provides an SNMP interface for monitoring application usage and server
health.
The gateway is installed as a daemon on Linux machines and is composed of the
following components:
• Signaling protocols and models
• Media capabilities
• CCXML scripting engine
• SNMP agent and sub-agents
• Fast call setup
These components are based on specific hardware support, including media boards
and signaling boards.
Dialogic 11
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Signaling protocols and models
The gateway can implement the following signaling protocols:
• ISDN, which is available with the ISDN audio and ISDN video models.
• ISUP, which is available with the ISUP audio and ISUP video models. These
models are available with one or more signaling servers.
All CX Video Gateway models use SIP/RTP signaling to in terface with the IP network.
For more information, see ISDN models on page
15 and ISUP models on page 16.
12 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
Media capabilities
The gateway media capabilities support the following codecs:
Codec
type
Audio
Video
Codec Description
AMR 3GPP TS 26.090, 26.101, and 26.073, version 5.3.0, 2004.
G.711 A-law
and mu-law
G.723.1
G.726
G.729 A
H.263 Standard: IETF RFC 2190, ITU-T Recommendation H.263, and 3GPP
H.263+ Standard: IETF RFC 2429, ITU-T Recommendation H.263, and 3GPP
specifications TS.26.111, TS.26.911, TS.26.140.
Encoding format (Profile/Level): Baseline level 10, 20, 30.
Picture format: QCIF Quarter Common Interchange Format (176 x 144)
and CIF Common Interchange Format (352 x 288).
Frame rate: 6 to 30 fps. Integer value only. 3G side is up to 15 fps. IP
side is determined via SDP negotiation.
Encoding bit rate: Up to 384 kbps. 3G side is 42 kbps. IP side is
determined via SDP negotiation.
specifications TS.26.111, TS.26.911, TS.26.140.
Picture format, frame rate, and encoding bit rate are the same as H.263.
MPEG-4 Standard: IETF RFC 3016, ISO/IEC 14496-2:2004 and 3GPP
T.38
Recommendation H.264, and 3GPP specifications TS.26.111, TS.26.911,
TS.26.140.
Encoding format (Profile/Level): Baseline profile, level 1.0, 1b, 1.1
and 1.2. Packetization mode single-NAL and non-interleave.
Picture format, frame rate, and encoding bit rate are the same as H.263,
except that CIF at 30 fps is not supported.
specifications TS.26.111, TS.26.911, TS.26.140.
Encoding format (Profile/Level): Simple profile level 0, 1, 2, and 3.
Picture format, frame rate, and encoding bit rate are the same as H.263.
CCXML scripting engine
The CCXML scripting engine enables the CX Video Gateway to execute applications
written in the W3C Working Draft of CCXML dated 29th June 2005
(http://www.w3.org/TR/2005/WD-ccxml-20050629). You can use CCXML to write
applications that provide call control for the durat ion of a phone call, including call
setup, monitoring, and tear-down. You can also use CCXML applications to provide
call routing and conferencing functionality.
For more information, see Managing CCXML applications on page
gateway routing on page
126, and the Dialogic® Vision™ CCXML Developer's
87, Fine tuning
Manual.
Dialogic 13
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
SNMP agent and subagents
The CX Video Gateway provides an SNMP interface that lets you monitor gateway
performance, view statistics, monitor a RAID server, and receive alarms. The
gateway uses Net-SNMP as a master agent and the DS1, Call Server, and RAID
subagents. The master agent supports SNMPv1, SNMPv2c, and SNMPv3.
For more information, see the Dialogic® Vision™ SNMP Reference Manual.
Fast call setup
The CX Video Gateway supports the following techniques for speeding up 3G-324M
call setup time:
•Packed H.245 messages, which groups independent H.245 messages together
into a single NSRP command frame. This reduces the number of message
round-trips, and thus reduces call setup time.
•Windowed Simple Retransmission protocol (WNSRP), an H.245 transport
improvement technique that is standardized in ITU-T Recommendation H.324
and accepted into the 3G-324M standard by 3GPP.
•Media oriented negotiation acceleration (MONA), which unites the
technologies for H.324 call setup acceleration under a common framework.
MONA was approved by the ITU-T in August 2006, and is recommended in
3GPP Release 7 in TR 26.911.
Note: You must obtain the appropriate license to use one of these techniques. For
information, see the readme file for this release.
The CX Video Gateway does not support:
• The signaling preconfigured channel (SPC) MONA technique.
• Preconfigured channel media frames encapsulated in MONA signaling
preference messages.
14 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
ISDN models
The CX Video Gateway is available with an ISDN audio model and an ISDN video
model.
ISDN audio model
In the ISDN audio model, the gateway:
• Provides ISDN signaling.
• Provides SIP signaling.
• Supports the Call Control Extensible M a rkup Language (CCXML) for call
control.
The following illustration shows the ISDN audio model:
ISDN access
network
ISDNSIP
CX Video
Gateway
IP
RTP G.711E1
network
ISDN video model
In the ISDN video model, the gateway:
• Provides ISDN signaling with 3G-324M.
• Provides SIP signaling.
• Provides the option to transcode between AMR and G.711.
• Supports the Call Control Extensible M a rkup Language (CCXML) for call
control.
The ISDN video model requires a mobile video device that supports 3G-324M.
The following illustration shows the ISDN v ideo model:
ISDN access
network
ISDNSIP
E1
(3G-324M)
CX Video
Gateway
RTP AMR (audio)
RTP H.263 (video)
IP
network
Dialogic 15
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
ISUP models
The CX Video Gateway is available with an ISUP audio model and an ISUP video
model. Each of these models can be configured for scalability and redundant
capability.
This topic describes the:
• Basic ISUP audio model
• Basic ISUP video model
• ISUP scalable deployment model
• ISUP redundant deployment model
Basic ISUP audio model
In the basic ISUP audio model, the gateway:
• Provides ISUP signaling.
• Provides SIP signaling.
• Supports the Call Control Extensible M a rkup Language (CCXML) for call
control.
The following illustration shows the basic ISUP audio model:
SS7 access
network
ISUP
CX Video
Gateway
SIP
RTP G.711E1
IP
network
16 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
Basic ISUP video model
In the basic ISUP video model, the gateway:
• Provides ISUP signaling with 3G-324M.
• Provides SIP signaling.
• Provides the option to transcode between AMR and G.711.
• Supports the Call Control Extensible M a rkup Language (CCXML) for call
control.
The basic ISUP video model requires a mobile video device that supports 3G-324M.
The following illustration shows the basic ISUP video model:
SS7 access
network
ISUP
E1
(3G-324M)
CX Video
Gateway
SIP
RTP AMR (audio)
RTP H.263 (video)
IP
network
Dialogic 17
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
ISUP scalable deployment model
For scalability, multiple CX Video Gateways can be deployed where the ISUP
termination on one gateway provides the signaling between the SS7 access network
and each of the other gateways in the system.
In this model, the gateways are configured to share the single signaling point code
terminated by the gateway with ISUP interface. This configuration allows for high
density deployments for a single signaling point code.
The following illustration shows the ISUP scalable deployment model.
SS7 access
network
ISUP
E1
E1
E1
CX Video
Gateway
CX Video
Gateway
CX Video
Gateway
.
.
.
SIP
RTP
G.711
SIP
RTP
G.711
SIP
RTP
G.711
IP
network
18 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
ISUP redundant deployment model
For a redundant and fault-tolerant system, two CX Video Gateways can be deployed
to provide higher availability. The gateways share a single signaling point code and
provide node-level redundancy.
The following illustration shows an ISUP model with two CX Video Gateways to
support redundancy. The redundant pair of gateways with ISUP terminations
seamlessly provides signaling services for multiple gateways as in the scalable
deployment model.
SS7 access
network
ISUP
E1
ISUP
E1
E1
CX Video
Gateway
CX Video
Gateway
CX Video
Gateway
.
.
.
SIP
RTP
G.711
SIP
RTP
G.711
SIP
RTP
G.711
IP
network
Dialogic 19
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Models with Video Transcoders
The CX Video Gateway includes options for video transcoders. A video transcoder can
be deployed in several configurations based on application need as described in the
following topics.
• Video Transcoder interconnect
• Video model with a single Video Transcoder
• Video model with multiple Video Transcoders
• Video model with gateways sharing Video Transcoders
• Video model with co-located Video Transcoder
For more information on video transcoders, see Managing video transcoder resources
PSTN
PSTN
PSTN
network
Network
Network
94.
ISUP
E1
CX Video
CX Video
CX Video
Gateway
Gateway
Gateway
SIP
RTP
RTPRTP
Video
Video
Video
Transcoder
Transcoder
Transcoder
IP
IP
IP
network
Network
Network
on page
Video Transcoder interconnect
The CX Video Gateway controls the video transcoder resources and inserts the
transcoder in the video media path between the gateway and the target IP endpoint.
The communication interface to the IP endpoint is SIP. The interworking of the
gateway has proprietary control of the video transcoder. Video traffic is routed to
and from the video transcoder via RTP. Audio traffic flows separately from the
gateway to the IP endpoint via RTP.
Video model with a single Video Transcoder
In the simplest case, a video transcoder is mated with the CX Video Gateway. The
gateway is configured with this single video transcoder system which is used to
complete gateway routes for the negotiated video codecs.
PSTN
network
CX Video
Gateway
Video
Transcoder
IP
network
20 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
Video model with multiple Video Transcoders
For scalability in transcoding requirements, multiple video tr anscoder systems may
be required to satisfy the needs of the application or the connectivity requirements of
the target IP endpoints. For this reason, the CX Video Gateway may be configured to
use multiple video transcoders.
Video
Video
Video
Transcoder
Transcoder
Transcoder
PSTN
PSTN
PSTN
Network
Network
network
CX Video
CX Video
CX Video
Gateway
Gateway
Gateway
Video
Video
Video
Transcoder
Transcoder
Transcoder
Video
Video
Video
Transcoder
Transcoder
Transcoder
IP
IP
IP
Network
Network
network
Video model with gateways sharing Video Transcoders
For flexibility in deployments and scalability of a gatewa y solution, multiple CX Video
Gateways may be configured to share multiple video transcoder systems. In this
configuration, the solution provider can view the composite of these servers as a
single node or scalable gateway.
Video
Video
Video
Transcoder
Transcoder
Transcoder
Video
Video
Video
Transcoder
Transcoder
Transcoder
Video
Video
Video
Transcoder
Transcoder
Transcoder
IP
IP
IP
network
Network
Network
PSTN
PSTN
PSTN
Network
Network
network
CX Video
CX Video
CX Video
Gateway
Gateway
Gateway
CX Video
CX Video
CX Video
Gateway
Gateway
Gateway
Video model with co-located Video Transcoder
For small deployments or development systems, the video transcoder may be a
subsystem deployed on the same physical server as the CX Video Gateway. Logically
these are separate servers and are configured similarly to the Video model with a
single Video Transcoder.
PSTN
PSTN
PSTN
Network
Network
network
Dialogic 21
CX Video
CX Video
Gateway
Gateway
Video
Video
Video
Transcoder
Transcoder
Transcoder
IP
IP
IP
network
Network
Network
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Standards
The CX Video Gateway complies with and supports the following standards,
depending on the model:
Standard Version Model
BICC ITU-T Q.1901, 2000 All ISUP
ITU-T Q.1902-6, 2001
ANSI T1.673-2002[R2007]
CCXML Version 1.0, based upon the W3C Working Draft of CCXML dated 29 All models
June 2005
See http://www.w3.org/TR/2005/WD-ccxml-20050629.
ISUP China ISUP All ISUP
EN 300-356-1, ETSI ISUP V.3, 1998
ETS 300-121, ETSI ISUP V.1, 1992
ETS 300-356-1, ETSI ISUP V.2, 1995
ETS 300-356-33, ETSI
ITU-T Q.730-737, 1992
ITU-T Q.761-764, 1997
ITU-T Q.767, 1992
ITU-T Q.784, 1996-1997
ANSI T1.113, 236, 1995
NTT Q.761-764 (future)
RFC 2833 RFC 2833, May 2000 All models
SIGTRAN SCTP (RFC 2960), 2000 All ISUP
M3UA (RFC 4666), 2006
SIP SIP: Session Initiation Proto col, Rosenberg et al., IETF RFC 3261, June All mo de ls
2002
22 Dialogic
models
Dialogic® Vision™ CX Video Gateway Administration Manual Overview of the CX Video Gateway
Document conventions
By default, the CX Video Gateway software is installed in the /opt/nms/vx directory.
This manual uses the string vx to refer to the default installation directory.
Dialogic 23
Overview of the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Related documentation
The following manuals provide information related to installing and configuring the
CX Video Gateway:
Document Description
Installing the Dialogic® Vision™ Server Describes how to install and cable the V ision™ TIGI2U
TIGI2U hardware.
Installing the Dialogic® Vision™ Server Describes how to install and cable the Vision™ TIGW1U
TIGW1U hardware.
Dialogic® Vision™ Call Server Describes how to configure the Call Server.
Administration Manual
Supplements the Call Server configuration information in
this manual.
Dialogic® Vision™ Signaling Server
Administration Manual
Dialogic® Vision™ CCXML Developer's
Manual
Dialogic® Vision™ SNMP Reference
Manual
Dialogic® CG 6565 Media Board
Installation and Developer's Manual
Describes how to configure the Vision™ Signaling Server.
Supplements the Vision™ Signaling Server configura tion
information in this manual.
Describes how to use the CCXML interface to configure and
develop CCXML applications for the CX Video Gateway.
Describes the management information bases (MIB s) and
agents that support SNMP on the CX Video Gateway.
Describes how to configure the media boards.
Supplements the media board configuration information in
this manual.
24 Dialogic
3
3
Configuring the CX Video
Gateway
Overview of configuring the CX Video Gateway
All software is pre-installed and pre-configured on the CX Video Gateway. However,
software parameters are set for the manufacturing environment. You must reconfigure some of these parameters so that the system operates properly at your
site.
Use the Vision™ Console to set up the gateway software. Using this tool, you enter
field values and the tool automatically modifies th e configuration files for your model.
This section describes how to use the Vision™ Console to set up the gateway
software. It contains the following topics:
• Gathering information
• Logging into the gateway for the first time
• Accessing the Vision™ Console
• Creating or revising a configuration
• Backing up a configuration
• Restoring a configuration
• Accessing the gateway using a secure shell
Note: After you create the CX Video Gateway configuration, you can fine tune it if
necessary. For information, see Overview of fine tuning the gateway configuration on
page 111.
Dialogic 25
Configuring the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Gathering information
Before you configure the CX Video Gateway, have the following information
available:
• Network configuration information (all models)
• ISDN configuration information (ISDN models)
• ISUP configuration information (ISUP models)
• Signaling server configuration information (ISUP models)
• Video transcoder configuration information (if applicable)
Network configuration information (all models)
The following information is required for configur ing all CX Video Gateway models:
Required information Value
Domain name for the CX Video Gateway node
Primary and secondary DNS server IP address
CX Video Gateway Ethernet 1 IP address, subnet mask, and default
gateway
CX Video Gateway Ethernet 2 IP address, subnet mask, and default
gateway
Media board 0 IP address, subnet mask, and default gateway
Media board 1 IP address, subnet mask, and default gateway, if
present
(Optional) IP address to use for dialog requests, such as requests
from a VoiceXML media server
Port of the HTTP server for the application server where the
VoiceXML index is hosted
ISDN configuration information (ISDN models)
If you are using the ISDN audio or ISDN video model, gather the following ISDN
configuration information:
Required information Value
ISDN protocol variant
ISDN equipment type
26 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Configuring the CX Video Gateway
ISUP configuration information (ISUP models)
If you are using the basic ISUP audio or basic ISUP video model, gather the following
ISUP configuration information:
• MTP 1 information
• MTP 2 and MTP 3 information
• ISUP Information
MTP 1 information
Required information Value
Number of E1s/T1s required
How E1s are being presented
Line coding
T1 ________
E1 ________
BNC Male (75 ohms)
RJ48 (120 ohms)
RJ45 (120 ohms)
Signaling only trunks:
Trunk 9: ________
Trunk 10 ________
Required information Value
PC format
3.8.3 (14 bit)
8.8.8 (24 bit)
Other ________
Local point code
Number of links
SS7 variant
Trunk number for link 1
Timeslot for link 1
Adjacent point code for link 1
Signaling link code (SLC) for link 1
Subservice field link for link 1
Trunk number for link 2
Timeslot for link 2
Adjacent point code for link 2
Signaling link code (SLC) for link 2
Subservice field link for link 2
28 Dialogic
Dialogic® Vision™ CX Video Gateway Administration Manual Configuring the CX Video Gateway
ISUP information
Required information Value
Origination point code
Subservice field
Destination point codes for circuits on each T1/E1 trunk
Number of circuits used per trunk
Circuit identification code (CIC) for each T1/E1 trunk
Trunk direction for each T1/E1 trunk
Subservice field
ISUP variant
Is inbound call required?
Is outbound call required?
Is transfer required? If yes, what type?
Range of numbers to use for the CX Video Gateway
Signaling Server configuration information (ISUP models)
The following information is required for ISUP models that have a Signaling Server:
Required information Value
Signaling server IP address
Signaling server circuit start value
Dialogic 29
Configuring the CX Video Gateway Dialogic® Vision™ CX Video Gateway Administration Manual
Required information Value
Signaling server variant (switch type)
Name of the signaling server associated with each trunk.
Values for CG media board 1 and CG media board 2 are used for
The following information is required for models that us e video transcoding:
Required information Value
IP address of video transcoder system
IP address of second video transcoder system, if used
IP address of third video transcoder system, if used
IP address of n video transcoder system, if used
30 Dialogic
Loading...
+ 107 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.