t
In this section:
Supported Standards
The following standards are supported to the extent that pertains to Ribbon product features to which they apply. The entire standard is not necessarily supported, only the section(s) of the standard that impact a given feature.
3GPP
Supported 3GPP Standards
| Standard | Requirement | Noted | Description |
|---|---|---|---|
| 3GPP TS 22.228 | IP Multimedia Subsystem, Stage 1 | ||
| 3GPP TS 23.002 | Group Services and Systems Aspects; Network architecture | ||
| 3GPP TS 23.003 | Numbering, Addressing and Identifications | ||
| 3GPP TS 23.203 | Policy and charging control architecture | Partially Comply (PC) | The Ribbon SBCs support the Rx interface. |
| 3GPP TS 23.207 | End-to-end Quality of Service (QoS) concept and architecture | Partially Comply (PC) | The SBC supports Rx interface towards PCRF. |
| 3GPP TS 23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | ||
| 3GPP TS 23.228 | IP Multimedia Subsystem (IMS); Stage 2 | Partially Comply (PC) | This standard defines IMS architecture. The Ribbon SBC complies to the applicable P-CSCF/IBCF procedures as noted in other standards. Note that the Ribbon SBC does not support SigComp. |
| 3GPP TS 23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | Partially Comply (PC) | This standard defines the architecture for access transfer and Inter-UE transfer procedures. The Ribbon SBC supports applicable for procedures for ATCF/ATGW, PS-PS access transfer, Inter-UE Transfer procedures etc. Note that Ribbon SBC does NOT support CS media for IMS sessions. |
| 3GPP TS 23.292 | IP Multimedia System (IMS) centralized services; Stage 2 | Partially Comply (PC) | |
| 3GPP TS 23.380 | Support S-CSCF Restoration Procedures | ||
| 3GPP TS 24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | ||
| 3GPP TS 24.173 | IMS Multimedia telephony service and supplementary services; Stage 3 | ||
| 3GPP TS 24.229 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | ||
| 3GPP TS 24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | ||
| 3GPP TS 24.341 | Support of SMS over IP networks; Stage 3 | ||
| 3GPP TS 24.604 | Communication Diversion (CDIV) using IP Multimedia (IM)Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.605 | Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.606 | Message Waiting Indication (MWI )using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.607 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.608 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | Partially Comply (PC) | The Ribbon SBC portfolio partially supports transparency of Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) information as defined in [3GPP TS 24.608]. The Ribbon SBCs support P-A-I, privacy headers in responses to INVITE/non-INVITE transactions. However, they do not support "from-change" tag and associated procedures. |
| 3GPP TS 24.610 | Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.611 | Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.615 | Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification | ||
| 3GPP TS 24.623 | Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Simulation Services | ||
| 3GPP TS 26.071 | Mandatory speech CODEC speech processing functions; AMR speech Codec; General description | ||
| 3GPP TS 26.090 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions | ||
| 3GPP TS 26.093 | Mandatory speech codec speech processing functions Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation | ||
| 3GPP TS 26.103 | Speech codec list for GSM and UMTS | ||
| 3GPP TS 26.114 | IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction | Partially Comply (PC) | |
| 3GPP TS 26.235 | Packet Switched Conversational Multimedia Application; Default Codecs | Partially Comply (PC) | |
| 3GPP TS 26.236 | Packet Switched Conversational Multimedia Applications; Transport Protocols | Partially Comply (PC) | |
| 3GPP TS 29.165 | Inter-IMS Network to Network Interface (NNI) | Partially Comply (PC) | |
| 3GPP TS 29.162 | Interworking between the IM CN subsystem and IP networks | ||
| 3GPP TS 29.214 | Policy and Charging Control over Rx Reference Point | ||
| 3GPP TS 29.235 | Interworking between SIP-I based circuit-switched core network and other networks | ||
| 3GPP TS 32.225 | Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS) | Partially Comply (PC) | This specification defines the high-level charging architecture for IMS. The Ribbon SBC as a P-CSCF/IBCF supports Rf interface. |
| 3GPP TS 32.260 | Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging | ||
| 3GPP TS 32.225 | Telecommunication management; Charging management; Charging data description for IMS domain | ||
| 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | Partially Comply (PC) | This specification defines the high-level charging architecture for 3GPP. The Ribbon SBC as a P-CSCF/IBCF supports Rf interface. |
| 3GPP TS 32.260 | Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging | ||
| 3GPP TS 32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | ||
| 3GPPTS 32.299 | Telecommunication management; Charging management; Diameter charging applications | ||
| 3GPP TS 33.203 | 3G security; Access security for IP-based services | Partially Comply (PC) | |
| 3GPP TS 33.210 | IP Network Level Security | ||
| 3GPP 26.441 | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Codec for Enhanced Voice Services (EVS); General Overview | ||
| 3GPP TS 22.228 | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the Internet Protocol (IP) Multimedia core network Subsystem (IMS); Stage 1 | Partially Comply (PC) | |
| 3GPP TS 23.002 | Group Services and Systems Aspects; Network architecture | ||
| 3GPP TS 23.003 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification | ||
| 3GPP TS 23.167 | IMS Emergency Sessions | ||
| 3GPP TS 23.203 | 3rd Generation Partnership Project;. Technical Specification Group Services and Systems Aspects; Policy and charging control architecture | Partially Comply (PC) | Ribbon SBCs support the Rx interface. |
| 3GPP TS 23.207 | End-to-end Quality of Service (QoS) concept and architecture | Partially Comply (PC) | The SBC supports Rx interface towards PCRF. |
| 3GPP TS 23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | ||
| 3GPP TS 23.228 | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS);Stage 2 | Partially Comply (PC) | This standard defines IMS architecture. The Ribbon SBC complies to the applicable P-CSCF/IBCF procedures as noted in other standards. Note that the Ribbon SBC does not support SigComp. |
| 3GPP TS 23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | Partially Comply (PC) | This standard defines the architecture for access transfer and Inter-UE transfer procedures. Ribbon SBC supports applicable for procedures for ATCF/ATGW, PS-PS access transfer, Inter-UE Transfer procedures etc. Note that the Ribbon SBC does not support CS media for IMS sessions. |
| 3GPP TS 23.292 | IP Multimedia System (IMS) centralized services; Stage 2 | Partially Comply (PC) | |
| 3GPP TS 24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | ||
| 3GPP TS 24.173 | 3rd Generation Partnership Project Technical Specification Group Core Network and Terminals;; IMS multimedia telephony communication service and supplementary services; Stage 3 | ||
| 3GPP TS 24.182 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification | Partially Comply (PC) | Note that the SBC Core portfolio does not support an "application/sdp" MIME body with the Content-Disposition set to "early-session" as specified in IETF RFC 3959 and this is optional as per 29.165. Note that the actual CAT service is in the scope of IMS AS and SBC’s scope is limited to transparently passing relevant headers and message-bodies. |
| 3GPP TS 24.183 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification | Partially Comply (PC) | Note that the SBC Core portfolio does not support an "application/sdp" MIME body with the Content-Disposition set to "early-session" as specified in IETF RFC 3959 and this is optional as per 29.165. Note that the actual CAT service is in the scope of IMS AS and SBC’s scope is limited to transparently passing relevant headers and message-bodies. |
| 3GPP TS 24.229 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | ||
| 3GPP TS 24.237 | 3rd Generation Partnership Project; IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 | ||
| 3GPP TS 24.239 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | ||
| 3GPP TS 24.259 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Personal Network Management (PNM); Stage 3 | ||
| 3GPP TS 24.341 | Support of SMS over IP networks; Stage 3 | ||
| 3GPP TS 24.604 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.605 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.606 | Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.607 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.608 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.610 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.611 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Anonymous Communication Rejection (ACR) and Communication Barring (CB); using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.615 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.616 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.623 | Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Simulation Services | ||
| 3GPP TS 24.628 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem | ||
| 3GPP TS 24.629 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.642 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | ||
| 3GPP TS 24.654 | Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification) | ||
| 3GPP TS 26.071 | Mandatory speech CODEC speech processing functions; AMR speech Codec; General description | ||
| 3GPP TS 26.090 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions | ||
| 3GPP TS 26.093 | Mandatory speech codec speech processing functions Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation | ||
| 3GPP TS 26.103 | Speech codec list for GSM and UMTS | Partially Comply (PC) | GSM-FR,HR and UMTS codecs are not supported for transcoding. The SBC portfolio supports AMR-NB and AMR-WB all mode sets as per RFC 4867. 3G-324M is not supported. Audio codec transparency/SMM are used to relay these codecs. |
| 3GPP TS 26.114 | 3rd Generation Partnership Project;Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction | Partially Comply (PC) | Audio codecs AMR and ANR-WB are supported in all modes. EVS supported in NB and WB only. RTCP profiles and SDPCapNeg not supported. ECN bit is not supported. RTCP-APP is not supported. Video codecs are supported in passthru. |
| 3GPP TS 26.235 | Packet Switched Conversational Multimedia Application; Default Codecs | Partially Comply (PC) | All audio. Video and text codecs are supported. RFC 4060 is not supported. |
| 3GPP TS 26.236 | Packet Switched Conversational Multimedia Applications; Transport Protocols | ||
| 3GPP TS 26.445 | Universal Mobile Telecommunications System (UMTS); LTE; Codec for Enhanced Voice Services (EVS); Detailed algorithmic description | ||
| 3GPP TS 29.162 | Interworking between the IM CN subsystem and IP networks | ||
| 3GPP TS 29.165 | 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Inter-IMS Network to Network Interface (NNI) | Partially Comply (PC) | Ribbon's SBC portfolio provides an integrated IBCF and TrGW; i.e., it provides signaling as well as media functionality in a single device. Ribbon SBCs support most all of the procedures as per 3GPP TS 29.165, including: support for network topology hiding, SIP signaling screening, IMS-Application Level Gateway (ALG), transcoding, screening SIP signaling, generation of charging data records, IP version interworking, RCS/MSRP, and more. Ribbon SBCs support audio, video and MSRP streams. |
| 3GPP TS 29.235 | Interworking between SIP-I based circuit-switched core network and other networks | ||
| 3GPP TS 32.225 | Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS) | Partially Comply (PC) | This specification defines the high-level charging architecture for IMS. The Ribbon SBC as a P-CSCF/IBCF supports Rf interface. |
| 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | Partially Comply (PC) | This specification defines the high-level charging architecture for 3GPP. The Ribbon SBC as a P-CSCF/IBCF supports Rf interface. |
| 3GPP TS 32.260 | Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging | ||
| 3GPP TS 32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | ||
| 3GPP TS 33.203 | 3G security; Access security for IP-based services | The SBC 5400/7000 partially support 33.203 and this deals with IMS AKA and other IMS authentication mechanisms. Note that the SBC CE does not claim any access feature compliance and hence if it is CE, it is Not Compliant. | |
| 3GPP TS 33.210 | IP Network Level Security | ||
| 3GPP TS 32.299 | Telecommunication management; Charging management; Diameter charging applications |
ETSI
Supported ETSI Standards
| Standard | Description | Noted | Description |
|---|---|---|---|
| ETSI ES 282 001 | NGN Functional Architecture Release 1 | Partially Comply (PC) | The Ribbon SBC acts as a P-CSCF and a combined IBGF/IBCF/TrGW. The Ribbon SBC, as a P-CSCF does not support Gq` and Rq interfaces towards RACS. |
| ETSI ES 282 002 | PSTN/ISDN Emulation Sub-system (PES); Functional architecture | Partially Comply (PC) | Ribbon does not support AGCF procedures and the Ribbon SBC, as a P-CSCF does not support Gq` and Rq interfaces towards RACS. The Ribbon SBC as a IBCF supports the applicable SBC procedures in passthrough mode. |
| ETSI ES 282 007 | NGN IMS Architecture | Partially Comply (PC) | The Ribbon SBC supports P-CSCF and combined IBCF/IBGF functionality. |
| ETSI EN 383 001 | Interworking for SIP/SIP-T (BICC, ISUP) | Partially Comply (PC) | Supported for SIP-I on the Ribbon SBCs, but BICC is not supported. |
| ETSI ES 283 003 | NGN SIP and SDP | ||
| ETSI TS 181 005 | Services and Capabilities Requirements | ||
| ETSI TS 181 006 | Services and Capabilities Requirements for TISPAN NGN Rel. 1 | ||
| ETSI TS 182 006 | IMS stage 2 Endorsement | ||
| ETSI TS 182 012 | IMS-based PSTN/ISDN Emulation Subsystem; Functional Architecture | ||
| ETSI TS 183 002 | Common Basis Communication Procedures, Protocol Specification | ||
| ETSI TS 183 043 | IMS-based PSTN/ISDN Emulation Stage 3 Specification | ||
| ETSI TS 187 001 | NGN Security requirements | ||
| ETSI TS 187 003 | Security Architecture | Partially Comply (PC) | We support IMS AKA, SIP Digest with and without TLS, GIBA authentication schemes. We don’t support some of annexures of this spec like NASS-IMS-Bundled-Authentication etc. |
| ESTI EN 300 356-1 | Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: ISUP Basic services[ITU T Recommendations Q.761 to Q.764 (1997), modified | ||
| ETSI ES 201 235-2 V1.2.1 (2002-03) | Access and Terminals (AT); Specification of Dual-Tone Multi-Frequency (DTMF) Transmitters and Receivers; Part 2: Transmitters | ||
| ETSI ETS 300 374-1 | Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: Protocol specification | ||
| ETSI PRI (Q.931 – ETSI EN 300-403) | Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. One (DSS1) Protocol; Signalling Network Layer for Circuit- Mode Basic Call Control; Protocol Specification | ||
| ETSI TR 103 393 V1.1.1 (2016-03) | Emergency Communications (EMTEL); Advanced Mobile Location for emergency calls |
FIPS
Modified: for 10.1.3
| Standard | Noted | Description |
|---|---|---|
| FIPS-140-3 | Fully Compliant (FC) | Federal Information Processing Standards Publication (FIPS) 140-3: Security requirements for cryptographic equipment |
GSMA
Supported GSMA Standards
| Standard | Description | Noted | Description |
|---|---|---|---|
| GSMA IR.34 | Guidelines for IPX Provider networks (Previously Inter-Service Provider IP Backbone Guidelines) | ||
| GSMA IR.65 | IMS Roaming and Interworking Guidelines | ||
| GSMA IR.74 | Video Share Interoperability Specification | ||
| GSMA IR.77 | Inter-Operator IP Backbone Security Requirements For Service Providers and Inter-operator IP backbone Providers | ||
| GSMA IR.79 | Image Share Interoperability Specification | ||
| GSMA IR.83 | SIP-I Interworking Description | ||
| GSMA IR.84 | Video Share Phase 2 Interoperability Specification | Partially Comply (PC) | |
| GSMA IR.90 | RCS Interworking Guidelines | ||
| GSMA IR.92 | IMS Profile for Voice and SMS | ||
| GSMA IR.94 | IMS Profile for Conversational Video Service | ||
| GSMA IR.95 | SIP – SDP Inter-IMS NNI Profile | Partially Comply (PC) | Unrecognized header/response code handling. Handling of requests/responses, where a Header mandatory for processing is missing |
| GSMA NGRAI | Next Generation Roaming and Interoperability (NGRAI) Project Scope White Paper | ||
| GSMA RCC.07 | Rich Communication Suite 5.1 Advanced Communications Services and Client Specification | ||
| GSMA RCC.71 | RCS Universal Profile Service Definition Document | Partially Comply (PC) | |
| GSMA SE.35 | IMS Services and Applications | Partially Comply (PC) |
IETF
Supported IETF Standards
| Standard | Description | Noted | Description |
|---|---|---|---|
| RFC 768 | User Datagram Protocol | ||
| RFC 791 (updated by RFC 1349) | Internet Protocol (Type of Service in the Internet Protocol Suite) | ||
| RFC 792 (updated by RFC 950, RFC 4884) | Internet Control Message Protocol | ||
| RFC 793 (updated by RFC 3168) | Transmission Control Protocol | ||
| RFC 826 | Ethernet Address Resolution Protocol | ||
| RFC 1305 | Network Time Protocol (Version 3) Specification, Implementation | ||
| RFC 1591 | Domain Name System Structure and Delegation | ||
| RFC 1878 | Variable Length Subnet Table For IPv4 | ||
| RFC 1889 | RTP: A Transport Protocol for Real-Time Applications | ||
| RFC 2198 | RTP Payload for Redundant Audio Data | Partially Comply (PC) | RFC 2198 is not supported for transcoding scenarios. There is some support for media that is passed through the SBC without transrating or transcoding applied. |
| RFC 2327 | SDP | ||
| RFC 2409 | The Internet Key Exchange (IKE) | ||
| RFC 2410 | The NULL Encryption Algorithm and Its Use With Ipsec | ||
| RFC 2460 | Internet Protocol Version 6 (IPv6) Specification | ||
| RFC 2461 (updated by 4311) | Neighbor Discovery for IP Version 6 (IPv6) | ||
| RFC 2464 | Transmission of IPv6 Packets over Ethernet Networks | ||
| RFC 2474 | Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers | ||
| RFC 2475 | An Architecture for Differentiated Services | ||
| RFC 2617 | HTTP Authentication: Basic and Digest Access Authentication | ||
| RFC 2675 | IPv6 Jumbograms | ||
| RFC 2711 | IPv6 Router Alert Option | ||
| RFC 2766 (updated by 3152) | Network Address Translation - Protocol Translation (NAT-PT) | ||
| RFC 2865 (updated by 2868, RFC 3575) | Remote Authentication Dial In User Service (RADIUS) | ||
| RFC 2866 (updated by RFC 2867) | RADIUS Accounting | ||
| RFC 2833 | RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals | ||
| RFC 2915 | The Naming Authority Pointer (NAPTR) DNS Resource Record | ||
| RFC 2916 | E.164 number and DNS | ||
| RFC 2976 | The SIP INFO Method | ||
| RFC 3087 | Control of Service Context using SIP Request-URI | ||
| RFC 3164 | The BSD Syslog Protocol | ||
| RFC 3204 | MIME media type ISUP | ||
| RFC 3260 | New Terminology and Clarifications for Diffserv | ||
| RFC 3261 | SIP: Session Initiation Protocol (SIP) | ||
| RFC 3262 | Reliability of Provisional Responses in Session Initiation Protocol (SIP) | ||
| RFC 3263 | Session Initiation Protocol (SIP): Locating SIP Servers | ||
| RFC 3264 | An Offer/Answer Model with the Session Description Protocol (SDP) | ||
| RFC 3265 | Session Initiation Protocol (SIP) - Specific Event Notification | ||
| RFC 3267 (2002) | Real-time Transport Protocol RTP Payload Format and File Storage Format for Audio Codecs | ||
| RFC 3309 | Stream Control Transmission Protocol (SCTP) Checksum | ||
| RFC 3311 | The Session Initiation Protocol (SIP) UPDATE Method | ||
| RFC 3312 | Integration of Resource Management and Session Initiation Protocol (SIP) | ||
| RFC 3313 | Private Session Initiation Protocol (SIP) Extensions for Media Authorization | ||
| RFC 3323 | A Privacy Mechanism for the Session Initiation Protocol (SIP) | ||
| RFC 3324 | Short Term Requirements for Network Asserted Identity | ||
| RFC 3325 | Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | ||
| RFC 3326 | The Reason Header Field for the Session Initiation Protocol (SIP) | ||
| RFC 3327 | Session Initiation Protocol (SIP) Extension Header Field for Registering Non- Adjacent Contacts | ||
| RFC 3329 | Security Mechanism Agreement for the Session Initiation Protocol (SIP) | Partially Comply (PC) | Security-Client Received by the SBC Security-Server Received by the SBC |
| RFC 3372 | Session Initiation Protocol for Telephones (SIP-T): Context and Architectures | ||
| RFC 3389 | Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) | ||
| RFC 3398 | ISUP to SIP Mapping | ||
| RFC 3411 | An Architecture for Describing SNMP Management Frameworks | ||
| RFC 3412 | Message Processing and Dispatching for SNMP | ||
| RFC 3413 | Simple Network Management Protocol (SNMP) Applications | ||
| RFC 3414 | User-based Security Model (USM) for version 3 of the Simple Network Management | ||
| RFC 3415 | View-based Access Control Model (VACM) for the SNMP | ||
| RFC 3418 | Management Information Base (MIB) for the SNMP | ||
| RFC 3420 | Internet Media Type message/sipfrag | ||
| RFC 3428 | Session Initiation Protocol (SIP) Extension for Instant Messaging | ||
| RFC 3455 | Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) | ||
| RFC 3486 | Compressing the Session Initiation Protocol (SIP) | ||
| RFC 3513 | Internet Protocol Version 6 (IPv6) Addressing Architecture | ||
| RFC 3515 | The Session Initiation Protocol (SIP) Refer Method | ||
| RFC 3550 | RTP: A Transport Protocol for Real-Time Applications | ||
| RFC 3551 | RTP Profile for Audio and Video Conferences with Minimal Control | ||
| RFC 3556 | Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth | Partially Comply (PC) | Supported for video. |
| RFC 3581 | An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing | ||
| RFC 3584 | SIP Extension for Symmetric Response Routing | ||
| RFC 3588 | Diameter Base Protocol | ||
| RFC 3596 | DNS Extensions to Support IP Version 6 | ||
| RFC 3605 | Real Time Control Protocol (RTCP) attribute in SDP | ||
| RFC 3608 | Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration | ||
| RFC 3611 | RTP Control Protocol Extended Reports (RTCP XR) | Partially Comply (PC) | Partially Supported, only as passthrough. |
| RFC 3680 | A Session Initiation Protocol (SIP) Event Package for Registrations | ||
| RFC 3711 | Secure Real-time Transport Protocol | ||
| RFC 3761 | The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) | ||
| RFC 3826 | The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User- | ||
| RFC 3840 | Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) | ||
| RFC 3841 | Caller Preferences for the Session Initiation Protocol (SIP) | ||
| RFC 3842 | A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) | ||
| RFC 3862 | Common Presence and Instant Messaging (CPIM): Message Format | ||
| RFC 3891 | The Session Initiation Protocol (SIP) "Replaces" Header | ||
| RFC 3892 | The Session Initiation Protocol (SIP) Referred-By Mechanism | ||
| RFC 3903 | Session Initiation Protocol (SIP) Extension for Event State Publication | ||
| RFC 3947 | Negotiation of NAT-Traversal in the IKE | ||
| RFC 3951 | Internet Low Bit Rate Codec (iLBC) | ||
| RFC 3952 | RTP Payload Format for iLBC (internet Low Bit Rate Codec) Speech | ||
| RFC 3959 | The Early Session Disposition Type for the Session Initiation Protocol (SIP) | ||
| RFC 3960 | Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) | ||
| RFC 3966 | The tel URI for Telephone Numbers | ||
| RFC 3994 | Indication of Message Composition for Instant Messaging | ||
| RFC 4006 | Diameter Credit-Control Application | Partially Comply (PC) | The SBC currently supports the Rf interface for Ribbon SBCs acting as P-CSCFs and/or IBCFs as per procedures and syntax defined in TS 32.260.Ro interface is not applicable to the SBC. |
| RFC 4022 | Management Information Base for the Transmission Control Protocol (TCP) | ||
| RFC 4028 | Session Timers in the Session Initiation Protocol (SIP) | ||
| RFC 4032 | Update to the Session Initiation Protocol (SIP) Preconditions Framework | ||
| RFC 4092 | Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP) | Partially Comply (PC) | ICE-Lite is supported in lieu of ANAT. ANAT has been deprecated in RFC 5245s. |
| RFC 4103 | RTP Payload for Text Conversation | ||
| RFC 4113 | Management Information Base for the User Datagram Protocol (UDP) | ||
| RFC 4109 | Algorithms for Internet Key Exchange version 1 (IKEv1) | ||
| RFC 4117 | Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Thurd Party Call Control (3pcc) | ||
| RFC 4119 | A Presence-based GEOPRIV Location Object Format | Partially Comply (PC) | Supported as passthrough. |
| RFC 4123 | Session Initiation Protocol (SIP)-H.323 Interworking Requirements | ||
| RFC 4145 | TCP-Based Media Transport in the Session Description Protocol (SDP) | ||
| RFC 4168 | The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) | ||
| RFC 4213 | Basic Transition Mechanisms for IPv6 Hosts and Routers | ||
| RFC 4291 | Internet Protocol Version 6 (IPv6) Addressing Architecture”; RFC3513 (Obsoletes RFC2373, Obsoleted by RFC4291) | ||
| RFC 4292 | IP Forwarding Table MIB | ||
| RFC 4293 | Management Information Base for the Internet Protocol (IP) | ||
| RFC 4294 | IPv6 Node Requirements | ||
| RFC 4244 | An Extension to the Session Initiation Protocol (SIP) for Request History Information | ||
| RFC 4293 | Management Information Base for the Internet Protocol (IP) | ||
| RFC 4301 | Security Architecture for the Internet Protocol | ||
| RFC 4302 | IP Authentication Header | ||
| RFC 4303 | IP Encapsulating Security Payload (ESP) | ||
| RFC 4306 | Internet Key Exchange (IKEv2) Protocol | ||
| RFC 4307 | Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2) | ||
| RFC 4308 | Cryptographic Suites for Ipsec | ||
| RFC 4412 | Communications Resource Priority for the Session Initiation Protocol (SIP) | ||
| RFC 4443 | Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification | ||
| RFC 4458 | Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR) | ||
| RFC 4488 | Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription | ||
| RFC 4538 | Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) | ||
| RFC 4566 | Session Description Protocol (SDP) | ||
| RFC 4567 | Key Management Extensions for SDP and RTSP | ||
| RFC 4568 | SDP Security Descriptions for Media Streams | ||
| RFC 4572 | Connection-Oriented Media Transport over the Transport Layer Security (TLS) | ||
| RFC 4573 | MIME Type Registration for RTP Payload Format for H.224 | ||
| RFC 4575 | A Session Initiation Protocol (SIP) Event Package for Conference State | ||
| RFC 4583 | Session Description Protocol (SDP) Format for Binary Floor Control Protocol | ||
| RFC 4585 | Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) | ||
| RFC 4629 | RTP Payload Format for ITU-T Rec. H.264 Video | Partially Comply (PC) | Supported only as passthrough. |
| RFC 4662 | A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists | ||
| RFC 4694 | Number Portability Parameters for the "tel" URI | ||
| RFC 4730 | A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML) | ||
| RFC 4733 | RTP Payload for DTMF Digits; Telephony Tones; and Telephony Signals | Partially Comply (PC) | The Ribbon SBC portfolio supports RFC 4733 as follows: The Ribbon SBCs support sending and receiving DTMF named events as per RFC-4733. They also support DTMF events at higher frequency for WB codecs. There are three minor exceptions:
|
| RFC 4753 | ECP Groups for IKE and IKEv2 | ||
| RFC 4835 | Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) | Partially Comply (PC) | The following ESP algorithms are supported:
The actual encryption method to use from among the supported algorithms is configurable. |
| RFC 4861 | Neighbor Discovery for IP Version 6 (IPv6) | ||
| RFC 4867 | RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs | ||
| RFC 4916 | Connected Identity in the Session Initiation Protocol (SIP) | Partially Comply (PC) | The Ribbon SBC portfolio partially supports RFC 4916, Connected Identity in SIP. If an UPDATE/re-INVITE has only media address change, it is not relayed to the other leg. |
| RFC 4961 | Symmetric RTP / RTP Control Protocol (RTCP) | ||
| RFC 4964 | The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular | Partially Comply (PC) | Supported as passthrough. |
| RFC 4967 | Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier | ||
| RFC 4975 | Message Session Relay Protocol (MSRP) | ||
| RFC 4976 | Relay Extensions for the Message Session Relay Protocol (MSRP) | ||
| RFC 5002 | The Session Initiation Protocol (SIP)P-Profile-Key Private Header (P-Header) | ||
| RFC 5009 | Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media | Partially Comply (PC) | The Ribbon SBC portfolio can transparently pass this header if received. The Ribbon SBC portfolio does not insert this header by itself. |
| RFC 5031 | A Uniform Resource Name (URN) for Emergency and Other Well-Known Services | ||
| RFC 5049 | Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP) | ||
| RFC 5067 | Infrastructure ENUM Requirements | ||
| RFC 5079 | ACR Response Code | Partially Comply (PC) | Supported as passthrough. |
| RFC 5095 | Network Time Protocol Version 4 (for IPv6) | ||
| RFC 5104 | Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF) | Partially Comply (PC) | The Ribbon SBC portfolio supports transparent relay and manipulation of these SDP parameters. |
| RFC 5139 | Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) | Partially Comply (PC) | Supported as passthrough. |
| RFC 5168 | XML Schema for Media Control | ||
| RFC 5227 | IPv4 Address Conflict Detection | ||
| RFC 5245 | Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols | Partially Comply (PC) | The SBC portfolio also partially supports RFC 5245 ICE for traversal of NAT. This can be configured on a per IP trunk group basis allowing the SBC to act as an ICE-lite agent allowing the traversal of NAT/firewalls by using STUN messaging (which after negotiating the local and remote address for media is periodically sent to keep the NAT pinhole open). In an ICE-lite role the SBC will respond to, but not generate, STUN Binding Requests, this is appropriate for an SBC since it always has a publicly addressable IP port for media. This approach works well when the SBC interoperates with WebRTC endpoints. Furthermore, the SBC can be configured to behave similar to a full-ICE endpoint to interoperate with peers which require a STUN Binding Request to be generated in order to complete ICE procedures (such as Microsoft Lync endpoints). |
| RFC 5282 | Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol | ||
| RFC 5285 | A General Mechanism for RTP Header Extensions | ||
| RFC 5318 | The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P- Header) | ||
| RFC 5343 | Simple Network Management Protocol (SNMP) Context EngineID Discovery | ||
| RFC 5359 | Session Initiation Protocol Service Examples | Partially Comply (PC) | The Ribbon SBC portfolio is only partially supported (join header is not supported). This RFC provides examples of Best Current Practices for SIP Services. Ribbon supports a comprehensive and robust SIP implementation and we believe that our SBC portfolio can fully meet TOT's SIP services requirements. |
| RFC 5360 | A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP) | Partially Comply (PC) | The Ribbon SBC portfolio partially supports RFC 5360 – A Framework for Consent-Based Communications in SIP. Consent-based communications may be transparently passed through Ribbon SBCs. |
| RFC 5365 | Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) | ||
| RFC 5366 | Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP) | ||
| RFC 5367 | Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP) | ||
| RFC 5368 | Referring to Multiple Resources in the Session Initiation Protocol (SIP) | ||
| RFC 5373 | Requesting Answering Modes for the Session Initiation Protocol (SIP) | Partially Comply (PC) | Passthrough for relevant headers is supported. Passthrough for "answermode" option tag requires use of SIP Message Manipulation capability. |
| RFC 5393 | Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies | ||
| RFC 5438 RFC 5438 Errata | Instant Message Disposition Notification (IMDN) | Partially Comply (PC) | The Ribbon SBC portfolio Supports pass through with use of SMM for Content-Disposition "notification" |
| RFC 5491 | GEOPRIV Presence Information Data Format Location Object (PIDF-LO)Usage Clarification, Considerations, and Recommendations | ||
| RFC 5502 | The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem | ||
| RFC 5503 | Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting | Partially Comply (PC) | Partial support only for the P-DCS-LAES header. |
| RFC 5547 | SDP Offer/Answer Mechanism To Enable File Transfer | ||
| RFC 5590 | Transport Subsystem for the Simple Network Management Protocol (SNMP) | ||
| RFC 5621 | Message Body Handling in the Session Initiation Protocol (SIP) | Partially Comply (PC) | Only multipart/mixed is supported from processing perspective. All types can be passed through by also using SIP Message Manipulation for certain cases. |
| RFC 5626 | Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) | ||
| RFC 5627 | Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) | ||
| RFC 5658 | Addressing Record-Route Issues in the Session Initiation Protocol (SIP) | ||
| RFC 5688 | A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes | ||
| RFC 5705 | Keying Material Exporters for Transport Layer Security (TLS) | ||
| RFC 5763 | Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) | ||
| RFC 5764 | Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP) | ||
| RFC 5768 | Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP) | ||
| RFC 5798 | Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 | ||
| RFC 5806 | Diversion Indication in SIP | ||
| RFC 5839 | An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification | Partially Comply (PC) | Supported as passthrough. |
| RFC 5881 | Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) | ||
| RFC 5883 | Bidirectional Forwarding Detection (BFD) for Multihop Paths | ||
| RFC 5905 | Network Time Protocol Version 4 (for IPv6) | ||
| RFC 5939 | Session Description Protocol (SDP) Capability Negotiation | ||
| RFC 5954 | Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261 | ||
| RFC 5966 | DNS Transport over TCP - Implementation Requirements | ||
| RFC 5976 | Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes | Partially Comply (PC) | Some of the metrics are present in statistics for calls, CDRs, e.g. peak rate, diffserv value etc. |
| RFC 6044 | Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP) | ||
| RFC 6050 | A Session Initiation Protocol (SIP) Extension for the Identification of Services | ||
| RFC 6086 | Session Initiation Protocol (SIP) INFO Method and Package Framework | Partially Comply (PC) | The Ribbon SBC portfolio partially supports RFC 6086 – SIP INFO Method and Package Framework; the SBCs’ SIP Message Manipulation rules must be used to pass through unknown Content-Disposition values. |
| RFC 6135 | Alternative Connection Model for MSRP UA | ||
| RFC 6140 | Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) | ||
| RFC 6184 | RTP Payload Format for H.264 Video | ||
| RFC 6223 | Indication of Support for Keep-Alive | ||
| RFC 6228 | Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog | ||
| RFC 6337 | Session Initiation Protocol (SIP) Usage of the Offer/Answer Model | ||
| RFC 6347 | Datagram Transport Layer Security Version 1.2 | ||
| RFC 6377 | Non-reliable provisional response to the INVITE | ||
| RFC 6432 | Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses | Partially Comply (PC) | The Ribbon SBC portfolio partially supports the Reason Header as defined in both RFC 3326 and RFC 6432. The Ribbon SBCs comply with RFC3326 as it pertains to Q.850 cause values, and support RFC 6432 in pass-through mode only. The Ribbon SBCs can be configured to either ignore or use the SIP status code or ITU-T Q.850 cause codes received in the Reason Header, and can also be configured to include (or not) these values in the responses sent. |
| RFC 6442 | Location Conveyance for the Session Initiation Protocol | ||
| RFC 6665 | SIP-Specific Event Notification | ||
| RFC 6714 | Connection Establishment for Media Anchoring | ||
| RFC 6716 | Definition of the Opus Audio Codec | ||
| RFC 6724 | Default Address Selection for Internet Protocol Version 6 (IPv6) | ||
| RFC 6733 | Diameter Base Protocol | ||
| RFC 6794 | A Framework for Session Initiation Protocol (SIP) Session Policies | Partially Comply (PC) | Supported as passthrough. |
| RFC 6809 | Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP) | ||
| RFC 6881 | Best Current Practice for Communications Services in Support of Emergency Calling | Partially Comply (PC) | The Ribbon SBC portfolio provides support to detect emergency calls and treat them with higher priority. Location information is supported only as passthrough. |
| RFC 6891 | Extension Mechanisms for DNS (EDNS (0) | ||
| RFC 6910 | Completion of Calls for the Session Initiation Protocol (SIP) | Partially Comply (PC) | Supported as passthrough. |
| RFC 6961 | The Transport Layer Security (TLS) Multiple Certificate Status Request Extension | ||
| RFC 7090 | Public Safety Answering Point (PSAP) Callback | Partially Comply (PC) | Supported as passthrough. |
| RFC 7135 | Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications | ||
| RFC 7200 | A Session Initiation Protocol (SIP) Load-Control Event Package | ||
| RFC 7245 | An Architecture for Media Recording Using the Session Initiation Protocol | ||
| RFC 7315 | Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP | Partially Comply (PC) | The Ribbon SBC portfolio supports the P-Charging-Vector. SBCs can be configured to insert or transparently pass P-Charging-Vector headers. The SBCs support “icid”, “orig-ioi”, and “term-ioi” parameters. Additionally, support for transit-ioi, related-icid, access-network-charging-info parameters is being added in an future (M2 compliant). |
| RFC 7316 | The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header) | Partially Comply (PC) | Supported as passthrough. Can be added with SMM as needed. |
| RFC 7329 | A Session Identifier for the Session Initiation Protocol (SIP) | ||
| RFC 7332 | Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs) | ||
| RFC 7339 | Session Initiation Protocol (SIP) Overload Control | ||
| RFC 7433 | A Mechanism for Transporting User-to-User Call Control Information in SIP | Partially Comply (PC) | Passthrough only. |
| RFC 7434 | Interworking ISDN Call Control User Information with SIP | Partially Comply (PC) | Supported as passthrough. |
| RFC 7459 | Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO) | ||
| RFC 7462 | URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP) | Partially Comply (PC) | Supported as passthrough and Alert-Info can be interworked to P-Early-Media. Furthermore, Alert-Info can be used to select the tone to play by the SBC if it is configured to do so. |
| RFC 7549 | 3GPP SIP URI Inter-Operator Traffic Leg Parameter | ||
| RFC 7627 | Transport Layer Security (TLS) Session Hash and Extended Master Secret Extension | Modified: for 10.1.6 | |
| RFC 7647 | Clarifications for the Use of REFER with RFC 6665 | Partially Comply (PC) | Supported as passthrough. |
| RFC 7798 | RTP Payload Format for High Efficiency Video Coding (HEVC) | ||
| RFC 7865 | Session Initiation Protocol (SIP) Recording Metadata | ||
| RFC 7866 | Session Recording Protocol | ||
| RFC 7913 | P-Access-Network-Info ABNF Update | ||
| RFC 7989 | End-to-End Session Identification in IP-Based Multimedia Communication Networks | ||
| RFC 8068 | Session Initiation Protocol (SIP) Recording Call Flows | ||
| RFC 8119 | SIP "cause" URI Parameter for Service Number Translation | Partially Comply (PC) | Passthrough only. |
| RFC 8197 | A SIP Response Code for Unwanted Calls | ||
| RFC 8224 | Authenticated Identity Management in the Session Initiation Protocol (SIP) | ||
| IETFdraft-ietf-insipid- logme-marking-09 | Marking SIP Messages to be Logged | Partially Comply (PC) | Supported as passthrough. |
| IETF draft-jesske- sipcore-reason-q850- loc-00 | ISUP Cause Location Parameter for the SIP Reason Header Field | Partially Comply (PC) | Supported as passthrough and can be added as needed with SMM. |
| IETF draft-mohali-sipcore-originating- cdiv-parameter-00 | A P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP) | Partially Comply (PC) | Supported as passthrough. |
ITU
Supported ITU Standards
| Standard | Description |
|---|---|
| ITU-T G.107 | The E-model: a computational model for use in transmission planning |
| ITU-T G.108 | Application of the E-model: A planning guide |
| ITU-T G.114 | International telephone connections and circuits – General Recommendations on the transmission quality for an entire international telephone connection |
| ITU-T G.711 | Pulse code modulation (PCM) of voice frequencies |
| ITU-T G.722 | 7 kHz audio-coding within 64 kbit/s |
| ITU-T G.729 | G.729 : Coding of speech at 8 kbit/s using conjugate-structure algebraic- code-excited linear prediction (CS-ACELP) |
| ITU-T Q.1912.5 | Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part |
| ITU-T Q771 – Q774 ETSI 300 134 ETSI 300 287 | Transaction Capabilities Application Part (TCAP) |
NENA
Supported NENA Standards
| Standard | Description | |
|---|---|---|
08-001 v2 | Interim VoIP Architecture for Enhanced 9-1-1 Services (i2) | |
PacketCable
Supported PacketCable Standards
| Standard | Description | |
|---|---|---|
PKT-SP-ESP-103-040113 | PacketCable Electronic Surveillance Specification | |
| PKT-SP-ES-DCI-C01-140314 | PacketCable 2.0 – PacketCable Electronic Surveillance Delivery Function to Collection Function Interface Specification | |
SIP Forum
Supported SIP Forum Standards
| Standard | Description | |
|---|---|---|
SIPConnect 1.0 | Direct IP peering between SIP-enabled IP PBXs and VoIP service provider networks | |
SIPConnect 1.1 | SIP-PBX/ Service Provider Interoperability | |
| SIPConnect 2.0 | Updated guidelines for SIP-PBX / Service Provider Interoperability | |
Telecommunication Technology Committee
| Standard | Description | |
|---|---|---|
JJ-90.30 | Common interconnection interface between IMS operator's networks. For more information, refer to https://www.ttc.or.jp/application/files/5615/5443/0175/JJ-90.30Ev5.pdf. | |
Other Specifications
Other Specifications
| Standard | Description |
|---|---|
| ACIF C518:2006 | Call Charging and Billing Accuracy |
| ACIF C519:2004 | End-to-End Network Performance for the Standard Telephone Service |
| ACIF C542:2003 | Industry Code: Billing |
| ACIF G.549:2000 | Interconnection Implementation Plan |
| ACIF G.557:2014 | Location Information for Emergency Calls |
| CA G632:2007 | Communication Alliance Guideline - Quality of Service parameters for networks using the Internet Protocol |
| CA G633:2007 | Communication Alliance Guideline - Testing Arrangements for Quality of Service Parameters for Internet Protocol Services |
| CA G634:2007 | Communication Alliance Guideline - Quality of Service parameters for Voice over Internet Protocol (VoIP) services |
| CA G635:2007 | Communication Alliance Guideline - Testing Arrangements for Quality of Service Parameters for Voice over Internet Protocol (VoIP) Services |
| ATIS-1000074 | Signature-Based Handling Of Asserted Information Using Tokens (Shaken) |
| ATIS-0300116 | Interoperability Standards between Next Generation Networks (NGN) for Signature-Based Handling of Asserted information Using Tokens (SHAKEN) |
| ATIS-1000080 | Signature-based Handling of Asserted information using toKENs (SHAKEN): Governance Model and Certificate Management |
| ATIS-0300251 | Codes for Identification of Service Providers for Information Exchange. |
| ATIS-1000054 | ATIS Technical Report on Next Generation Network Certificate Management. |
References
The following public websites provide standards definition details.
- http://www.ietf.org/
- http://www.rfc-editor.org/index.html
- http://en.wikipedia.org/wiki/Main_Page
- http://www.3gpp.org
- http://www.nena.org
- https://www.etsi.org
- https://www.cablelabs.com/specs
- https://www.ttc.or.jp/e
Overview
Content Tools