MP-1xx SIP User’s Manual 1. Overview
Version 4.4 19 March 2005
• Proxy and Registrar Authentication (handling 401 and 407 responses) using Basic or Digest
methods.
• Single gateway Registration or multiple Registration of all gateway endpoints.
• Configuration of authentication username and password per each gateway endpoint, or
single username and password per gateway.
• Supported methods: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, INFO, REFER,
NOTIFY, PRACK, UPDATE and SUBSCRIBE.
• Modifying connection parameters in a 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.
• Call Forward (using 302 response): Immediate, Busy, No reply, Busy or No reply, Do Not
Disturb.
• Supports RFC 3327 – Adding “Path” to Supported header.
• Supports RFC 3581 – Symmetric Response Routing.
• Session Timer <draft-ietf-sip-session-timer-13.txt>.
• 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>.
• Obtaining Proxy Domain Name(s) from DHCP (Dynamic Host Control Protocol) according to
RFC 3361.
• RFC 2833 relay for Dual Tone Multi Frequency (DTMF) digits, including payload type
negotiation.
• DTMF out-of-band transfer using:
INFO method <draft-choudhuri-sip-info-digit-00.txt>.
INFO method, compatible with Cisco gateways.
NOTIFY method <draft-mahy-sipping-signaled-digits-01.txt>.
• Supported coders:
G.711 A-law 64 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.711 µ-law 64 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.723.1 5.3, 6.3 kbps (30, 60, 90, 120, 150 msec)
G.726 32 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.729A 8 kbps (10, 20, 30, 40, 50, 60, 80, 100, 120 msec)
G.729B is supported if Silence Suppression is enabled.
• Can negotiate coder from a list of given coders.
• Implementation of Message Waiting Indication (MWI) IETF draft-ietf-sipping-mwi-04.txt,
including SUBSCRIBE (to the MWI server). The MP-1xx/FXS gateways can accept an MWI
Notify message that indicates waiting messages or indicates that the MWI is cleared.
For more updated information on the gateway’s supported features, refer to the latest MP-1xx SIP
Release Notes.
To Next Page
Loading...
Need help?
General
