RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)

The Session Initiation Protocol (SIP) allows proxy servers to initiate TCP connections or to send asynchronous UDP datagrams to User Agents in order to…

Read RFC 5626 on the RFC Editor

Outgoing relationships (2 related RFCs)

Updates — RFC 3261: SIP: Session Initiation Protocol
Updates — RFC 3327: Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts

Incoming relationships (18 related RFCs)

Normatively referenced by — RFC 5627: Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5630: The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 7350: Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 6223: Indication of Support for Keep-Alive
Normatively referenced by — RFC 6011: Session Initiation Protocol (SIP) User Agent Configuration
Normatively referenced by — RFC 7904: A SIP Usage for REsource LOcation And Discovery (RELOAD)
Normatively referenced by — RFC 9248: Interoperability Profile for Relay User Equipment
Informatively referenced by — RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
Informatively referenced by — RFC 8839: Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)
Informatively referenced by — RFC 8489: Session Traversal Utilities for NAT (STUN)
Informatively referenced by — RFC 6230: Media Control Channel Framework
Informatively referenced by — RFC 5780: NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
Informatively referenced by — RFC 5923: Connection Reuse in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6809: Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 7118: The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 5947: Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6751: Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
Informatively referenced by — RFC 6140: Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)