20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

SIP standards supported by MetaSphere CFS

Modified on: Wed, 25 Aug, 2021 at 4:11 PM

QuickLink ID: F005405

This following table lists the SIP standards supported by MetaSphere CFS. RFC standards can be downloaded from the
IETF website - www.ietf.org (http://www.ietf.org/).

Standard Summary MetaSphere CFS Support

MIME
RFC 2387 multipart Supported for SIP-T and SDP content
content

HTTP
Authenticatio
RFC 2617 (was n: Basic and
Supported
RFC 2069) Digest Access
Authenticatio
n

DNS RR for
specifying the
RFC 2782 location of Supported
services (DNS
SRV)

RTP payload Supported (note that CFS does not support encoding flash events, but this is not
RFC 2833 for DTMF mandatory in the RFC; instead other mechanisms are used for signaling flash
digits hooks, e.g. H.248 events or SIP INFO)

Session
RFC 3261 Initiation Supported
Protocol (SIP)

Reliable
RFC 3262 (was provisional
draft-ietf-sip- respones Supported
100rel) (PRACK
method)

Locating SIP
RFC 3263 servers (DNS Supported
lookups)

SDP
RFC 3264 offer/answer Supported
model

Feedback

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 1/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

SIP event
notifications
RFC 3265 (SUBSCRIBE/ Supported
NOTIFY
methods)

Support for
IPv6 in
Session
RFC 3266 Supported
Description
Protocol
(SDP)

SIP UPDATE
RFC 3311 Supported
method

Integration of
resource
Partially supported from V9.0. See MGCF preconditions support
RFC 3312 management
(https://communities.metaswitch.com/docs/DOC-102553).
and SIP (SIP
preconditions)

A Privacy
RFC 3323 (was Mechanism
draft-ietf-sip- for SIP (SIP Supported
privacy-general) Privacy
header)

SIP asserted Partially supported (P-Asserted-Identity header supported, P-Preferred-Identity

RFC 3325
identities header not supported)

SIP reason
header (for
encoding
RFC 3326 Supported
Q.850 ISUP
release
causes)

RFC 3362 T.38 Supported

RFC 3372 SIP-T Supported

RTP payload
RFC 3389 for comfort Supported
noise

RFC 3398 (was

draft-ietf-sip-
SIP to ISUP Partially supported (message, header and release code mostly supported, SIP
isup and draft-
mappings INFO for mid-call signaling not supported)
ietf-sipping-
isup)

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 2/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

Private
Header (P-
Header) Supported:
Extensions to • P-Charging-Function-Addresses
the Session • P-Charging-Vector
Initiation • P-Visited-Network-ID
RFC 3455
Protocol (SIP) • P-Access-Network-Info
for the 3rd- Not supported:
Generation • P-Associated-URI
Partnership • P-Called-Party-ID
Project
(3GPP)

SIP REFER
RFC 3515 Supported
method

RFC 3550 (was Real Time Supported (note that 3550 obsoletes 1889, and is back compatible in the
RFC 1889) Protocol (RTP) RTP/RTCP formats, so by supporting 3550 CFS also supports 1889)

RTP Profile for

Audio and
Video
RFC 3551 Supported
conferences
with Minimal
Control

MIME Type
Registration
RFC 3555 of RTP Supported
Payload
Formats

SIP rport
parameter
RFC 3581 (symmetric Supported
response
routing)

SIP basic call

RFC 3665 Supported
flow

Best current
practices for
RFC 3725 third party Supported
call control in
SIP

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 3/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

The E.164 to
Uniform
Resource
Identifiers
(URI)
RFC 3761 Dynamic Supported
Delegation
Discovery
System
(DDDS)
Application

SIP
RFC 3764 Supported
enumservice

Using E.164
RFC 3824 numbers with Supported
SIP

SIP
RFC 3840 CFS only supports the automata parameter in the Contact header.
capabilities

SIP message
waiting
RFC 3842 indicator Supported (message-summary event package)
event
package

A Presence
Event
Package for
RFC 3856 Supported
the Session
Initiation
Protocol (SIP)

SIP replaces
RFC 3891 Supported
header

SIP "Referred-
RFC 3892 By" Supported
mechanism

Early media
and ring tone
RFC 3960 Supported
generation in
SIP

RFC 3966 (was Partially supported from V9.0 - see Tel URI support
Tel URIs
RFC 2806) (https://communities.metaswitch.com/docs/DOC-102785).

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 4/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

Uniform
Resource
RFC 3986 (was
Identifiers Supported
RFC 2396)
(URI) Generic
Syntax

Partially supported.CFS supports keepalive of SIP sessions using polling

RFC 4028 (was
SIP session reINVITEs but does not support the explicit mechanisms of this RFC. Specifically
draft-ietf-sip-
timers CFS does not support negotiation of timer intervals described by this RFC [PRD
session-timer)
1322] and may change SDP on polling reINVITEs.

RTP Payload
Format for a
64 kbit/s
RFC 4040 Supported
Transparent
Call
specifications

SIP dialog
RFC 4235 state event Supported
package

SIP History-
RFC 4244 Partially supported from V9.2 (made obsolete by RFC 7044 - see below)
Info header

SIP Resource
RFC 4412 Supported
Priority

Session
RFC 4566 (was Descriptor
Supported
RFC 2327) Protocol
(SDP)

SIP
parameters
for telephone
RFC 4694 (was networks e.g. Supported parameters:
draft-ietf-iptel- carrier codes, cic - carrier ID
tel-np / draft- number rn - routing number
yu-tel-url) portability, npdi - number portability dip indicator
originating
LRN (cic, rn,
npdi)

RTP payload
RFC 4733 (was
for DTMF Supported
RFC 2833)
digits

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 5/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

RTP Payload
Format and
File Storage
Format for the
Adaptive
Multi-Rate
RFC 4867 Supported
(AMR) and
Adaptive
Multi-Rate
Wideband
(AMRWB)
Audio Codecs

Trunk Groups
RFC 4904 Supported
in tel/sip URIs

Connected
Identity in the
RFC 4916 Session Supported except Identity header
Initiation
Protocol (SIP)

P-Early-Media Partially supported from V9.0 - see MGCF preconditions support

RFC 5009
Header (https://communities.metaswitch.com/docs/DOC-102553).

SIP Service See MetaSphere CFS SIP Interop Guide section 3.18 for detailed compliance
RFC 5359
Examples statement.

The P-Served-
User Private-
Header (P-
Header) for
RFC 5502 the 3GPP IP Supported
Multimedia
(IM) Core
Network (CN)
Subsystem

Private SIP Supported headers:

Proxy-to- • P-DCS-OSPS
Proxy • P-DCS-Billing-Info
Extensions for Unsupported headers:
RFC 5503 (was Supporting • P-DCS-LAES
RFC 3603) the • P-DSC-Redirect
PacketCable • P-DCS-Trace-Party-ID
Distributed • Target-Dialog
See MetaSphere CFS SIP Interop Guide sections 8.8.4 and 9.3.9 for details of
Call Signaling
support for INVITEs to "call-trace".
Architecture

SIP Call
RFC 5589 Control- Supported
Transfer

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 6/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

RFC 5806 (draft-

SIP diversion
levy-sip- Supported
header
diversion)

RFC 6035 (was SIP event

draft-ietf- package for
Supported (only PUBLISH method, not SUBSCRIBE/NOTIFY)
sipping-rtcp- voice quality
summary) reporting

RFC 6086 (was SIP INFO Used for analog line flash hook and call waiting, and out of band DTMF
RFC 2976) method reporting

Supported from V9.2 - see SIP History-Info and 181s

SIP History-
RFC 7044 (https://community.metaswitch.com/a/solutions/articles/76000005422?
Info header
portalId=76000000063)

Loop
Detection
RFC 7332 (was Mechanisms
draft-ietf- for Session
CFS supports decrementing the maxforwards header and rejecting incoming
strawb2bua- Initiation
SIP calls with a maxforwards value of 0
loopdetection- Protocol (SIP)
04) Back-to-Back
User Agents
(B2BUAs)

A SIP
Supported from V9.3.20 SU124, V9.5.40 SU50 and V9.6.30 (see
Response for
RFC 8197 https://community.metaswitch.com/support/solutions/articles/760000421
Unwanted
98 (https://community.metaswitch.com/support/solutions/articles/76000042198))
Calls

A Session
Initiation
Supported from V9.3.20 SU124, V9.5.40 SU50 and V9.6.30 (see
Protocol (SIP)
RFC 8688 https://community.metaswitch.com/support/solutions/articles/760000421
Response
98 (https://community.metaswitch.com/support/solutions/articles/76000042198))
Code for
Rejected Calls

draft-york-
SIP charge
sipping-p- Supported
information
charge-info

SIP Remote-
draft-ietf-sip- Party-ID and Partially supported (CFS supports sending and receiving the Remote-Party-ID,
privacy RPID-Privacy but not the RPID-Privacy header)
headers

DAI
draft-yu-tel-dai Parameter for Supported
the "tel" URI

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 7/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

Uniform
Resource
Identifier
(URI)
Parameters
draft-patel-
for indicating
dispatchcpc-oli- Supported
the Calling
parameter
Party's
Category and
Originating
Line
Information

draft- The isup-oli

haluskadispatch- SIP URI Supported
isup-oli parameter

Interworking
between
Session
Initiation
Protocol (SIP)
and Bearer CFS supports Q.1912.5 Profile C, for SIP-I to ISUP interworking. It does not
ITU Q.1912.5
Independent support BICC.
Call Control
(BICC)
protocol or
ISDN User
part

IP multimedia
call control
protocol
based on
Session
Initiation
Protocol (SIP)
and Session
Description
Protocol
CFS supports a number of BroadSoft defined / de facto standards including:
(SDP);
• call-info event package
Stage3
• line-seize event package
3GPP TS 24.229 BroadSoft –
• application/broadsoft bodies in SIP INFO for flash hook indications and call
• BroadWorks
waiting tones
SIP Access
• as-feature-event package for call feature / ACD presence synchronization
Interface
Interworking
Guide,
Release 18.0
• BroadWorks
SIP Access
Side
Extensions
Interface,
Release 18.0

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 8/9
20/03/2024, 15:01 SIP standards supported by MetaSphere CFS

That part of ETSI

TS 183 036 ISDN/SIP CFS supports receiving a SIP Re-INVITE that includes an XML MCID request to
s5.2.6.2 that interworking; invoke Call Trace.
relates to SIP

This used to be article 12801.

©2023 Microsoft. All rights reserved - CONFIDENTIAL

https://community.metaswitch.com/support/solutions/articles/76000005405-sip-standards-supported-by-metasphere-cfs 9/9