Standards & interoperability
Built on open standards
Interoperable with any compliant carrier, phone, or browser.
Pentacomm and PentaPhone implement the relevant IETF, ITU-T and W3C standards rather than proprietary variants — so they interoperate with FreeSWITCH, OpenSIPS, Kamailio, Asterisk, and any compliant carrier, phone, or browser. The tables below list the standards the platform conforms to, grouped by area.
No proprietary lock-in at the protocol layer — your carriers, your numbers, and your phones stay yours.
SIP signalling
| RFC 3261 | Session Initiation Protocol (SIP) — core signalling, transactions, dialogs. |
|---|---|
| RFC 6026 | Correct transaction handling of SIP 2xx responses. |
| RFC 3581 | Symmetric response routing (rport) for NAT traversal. |
| RFC 3264 | SDP offer/answer model. |
| RFC 4566 | Session Description Protocol (SDP). |
| RFC 5888 | SDP media grouping (BUNDLE) for media-gateway interoperability. |
| RFC 4028 | SIP session timers — dead-call detection on long calls. |
| RFC 3311 | SIP UPDATE method. |
| RFC 3325 | P-Asserted-Identity — trusted caller identity. |
| RFC 4916 | Connected identity in SIP. |
| RFC 5658 | Record-Route fix for dialogs behind NAT. |
Transport & mobility
| RFC 7118 | SIP over WebSocket — the signalling transport (secure WSS only). |
|---|---|
| RFC 6455 | The WebSocket protocol. |
| RFC 5626 | Client-initiated connections (reg-id, +sip.instance) for reliable registration. |
| RFC 8599 | Push-notification support for SIP — wakes offline devices for incoming calls. |
| TLS 1.3 / 1.2 | RFC 8446 / 5246 — all signalling encrypted in transit. |
Call control & services
| RFC 3515 | SIP REFER method — blind call transfer. |
|---|---|
| RFC 5589 | Call-transfer best practices — attended (consultative) transfer. |
| RFC 3891 | SIP "Replaces" header — dialog replacement during attended transfer. |
| RFC 6665 | SIP-specific event notification (SUBSCRIBE/NOTIFY). |
| RFC 3842 | Message-summary event — voicemail MWI. |
| RFC 4733 | DTMF as RTP telephone-events — in-call keypad, IVR navigation. |
Security & authentication
| RFC 7616 | Digest authentication — MD5 and SHA-256 credential challenge. |
|---|---|
| RFC 5763 / 5764 | DTLS-SRTP — mandatory media keying. |
| RFC 3711 | Secure RTP (SRTP) — media encryption. |
| RFC 4568 | SDES — SDP security descriptions for SRTP keying. |
| RFC 5280 | X.509 certificate and CRL profile. |
| RFC 6125 | Service identity verification in TLS. |
| RFC 7030 / 8555 | Certificate enrolment (EST) and ACME automation. |
| RFC 5116 / 3394 | AEAD (AES-GCM) and AES key-wrap — recording encryption. |
| RFC 7519 / 8725 | JSON Web Token (JWT) and JWT best current practice. |
| RFC 6749 | OAuth 2.0 authorization framework (token model). |
Media & codecs
| RFC 3550 / 3551 | RTP/RTCP real-time media transport and the audio/video profile. |
|---|---|
| RFC 8445 | ICE — connectivity establishment and NAT traversal for media. |
| RFC 6716 / 7587 | Opus wideband audio codec and its RTP payload format. |
| Codecs | Opus (preferred, wideband) · G.722 HD (ITU-T) · G.711 A-law / µ-law · G.729 · VP8 / H.264 (video). |
Web & data
| RFC 9110 | HTTP semantics and status codes. |
|---|---|
| RFC 6585 | Additional HTTP status codes (e.g. 429 rate-limit). |
| RFC 7233 | HTTP range requests — media streaming. |
| RFC 8259 | JSON data interchange format. |
| RFC 3339 | Date/time on the Internet (ISO 8601 timestamps). |
| RFC 3986 | Uniform Resource Identifier (URI) syntax. |
This reference spans the Pentacomm appliance and the PentaPhone mobile endpoint. Feature availability may depend on licensing and deployment.
Put your phone system in every pocket.
See Pentacomm running on a live appliance and PentaPhone registered against it — or against your existing SIP platform. Talk to us about a proof-of-concept, licensing, and deployment.
Talk to us