Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 263 views

    SIP Headers

    Uploaded by

    Bikash Dash
    The document describes SIP headers and SDP messages used in SIP signaling. It provides breakdowns of the key headers in a sample SIP INVITE message. The main headers in a SIP message like INVITE are mandatory and include Via, From, To, Call-ID and CSeq. The Via header contains information for routing responses. The From and To headers contain caller and callee identifiers. Call-ID provides a unique identifier for the call and CSeq contains the request sequence number and method.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    SIP Headers

    Uploaded by

    Bikash Dash
    263 views22 pages
    The document describes SIP headers and SDP messages used in SIP signaling. It provides breakdowns of the key headers in a sample SIP INVITE message. The main headers in a SIP message like INVITE are mandatory and include Via, From, To, Call-ID and CSeq. The Via header contains information for routing responses. The From and To headers contain caller and callee identifiers. Call-ID provides a unique identifier for the call and CSeq contains the request sequence number and method.

    Original Description:

    SIP headers messages

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes SIP headers and SDP messages used in SIP signaling. It provides breakdowns of the key headers in a sample SIP INVITE message. The main headers in a SIP message like INVITE are mandatory and include Via, From, To, Call-ID and CSeq. The Via header contains information for routing responses. The From and To headers contain caller and callee identifiers. Call-ID provides a unique identifier for the call and CSeq contains the request sequence number and method.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    263 views22 pages

    SIP Headers

    Uploaded by

    Bikash Dash
    The document describes SIP headers and SDP messages used in SIP signaling. It provides breakdowns of the key headers in a sample SIP INVITE message. The main headers in a SIP message like INVITE are mandatory and include Via, From, To, Call-ID and CSeq. The Via header contains information for routing responses. The From and To headers contain caller and callee identifiers. Call-ID provides a unique identifier for the call and CSeq contains the request sequence number and method.

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 22
    At a glance
    Powered by AI
    The document discusses SIP (Session Initiation Protocol) headers and messages, including the INVITE method, components of SIP INVITE messages like Via, From, To, etc. and breakdown of SDP (Session Description Protocol) portions. It also provides examples of SIP INVITE messages.

    The main components of a SIP INVITE message are the Via, From, To, Contact, Call-ID, CSeq, User-Agent, Allow, Content-Type, and Content-Length headers. The INVITE also contains request parameters like the request URI, request method, and message body.

    The SDP portion of a SIP message contains information like the protocol version (v=), owner/creator of session (o=), session name (s=), time session is active (t=), media connection information (c=), bandwidth information (b=), media attributes like codecs and formats (a=), and media description with port and transport protocol (m=).

    SIP Headers

    •Via contains the address at which the originator is expecting to receive responses to this request. Mandatory

    •To contains a display name and a SIP URI towards which the request was originally directed. Mandatory

    •Display names are described in RFC 2822

    •From also contains a display name and a SIP URI that indicate the originator of the request. The From also contains a tag parameter
    which is used for identification purposes. Mandatory

    •Call-ID contains a globally unique identifier for this call. Mandatory

    •CSeq or Command Sequence contains an integer and a method name. The CSeq number is incremented for each new request within a
    dialog and is a traditional sequence number. Mandatory

    •Contact contains a SIP URI that represents a direct route to the originator usually composed of a username at a fully qualified domain
    name (FQDN). While an FQDN is preferred, many end systems do not have registered domain names, so IP addresses are permitted.
    The Contact header field tells other elements where to send future requests.

    •Max-Forwards serves to limit the number of hops a request can make on the way to its destination. It consists of an integer that is
    decremented by one at each hop.

    •Content-Type contains a description of the message body. Mandatory

    •Content-Length contains an octet (byte) count of the message body.


    SDP Messages
    Session description

    v= (protocol version) Mandatory

    o= (owner/creator and session identifier). Mandatory

    s= (session name) Mandatory

    t= (time the session is active) Mandatory


    i=* (session information)
    u=* (URI of description)
    e=* (email address)
    p=* (phone number)
    c=* (connection information - not required if included in all media)
    b=* (bandwidth information)
    z=* (time zone adjustments)
    k=* (encryption key)
    a=* (zero or more session attribute lines)
    r=* (zero or more repeat times)Media description

    m= (media name and transport address) Mandatory


    i=* (media title)
    c=* (connection information - optional if included at session-level)
    b=* (bandwidth information)
    a=* (zero or more media attribute lines)
    Normal SIP Invite
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -
    Breakdown of the Invite Message – INVITE Request

    INVITE sip:01150259917040@67.135.76.4 SIP/2.0


    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE Called Number Destination (Qwest) IP
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT Signaling Address
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    Request Method
    Breakdown of the Invite Message – Via Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Signaling Port
    Date: Thu, 22 Dec 2005 18:38:28 GMT Number of the
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp Source IP Address
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101 Source IP Address
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    The Via Header is used for


    Via Header translation rules and Session
    Agent matches.
    This is a
    Mandatory
    Header
    Breakdown of the Invite Message – From Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    From Address
    Content-Type: application/sdp
    Content-Length: 268 This is used to make a
    v=0 Maps to the ISUP match in the Local-
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session Generic Name Policy.
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000 Maps to the ISUP
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000 Calling Party Number
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    From Header
    This is a
    Mandatory
    Header
    Breakdown of the Invite Message – To Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Destination Number
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Destination (Qwest)
    Content-Type: application/sdp
    Content-Length: 268 IP Signaling
    v=0
    Address
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    To Header
    This is a
    Mandatory
    Header
    Breakdown of the Invite Message – Contact Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp Contact Address
    Content-Length: 268

    v=0
    This is used to
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    send the reply
    c=IN IP4 69.7.163.154 back to the sender.
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    Contact Header
    Breakdown of the Invite Message – Call-ID Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154 Call-ID Header
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    This is a Mandatory
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    Header
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -
    Breakdown of the Invite Message – CSeq Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    Command Sequence
    Header
    This is a Mandatory
    Header
    Breakdown of the Invite Message – User-Agent Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    User-Agent
    Header
    Breakdown of the Invite Message – Date Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    Date
    Header
    Breakdown of the Invite Message – Allow Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -

    Allow
    Header
    Breakdown of the Invite Message – Content-Type Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000 Content-Type
    a=rtpmap:18 G729/8000
    Header
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - - This is a
    Mandatory
    Header
    Breakdown of the Invite Message – Content-Length Header
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268
    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000 Content-Length
    a=rtpmap:18 G729/8000
    Header
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -
    Breakdown of the Invite Message – SDP Messages
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0 This is the SDP
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    information within
    a=rtpmap:8 PCMA/8000 the Invite
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -
    Breakdown of the Invite Message – SDP Messages

    INVITE sip:01150259917040@67.135.76.4 SIP/2.0


    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Protocol Version Mandatory
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154 Owner Mandatory
    s=session Session Name Mandatory
    c=IN IP4 69.7.163.154 IP address for RTP
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101 Time the session is
    a=rtpmap:0 PCMU/8000 active Mandatory
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=fmtp:18 annexb=no - - - -
    Breakdown of the Invite Message – SDP Media Message
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268
    Port for m=Media Name
    v=0
    RTP
    o=root 14040 14040 IN IP4 69.7.163.154 Mandatory
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16 101 = Telephone Event
    a=fmtp:18 annexb=no - - - -
    18 = G.729
    8 = G.711 ALaw
    0 = G.711 MuLaw
    Breakdown of the Invite Message – SDP Media Attributes
    INVITE sip:01150259917040@67.135.76.4 SIP/2.0
    Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6
    From: "8069664170" <sip:8069664170@69.7.163.154>;tag=as42e2ecf6
    To: <sip:01150259917040@67.135.76.4>
    Contact: <sip:8069664170@69.7.163.154>
    Call-ID: 2485823e63b290b47c042f20764d990a@69.7.163.154
    CSeq: 102 INVITE
    User-Agent: MatrixSwitch
    Date: Thu, 22 Dec 2005 18:38:28 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
    Content-Type: application/sdp
    Content-Length: 268

    v=0
    o=root 14040 14040 IN IP4 69.7.163.154
    s=session
    c=IN IP4 69.7.163.154
    t=0 0
    m=audio 26784 RTP/AVP 0 8 18 101 Codecs
    a=rtpmap:0 PCMU/8000 18 = G.729
    a=rtpmap:8 PCMA/8000 8 = G.711 ALaw
    a=rtpmap:18 G729/8000 0 = G.711 MuLaw
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16 DTMF via RFC 2833 is shown as a
    Telephone Event (101) with values 0-16
    a=fmtp:18 annexb=no - - - -
    This is how G.729A (without silence
    suppression) is designated
    How does the SIP Invite Map to an IAM?
    INVITE sip:2127568000@67.130.192.6:5060 SIP/2.0 Called Number
    f:"Kevin Generic Name
    Hyden"<sip:6142591566@67.130.192.6:5060>;tag=6ac1e3a4aa1f4e549ab21ea
    ea153ed20
    m:<sip:0-c0a8c94b13c419202d5d@67.133.234.161:5060;transport=udp> Calling Party Number
    t:<sip:2127568000@67.130.192.6:5060>
    i:637cdd3676311d35ff614f78593a2e44-43ba8a9c@67.133.234.161
    CSeq:31810 INVITE
    v:SIP/2.0/UDP
    67.133.234.161:5060;branch=z9hG4bK1e891a7df195a14ccd9df344e4583880-0
    Max-Forwards:70
    Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIF
    Y
    c:application/sdp
    Remote-Party-ID: <sip:6142591566@192.168.201.23>;party=calling;id-
    type=subscriber;privacy=off
    Anonymity: uri DOES NOT MAP TO CHARGE
    Proxy-Require:privacy NUMBER (CGN)
    l:124

    v=0
    o=- 256000 25600000 IN IP4 67.133.234.141
    s=-
    c=IN IP4 67.133.234.141
    t=0 0
    m=audio 48744 RTP/AVP 0 8
    a=ptime:20
    Example of an Invite With Caller ID Blocked
    INVITE sip:2128507797@67.130.192.6:5060 SIP/2.0 Called Number
    f:Anonymous
    <sip:PrivateNumber@localhost1>;tag=38fb29dc743e09a87fa0f40ce1e92906 Generic Name
    t:<sip:2128507797@localhost2>
    i:3dd342b75e489191fc70a4d658ded835-43ba8cf2@67.133.234.161 No Calling Party Number will be
    CSeq:19718 INVITE present in the ISUP IAM
    v:SIP/2.0/UDP
    67.133.234.161:5060;branch=z9hG4bK844bec9bcb061c035deaefe92fe1007e-0
    Max-Forwards:70
    Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIFY
    c:application/sdp
    Remote-Party-ID: <sip:6099448955@192.168.201.25>;party=calling;id-
    type=subscriber;privacy=full
    P-Asserted-Identity: sip:6099448955@192.168.201.25
    DOES NOT MAP TO CHARGE
    Privacy: id; user
    NUMBER (CGN)
    Anonymity: uri
    Proxy-Require:privacy
    m:<sip:0-c0a8c94b13c419202d5d@67.133.234.161:5060;transport=udp>
    l:124

    v=0
    o=- 108600 10860000 IN IP4 67.133.234.140
    s=-
    c=IN IP4 67.133.234.140
    t=0 0
    m=audio 53016 RTP/AVP 0 8
    a=ptime:20
    Example of G.711
    INVITE sip:2125332600@67.130.192.6:5060 SIP/2.0
    f:"Kevin Hyden"<sip:6142591566@67.130.192.6:5060>;tag=f0af9415bfb610da4ba208f2cf39fe8e
    m:<sip:0-c0a8c94a13c419202d5d@67.133.234.161:5060;transport=udp>
    t:<sip:2125332600@67.130.192.6:5060>
    i:9a22036f405d74b3853c437f3f3a598f-43ba8745@67.133.234.161
    CSeq:45023 INVITE
    v:SIP/2.0/UDP 67.133.234.161:5060;branch=z9hG4bKcee1d96ac551c44bc1efe13065f6ff3a-0
    Max-Forwards:70
    Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIFY
    c:application/sdp
    Remote-Party-ID: <sip:6142591566@192.168.201.23>;party=calling;id-type=subscriber;privacy=off
    Anonymity: uri
    Proxy-Require:privacy
    l:124

    v=0
    o=- 132000 13200000 IN IP4 67.133.234.140
    s=-
    c=IN IP4 67.133.234.140
    t=0 0 G.711 a-Law (PCMU)
    m=audio 40294 RTP/AVP 0 8
    a=ptime:20 G.711 Mu-Law (PCMU)

    Packet Size (this not codec dependent)


    Note that the Packet Size is not always specified,
    and is defaulted to 20ms unless otherwise noted.

    You might also like