Full detail about SIP Protocol

The SIP protocol

The SIP protocol defines several methods.

SIP methods defined in the SIP RFC

• SIP method ack: Used to facilitate reliable message exchange for INVITEs
• SIP method bye: Hangup a session
• SIP method cancel: Cancel an invite
• SIP method invite: Invite another UA to a session
• SIP method invite re-invite: Change a running session
• SIP method options
• SIP method register: Register a location with a SIP Registrar server

SIP method extensions from other RFCs

• SIP Message Waiting Indication: Extension in RFC 3842
• SIP method info: Extension in RFC 2976
• SIP method message: Extension in RFC 3428
• SIP method notify: Extension in RFC 2848 PINT
• SIP method prack: Extension in RFC 3262
• SIP method PUBLISH: Extension is RFC 3903
• SIP method refer: Extension in RFC 3515
• SIP method subscribe: Extension in RFC 2848 PINT
• SIP method unsubscribe: Extension in RFC 2848 PINT
• SIP method update: Extension in RFC 3311
• SIP Specific Event Notification: Extension in RFC 3265

SIP responses

• SIP response codes

SIP terms and definitions

• SIP Authentication
• SIP Compression
• SIP DTMF signalling
• SIP outbound proxy
• SIP proxy
• SIP redirect server
• SIP registrar server
• SIP URI - how to specify a SIP connection in an URL
• SIP URI non-numeric - how to specify non-numeric SIP URI

SIP RFCs

• RFC 2848 - The PINT Service Protocol: xtensions to SIP and SDP for IP Access to Telephone Call Service
• RFC 2976 - The SIP INFO Method
• RFC 3050 - Common Gateway Interface for SIP
• RFC 3087 - Control of Service Context using SIP Request-URI
• RFC 3261 Official Main SIP RFC
• RFC 3261 - SIP: Session Initiation Protocol (Main SIP RFC)
• RFC 3262 - Reliability of Provisional Responses in the 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 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 3319 - Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers
• 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)
• RFC 3361 - Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers
• RFC 3388 - Grouping of Media Lines in the Session Description Protocol (SDP)
• RFC 3420 - Internet Media Type message/sipfrag
• RFC 3428 - Session Initiation Protocol (SIP) Extension for Instant Messaging
• RFC 3485 - The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
• RFC 3486 - Compressing the Session Initiation Protocol (SIP)
• RFC 3487 - Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP)
• RFC 3515 - The Session Initiation Protocol (SIP) Refer Method
• RFC 3524 - Mapping of Media Streams to Resource Reservation Flows
• RFC 3966 - The tel URI for Telephone Numbers
• RFC 4694 - Number Portability Parameters for the ""tel"" URI * last minute

References

• Additional SIP Related IETF Documents, Drafts, and RFCs
• Formatted/explained version of RFC 3261 (over 250 pages!)
• RFC 3329 : Security Mechanism Agreement for the Session Initiation Protocol (SIP)
• The IETF SIP Working Group - on this page, you'll find all current Internet Drafts, RFCs and standards

Posted in: