AudioCodes Mediant 1000 User Manual page 27

Sip media gateways
Hide thumbs Also See for Mediant 1000:
Table of Contents

Advertisement

SIP User's Manual
The "sipgatewayname" parameter (defined in the ini file or set from the Web browser),
can be any string. Some Proxy servers require that the "sipgatewayname" (in
REGISTER messages) is set equal to the Registrar/Proxy IP address or to the
Registrar/Proxy domain name.
The REGISTER message is sent to the Registrar's IP address (if configured) or to the
Proxy's IP address. The message is sent per gateway or per gateway endpoint
according to the "AuthenticationMode" parameter. Usually the FXS gateways are
registered per gateway port, while FXO gateways send a single registration message,
where Username is used instead of phone number in From/To headers. The
registration request is resent according to the parameter 'RegistrationTimeDivider'.
For example, if 'RegistrationTimeDivider = 70' (%) and Registration Expires time =
3600, the gateway resends its registration request after 3600 x 70% = 2520 sec. The
default value of 'RegistrationTimeDivider' is 50%.
If registration per B-channel is selected, on gateway startup, the gateway sends
REGISTER requests according to the maximum number of allowed SIP dialogs
(configured by the parameter NumberOfActiveDialogs). After each received response,
the subsequent REGISTER request is sent.
Proxy and Registrar Authentication (handling 401 and 407 responses) using Basic or
Digest methods. Accepted challenges are kept for future requests to reduce the
network traffic.
Single gateway Registration or multiple Registration of all gateway endpoints.
Supported methods: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, INFO,
REFER, UPDATE, NOTIFY, PRACK, SUBSCRIBE and PUBLISH.
Modifying connection parameters for an already established call (re-INVITE).
Working with Redirect server and handling 3xx responses.
Early media (supporting 183 Session Progress).
PRACK reliable provisional responses (RFC 3262).
Call Hold and Transfer Supplementary services using REFER, Refer-To, Referred-By,
Replaces and NOTIFY.
Supports RFC 3711, Secured RTP and Key Exchange according to <draft-ietf-
mmusic-sdescriptions-12>.
Supports RFC 3489, Simple Traversal of UDP Through NATs (STUN).
Supports RFC 3605, RTCP Attribute in SDP.
Supports RFC 3326, Reason header.
Supports RFC 3911, The SIP Join Header.
Supports RFC 3903, SIP Extension for Event State Publication.
Supports RFC 3953, The Early Disposition Type for SIP.
Supports for RFC 3966, The tel URI for Telephone Numbers.
Supports RFC 4244, An Extension to SIP for Request History Information.
Supports ITU V.152 - Procedures for supporting Voice-Band Data over IP Networks.
Supports RFC 3327, Adding 'Path' to Supported header.
Supports RFC 3581, Symmetric Response Routing.
Supports RFC 4028, Session Timers in SIP.
Supports network asserted identity and privacy (RFC 3325 and RFC 3323).
Supports Tel URI (Uniform Resource Identifier) according to RFC 2806 bis.
Remote party ID <draft-ietf-sip-privacy-04.txt>.
Supports obtaining Proxy Domain Name(s) from DHCP (Dynamic Host Control
Protocol) according to RFC 3361.
Supports handling forking proxy multiple responses.
RFC 2833 Relay for DTMF Digits, including payload type negotiation.
Version 5.0
27
1. Overview
December 2006

Advertisement

Table of Contents
loading

Table of Contents