|
Version 6.3 |
|
| ||||||||||||||||||||||
Media Server SettingsTo configure the Media Server component, open the Real-Time pages in the WebAdmin Settings realm, and follow the Media link.
When the remote peer SDP does not announce the special telephone-event codec, the Media Server tries to detect the DTMF signals in the received and decoded audio data. The following settings allow you to fine-tune this process.
CodecsThe Media Server supports a set of audio codecs. The following panel allows you to control how these codecs are used: There are two Priority settings for each codec - the primary and the secondary one. When a Media Server composes an initial offer, the codecs are listed sorted by their primary and secondary priority values.
When a Media Server composes an answer or a non-initial offer, i.e. when the audio codecs supported by the peer are known,
only the codecs supported by the peer are listed.
Note: the set of supported codecs depends on the platform CommuniGate Pro is running on. Compressing codecs (such as G.729) require a lot of CPU resources. You may want to offload coding-encoding operations to separate Transcoder servers: If the Usage setting is set to Transcoder, the Media Server tries to create a transcoder channel on one of the listed Transcoder servers. The peer is instructed to exchange media with the created transcoder channel, while the transcoder channel exchanges media with the CommuniGate Pro Media Server using the PCM (G.711) codec. Transcoder servers are used in a round-robin manner. If a Transcoder refuses to create a transcoder channel, and there are more than 2 servers specified, the next server is contacted. The CommuniGate Pro Server software or special CommuniGate Pro Transcoder software can be used to implement Transcoder servers. FeaturesThe Media Server supports clients connecting from remote NATed networks, using the same algorithms as those employed with the Media Proxy component. When a call media is terminated with the CommuniGate Pro Media Server, there is no need to build a Media Proxy to handle media transfer over a remote NAT. The Media Server supports DTMF "codecs": if the peer announces support for such a codec, the Media Server detects
audio packets sent using that codec and interprets the packet content as DTMF symbols. The Media Server can also
send DTMF symbols using special DTMF "codecs".
|