SIP Capabilities

List of supported SIP features and link to the relevant PJSIP documentation and/or the standard document.

Base specs

• Core methods: RFC 3261: INVITE, CANCEL, BYE, REGISTER, OPTIONS, INFO

• Digest authentication (RFC 2617)

• Encoding and parsing of Bearer authenticaion (OAuth 2.0) (RFC 8898)

Transports

• UDP, TCP, TLS (server or mutual)

• DNS SRV resolution (RFC 3263)

• IPv6

• QoS (DSCP, WMM)

Routing/NAT

• rport (RFC 3581)

• Service-Route header (RFC 3608)

• SIP outbound for TCP/TLS (RFC 5626)

• Path header (with SIP outbound) (RFC 3327)

• ICE option tag (RFC 5768)

• Trickle ICE on SIP: (RFC 8840)

Call

• Offer/answer (RFC 3264)

• hold, unhold

• redirection

• transfer/REFER (attended and unattended):

  • Base (RFC 3515)

  • replaces (RFC 3891)

  • Referred-by (RFC 3892)

• sipfrag support (RFC 3420)

• norefersub (RFC 4488)

• UPDATE (RFC 3311)

• 100rel/PRACK (RFC 3262)

• tel: URI (RFC 3966)

• Session Timers (RFC 4028)

• Reason header (RFC 3326, partially supported)

• P-Header (RFC 3325, partially supported)

SDP

• RFC 2327 (obsoleted by RFC 4566)

• RTCP attribute (RFC 3605)

• IPv6 support (RFC 3266)

• SDP media ID (RFC 5888)

• SDP for ICE (RFC 8839)

Presence and IM

• Event framework (SUBSCRIBE, NOTIFY) (RFC 3265)

• Event publication (PUBLISH) (RFC 3903)

• MESSAGE (RFC 3428)

• typing indication (RFC 3994)

• pidf+xml (RFC 3856, RFC 3863)

• xpidf+xml

• RPID (subset) (RFC 4480)

Other extensions

• INFO (RFC 2976)

• AKA, AKA-v2 authentication (RFC 3310, RFC 4169)

• ICE option tag (RFC 5768)

• Message summary/message waiting indication (MWI, RFC 3842)

• Multipart (RFC 2046, RFC 5621)

Compliance, best current practices

• Issues with Non-INVITE transaction (RFC 4320)

• Issues with INVITE transaction (RFC 4321)

• Multiple dialog usages (RFC 5057)

• SIP torture messages (RFC 4475, tested when applicable)

• SIP torture for IPv6 (RFC 5118)

• Message Body Handling (RFC 5621. Partial compliance: multipart is supported, but Content-Disposition header is not handled)

• The use of SIPS (RFC 5630. Partial compliance: SIPS is supported, but still make use of transport=tls parameter)