Ask a question or submit a request for more information. Read more
Basic Startup Configuration for Nex Gen Video Conferencing Exchange (NGVX)
Once you have NGVX up and running you will need to create one or more conference definition files to allow SIP calling clients to make use of the server.
A conference definition file is a text properties file used to create a virtual conference SIP URI. The unique SIP URI can be dialed by a SIP calling client to connect to the configured conference.
Conference definition files exist in the directory:
Conference definition files can be created and removed during server runtime, which can be done by an external provisioning application.
NGVX comes out of the box with a sample conference definition file NGVX_INSTALL_DIR/conferences/1234.conference. A SIP calling client can dial the SIP uri sip:email@example.com to connect to this conference.
The domain part of the URI can be anything.
The conference definition defines conference behavior and settings:
Permitted conference participants.
Conference SIP password.
Maximum number of participants.
Secure media policy.
Conference video encoder resource usage.
The example conference definition defines several video codec specific encoder configurations. The configuratinos are defined by using the encoder= property. NGVX will search for the appropriate encoder profile which is a best fit for the advertised video capabilities of the connecting client.
NGVX uses the configuration file NGVX_INSTALL_DIR/conf/sip-ngconference.conf. This file is used to define server behavior and settings:
UDP/RTP port range
NGMS (Nex Gen Media Server) properties
Offered video and audio codec configurations
NGVX runs in the context of the Mobicents SIP Server JSLEE 1.1 (JSR 240) Application Server Sip Servlets framework available either for JBoss or Apache Tomcat. This example uses Tomcat as the servlets container.
Servlet socket listener properties are defined in the file NGVX_INSTALL_DIR/conf/server.xml. These settings are used to define the server SIP listener ports, such as UDP/TCP, SSL, and Websockets.
NGVX produces log output in NGVX_INSTALL_DIR/logs/sip-ngconference.log.
Each conference is serviced by a dedicated NGMS (Nex Gen Media Server) process which handles all media traffic. NGMS creates a conference specific log file in the directory NGMS_HOME/log/.
For eg., NGMS_HOME/log/log_1234mydomain.com_Mon-Jan-01-13:54:41.log.