Sip Message Compliancy; Sip Functions - AudioCodes Mediant 800B User Manual

User's Manual
RFC
RFC 2782 A DNS RR for specifying the location of services
RFC 2617 HTTP Authentication: Basic and Digest Access
Authentication
RFC 2327 SDP
ECMA-355, QSIG tunneling
ISO/IEC 22535
draft-mahy- Signaled Telephony Events in the Session
sipping-signaled- Initiation Protocol
digits-01
draft-mahy-iptel- The Calling Party's Category tel URI Parameter
cpc-06
draft-levy-sip- Diversion Indication in SIP
diversion-08
draft-johnston- Transporting User to User Information for Call
sipping-cc-uui-04 Centers using SIP
draft-ietf-sip- SIP Extensions for Network-Asserted Caller
privacy-04.txt Identity using Remote-Party-ID header
draft-ietf-sipping- SIP Support for Real-time Fax: Call Flow
realtimefax-01 Examples
draft-ietf-sipping- Call Transfer
cc-transfer-05
draft-ietf-sip- Connection Reuse in SIP
connect-reuse-06
draft-choudhuri- SIP INFO method for DTMF digit transport and
sip-info-digit-00 collection

69.1.2 SIP Message Compliancy

The SIP device complies with RFC 3261, as shown in the following subsections.

69.1.2.1 SIP Functions

The device supports the following SIP Functions:
Function
User Agent Client (UAC)
User Agent Server (UAS)
Proxy Server
Redirect Server
Version 7.2
Description
Table 69-3: Supported SIP Functions
-
-
The device supports working with third-party Proxy Servers such as
Nortel CS1K/CS2K, Avaya, Microsoft OCS, Alcatel, 3Com, BroadSoft,
Snom, Cisco and many others
The device supports working with third-party Redirection servers
1249
69. Technical Specifications
Gateway
√
√
√
√
√
√
√
√
√
√
√
√
√
Comments
Mediant 800B Gateway & E-SBC
SBC
√
√
√
√ (forwarded
transparently)
√
√ (forwarded
transparently)
√
√ (forwarded
transparently)
√
√ (forwarded
transparently)
√
√
√