VoIP server settings:
To create new VoIP server settings, click the Create button.
Server Protocol Type:
Changing VoIP server protocol type automatically reboots the system. All voice and data connections will be terminated.
Server Objects
Protocol Type |
The signalling protocol used for VOIP. Choices are: SIP (Session Initiation Protocol) SIP-PLAR (Private Line Automatic Ringdown) MGCP (Media Gateway Control Protocol). MEGACO (Media Gateway Control Protocol H.248) Default: SIP | ||||||||||||||
Server Address Type |
IP or DNS | ||||||||||||||
Server Address |
IP Address, if Server Address Type is IP. DNS Name, if Server Address Type is DNS, and Resolver is provisioned. | ||||||||||||||
UDP Port |
Specifies the UDP port number for the MGCP gateway. Default: 2427 | ||||||||||||||
Server Type |
Identifies the VOIP server type. | ||||||||||||||
Domain Name |
Indicates the Universal Resource Identifier (URI)of the system. | ||||||||||||||
IP ToS |
A service level or type of service (TOS) can be assigned to an IP interface. The configured TOS level specifies the packet priority and queueing methods used to transport the packet through the IP network. The TOS settings are passed to other IP devices in the network. The TOS value that is set in the IP header for voice of IP traffic.
Default: 0 | ||||||||||||||
DTFM |
Indicates whether DTFM digits are to be passed as codec. Voice packets or special separate packets (rfc2833). Default is rfc2833. | ||||||||||||||
RTP TermId Syntax |
The Ephemeral term ID syntax for the switch. The RTP syntax varies from switch to switch, but the string should contain at least one %eid format, eg <string>%eid<string> . This field is only supported only for the Megaco protocol. If the protocol is megaco and the field is NULL, Ephemeral term id will be updated to default syntax of the server Id given. If the server Id is not provisioned with the default id then field will be updated to NULL |
Secondary Server
Server Address |
IP Address, if Server Address Type is IP. DNS Name, if Server Address Type is DNS, and Resolver is provisioned. |
SIP Objects
Expires Invite |
For user agent clients, this value is inserted into the Expires header. For proxy servers, if a received request contained an Expires header, then the value in the header takes precedence. |
Expires Register |
For user agent clients, this value is inserted into the Expires header. For registrar servers, if a received request contained an Expires header, then the value in the header takes precedence. |
Server Header Method |
Invite or Register. This convention is a bit map. Each bit represents a SIP method where the Expires header should be included. If a bit has value 1, then the requests corresponding to that SIP method must include an Expires header line. If a bit has value 0, then the Expires header line will not be added. Combinations of bits can be set when the Expires header line is required in multiple SIP methods. INVITE method: bit 0 REGISTER Method: bit 1 |
Session Timer |
On: Session timers are supported and SIP messages will have a 'Supported: timer' header. Off: Session timers are NOT supported and SIP messages will NOT have a 'Supported: timer' header. Default: Off |
Expiration Timeout |
The time at which an element (proxy, UAC, UAS) will consider the SIP session timed out, if no successful session refresh transaction occurs beforehand. Default: 180 |
Minimun Session Expire |
Because of the processing load of mid-dialog requests, all elements (proxy, UAC, UAS) can have configured minimum value for the session interval that they are willing to accept." Default: 180 |
Caller Request Timer |
This field specifies the caller's action. Yes: Caller (UAC) will request for timer when making outbound calls. No: Caller (UAC) will NOT request for timer when making outbound calls" Default: No |
Callee Request Timer |
When caller supports timer but did not request one this field specifies the callee's action Yes: Callee (UAS) will request for timer. No : Callee (UAS) will NOT request for timer. Default: No |
Caller Specify Refresher |
Caller specifies the refresher: UAC : Caller specifies itself (UAC) as the refresher. UAS : Caller specifies the callee (UAS) as the refresher. Omit: Caller does NOT explicitly specify the refresher. Default: Omit |
Callee Specify Refresher |
When UAC did not specify refresher tag, callee specifies the refresher: UAC: Callee specifies the caller (UAC) as the refresher. UAS: Callee specifies itself (UAS) as the refresher. Default: UAC |
January 22, 2011