VOSS Phone Server Overview¶
The VOSS phone server provides a method of hosting SIP compliant devices such as phones and softclients where it is not possible or desirable to connect these devices into other vendor platforms.
In an HCS environment, full integration management is provided where all trunk and dialplan related configuration is automatically applied. Other CUCM dialplan designs may be utilised through the VOSS4UC dialplan additions templating feature.
The VOSS Phone Server provides three functions:
A SIP registrar allows the use of SIP devices from any compliant vendor, thereby allowing for a wide choice of phones with various feature sets, including the re-use of existing devices from systems such as Cisco Unified CM and others. Since the registrar requires only account definition per line, there is no phone concept in the Phone Server itself. Phones are represented in VOSS-4-UC and are a local construct only.
A SIP Switch handling SIP call traffic. Calls between phones hosted on the VOSS Phone Server are handled locally and calls to other extensions or PSTN destinations are offloaded over a SIP Trunk
Configuration File Management (Optional). Phone configuration files may be created and hosted in the VOSS Phone Server’s tftp server. This allows unconfigured phones (i.e. new unused phones, or factory defaulted old phone stock) to obtain their configuration automatically when connected to the network.
Sample configuration files for phones from SNOM, Grandstream and Cisco are included.
VOSS-4-UC utilities include:
- System setup and Country dialplan management
- Evaluation of the number of re-usable Cisco CUM hosted phones
- Conversion of Cisco configuration to phone server configuration
The VOSS Phone Server is deployed as an OVA, typically alongside CUCM Virtual Machines in an HCS/CUCM environment. Redundancy is an option, providing data replication between servers.
