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.

Slides:



Advertisements
Similar presentations
SIP(Session Initiation Protocol) - SIP Messages
Advertisements

Multimedia Streaming Protocols. signalling and control protocols protocols conveying session setup information and VCR-like commands (play, pause, mute,
NAT Traversal Panasonic Communications Co.,Ltd Office Network Company Network SE Team 2008 Feb 25 th.
Signaling: SIP SIP is one of Many ITU H.323 Originally for video conferencing The first standard protocol for VoIP Still in wide usage, but negative.
Copyright 2005 – 2008 © by Elliot Eichen. All rights reserved. SIP: Session Initiation Protocol.
1 School of Computing Science Simon Fraser University CMPT 820: Multimedia Systems Network Protocols for Multimedia Applications Instructor: Dr. Mohamed.
Session Initiation Protocol Winelfred G. Pasamba.
Asterisk PBX: VoIP’s gateway to the future By Alex Ayala For Telecom class of 2003.
Lecture 5 and 6 notes: Reji Mathew & Jian Zhang NICTA & CSE UNSW COMP9519 Multimedia Systems S
Session Initiation Protocol (SIP) By: Zhixin Chen.
SIP/RTP/RTCP Implementation by George Fu, UCCS CS 525 Semester Project Fall 2006.
VoIP Using SIP/RTP by George Fu, UCCS CS 522 Semester Project Fall 2004.
Application Layer Protocols For Real-Time Media Transmission
12/05/2000CS590F, Purdue University1 Sip Implementation Protocol Presented By: Sanjay Agrawal Sambhrama Mundkur.
CSc 461/561 CSc 461/561 Multimedia Systems Part C: 2. SIP.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
An Introduction to SIP Moshe Sambol Services Research Lab November 18, 1998.
SIP 逄愛君 SIP&SDP2 Industrial Technology Research Institute Computer & Communication Research Laboratories Elgin Pang Outline.
Introduction to SIP Speaker: Min-Hua Yang Advisor: Ho-Ting Wu Date:2005/3/29.
Membership and Media Management in Centralized Multimedia Conferences based on Internet Engineering Task Force Protocol Building Blocks Author: Ritu Mittal.
AARNet Copyright 2011 Network Operations SDP Deep Dive Bill Efthimiou APAN33 SIP workshop February 2012.
Session Initialization Protocol (SIP) Presented by: Aishwarya Gurazada CISC856: TCP/IP and upper layer protocols May 5 th 2011 Some slides borrowed from.
SIP Session Initiation Protocol Short Introduction Artur Hecker, ENST.
Thomas Lee Chief Architect Global Knowledge EMEA UNC404.
Session Initiation Protocol (SIP) Ram Dantu (Compiled from different sources, see the references list)
LOGO Yeastar Technology Co., Ltd. Enterprise Communication.
SIP South Carolina Cisco User Group Martin Jefferson IE UC Practice Manager.
Developing A Sip User Agent Using The Jain Sip Stack. Robert.V Masango Supervisors: Alfredo Terzoli, Ming Hsieh.
Session Initiation Protocol Team Members: Manjiri Ayyar Pallavi Murudkar Sriusha Kottalanka Vamsi Ambati Girish Satya LeeAnn Tam.
1 © 2004, Cisco Systems, Inc. All rights reserved. VVT-A01 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public SIP Location Conveyance draft-ietf-sip-location-conveyance-04.txt.
NAT Traversal Speaker: Chin-Chang Chang Date:
1 Kommunikatsiooniteenuste arendus IRT0080 Loeng 8 Avo Ots telekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.
1 Kommunikatsiooniteenuste arendus IRT0080 Loeng 4 Avo Ots telekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.
Np160 Dennis Baron, January 15, 2008 Page 1 SIP Fundimentals IAP 2008 VoIP Series Dennis Baron January 15, 2008.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
Improving the Routing Efficiency of SIP Instant Message SIP 即時傳訊之繞送效能研究 adviser : Quincy Wu speaker : Wenping Zhang date :
Gonzalo Camarillo Advanced Signalling Research Lab 48th IETF MMUSIC WG Gonzalo Camarillo draft-camarillo-sip-sdp-00.txt.
Presented By Team Netgeeks SIP Session Initiation Protocol.
Team Members Atcharawan Jansprasert Padmoja Roy Rana Almakabi Ehsan Eslamlouevan Manya Tarawalie.
SIP, SDP and VoIP David A. Bryan CSCI 434/534 December 6, 2003.
Elin Sundby Boysen Lars Strand Norwegian Defence Research Establishment (FFI) Norwegian Computing Center (NR) University Graduate Center (UNIK) November.
1 Outline Introduction to IPv6 Enabling SER with IPv6 Concept of SIP Mobility UA with SIP Mobility Support Conclusion and Future Work.
Quiz Problem – Draw Ladder Diag. INVITE SIP/ :19: INFO SIP ::send_sip_udp Send to: udp: :5060.
SIP:Session Initiation Protocol Che-Yu Kuo Computer & Information Science Department University of Delaware May 11, 2010 CISC 856: TCP/IP and Upper Layer.
VoIP Signaling Protocols A signaling protocol is a common language spoken by telephones and call-management servers, the PSTN, and legacy PBX systems as.
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
Summary: Internet Multimedia: bag of tricks r use UDP to avoid TCP congestion control (delays) for time-sensitive traffic r client-side adaptive playout.
SIP Security Issues : The SIP Authentication Procedure and its Processing Load Speaker: Lin-Yi Wu Advisor : Prof. Yi-Bing Lin Date : 2003/04/09.
SIP-SIP Video Delayed Offer-Delayed Offer
1 RFC4028 Session Timer in the Session Initiation Protocol Speaker : Ying Shun Lin Adviser : Quincy Wu.
Session Description Protocol
Slide #1 Nov 6 -11, 2005SIP WG IETF64 Feature Tags with SIP REFER draft-ietf-sip-refer-feature-param-00 Orit
1 Internet Telephony: Architecture and Protocols an IETF Perspective Authors:Henning Schulzrinne, Jonathan Rosenberg. Presenter: Sambhrama Mundkur.
The Session Initiation Protocol - SIP
1 SIPREC Protocol draft-portman-siprec-protocol Virtual interim meeting Dec 16, 2010 Authors: L. Portman, H. Lum.
S Postgraduate Course in Radio Communications. Application Layer Mobility in WLAN Antti Keurulainen,
Session-Independent Policies draft-ietf-sipping-session-indep-policy-00 Volker Hilt Gonzalo Camarillo
1 Personal Mobility Management for SIP-based VoIP Services 王讚彬 國立台中教育大學資訊工程學系
Configuring the SIP Application Filter Configuration Example Alcatel-Lucent Security Products Configuration Example Series.
7: Multimedia Networking7-1 protocols for real-time interactive applications RTP, RTCP, SIP.
The SIP-Based System Used in Connection with a Firewall Peter Koski, Jorma Ylinen, Pekka Loula Tampere University of Technology, Pori Pohjoisranta 11 A,
MSRP (The Message Session Relay Protocol) 姓名:張文萍 日期: 2007/04/02.
CS Spring 2014 CS 414 – Multimedia Systems Design Lecture 24 – Multimedia Session Protocols Klara Nahrstedt Spring 2014.
SIP AAI a possibility for TF-EMC2 and TF-ECS cooperation
SIP Fundimentals IAP 2008 VoIP Series Dennis Baron January 15, 2008.
Session Initiation Protocol
Session Initiation Protocol (SIP)
SIP ,SIP-T and SIP-I Protocol
Running SIP behind NAT Dr. Christian Stredicke, snom technology AG
SIP Basics Workshop Dennis Baron July 20, 2005.
Presentation transcript:

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 2822RFC 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. SIP Headers

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=* ( 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/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no

INVITE SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no Request Method Called Number Destination (Qwest) IP Signaling Address Breakdown of the Invite Message – INVITE Request

INVITE SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no Breakdown of the Invite Message – Via Header Via Header This is a Mandatory Header Source IP Address Signaling Port Number of the Source IP Address The Via Header is used for translation rules and Session Agent matches.

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

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

INVITE SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no Breakdown of the Invite Message – Contact Header Contact Header Contact Address This is used to send the reply back to the sender.

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

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

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

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

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

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

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

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

INVITE SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no Breakdown of the Invite Message – SDP Messages IP address for RTP Protocol Version Mandatory Owner Mandatory Session Name Mandatory Time the session is active Mandatory

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

INVITE SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK400fc6e6 From: " " ;tag=as42e2ecf6 To: Contact: Call-ID: CSeq: 102 INVITE User-Agent: MatrixSwitch Date: Thu, 22 Dec :38:28 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER Content-Type: application/sdp Content-Length: 268 v=0 o=root IN IP s=session c=IN IP t=0 0 m=audio RTP/AVP a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=fmtp: a=fmtp:18 annexb=no Breakdown of the Invite Message – SDP Media Attributes DTMF via RFC 2833 is shown as a Telephone Event (101) with values 0-16 Codecs 18 = G = G.711 ALaw 0 = G.711 MuLaw This is how G.729A (without silence suppression) is designated

How does the SIP Invite Map to an IAM? INVITE sip: SIP/2.0 f:" Kevin Hyden " ;tag=6ac1e3a4aa1f4e549ab21ea ea153ed20 m: t: CSeq:31810 INVITE v:SIP/2.0/UDP :5060;branch=z9hG4bK1e891a7df195a14ccd9df344e Max-Forwards:70 Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIF Y c:application/sdp Remote-Party-ID: ;party=calling;id- type=subscriber;privacy=off Anonymity: uri Proxy-Require:privacy l:124 v=0 o= IN IP s=- c=IN IP t=0 0 m=audio RTP/AVP 0 8 a=ptime:20 Called Number Generic Name Calling Party Number DOES NOT MAP TO CHARGE NUMBER (CGN)

Example of an Invite With Caller ID Blocked INVITE SIP/2.0 f:Anonymous ;tag=38fb29dc743e09a87fa0f40ce1e92906 t: CSeq:19718 INVITE v:SIP/2.0/UDP :5060;branch=z9hG4bK844bec9bcb061c035deaefe92fe1007e-0 Max-Forwards:70 Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIFY c:application/sdp Remote-Party-ID: ;party=calling;id- type=subscriber;privacy=full P-Asserted-Identity: Privacy: id; user Anonymity: uri Proxy-Require:privacy m: l:124 v=0 o= IN IP s=- c=IN IP t=0 0 m=audio RTP/AVP 0 8 a=ptime:20 DOES NOT MAP TO CHARGE NUMBER (CGN) Called Number Generic Name No Calling Party Number will be present in the ISUP IAM

Example of G.711 INVITE SIP/2.0 f:"Kevin Hyden" ;tag=f0af9415bfb610da4ba208f2cf39fe8e m: t: CSeq:45023 INVITE v:SIP/2.0/UDP :5060;branch=z9hG4bKcee1d96ac551c44bc1efe13065f6ff3a-0 Max-Forwards:70 Allow:INVITE,BYE,ACK,CANCEL,PRACK,REFER,OPTIONS,REGISTER,NOTIFY c:application/sdp Remote-Party-ID: ;party=calling;id-type=subscriber;privacy=off Anonymity: uri Proxy-Require:privacy l:124 v=0 o= IN IP s=- c=IN IP t=0 0 m=audio RTP/AVP 0 8 a=ptime: 20 Packet Size (this not codec dependent) Note that the Packet Size is not always specified, and is defaulted to 20ms unless otherwise noted. G.711 Mu-Law (PCMU) G.711 a-Law (PCMU)