Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Published byMarian Harrell Modified over 8 years ago

Similar presentations

Presentation on theme: "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."— Presentation transcript:

1 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

2 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)

3 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" ;tag=as42e2ecf6 To: Contact: 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 - - - -

4 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 - - - - Request Method Called Number Destination (Qwest) IP Signaling Address Breakdown of the Invite Message – INVITE Request

5 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – 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.

6 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – 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

7 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – To Header To Header This is a Mandatory Header Destination NumberDestination (Qwest) IP Signaling Address

8 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Contact Header Contact Header Contact Address This is used to send the reply back to the sender.

9 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Call-ID Header Call-ID Header This is a Mandatory Header

10 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – CSeq Header Command Sequence Header This is a Mandatory Header

11 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – User-Agent Header User-Agent Header

12 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Date Header Date Header

13 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Allow Header Allow Header

14 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Content-Type Header Content-Type Header This is a Mandatory Header

15 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – Content-Length Header Content-Length Header

16 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – SDP Messages This is the SDP information within the Invite

17 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – SDP Messages IP address for RTP Protocol Version Mandatory Owner Mandatory Session Name Mandatory Time the session is active Mandatory

18 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – SDP Media Message Port for RTP 101 = Telephone Event 18 = G.729 8 = G.711 ALaw 0 = G.711 MuLaw m=Media Name Mandatory

19 INVITE sip:01150259917040@67.135.76.4 SIP/2.0 Via: SIP/2.0/UDP 69.7.163.154:5060;branch=z9hG4bK400fc6e6 From: "8069664170" ;tag=as42e2ecf6 To: Contact: 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 – SDP Media Attributes DTMF via RFC 2833 is shown as a Telephone Event (101) with values 0-16 Codecs 18 = G.729 8 = G.711 ALaw 0 = G.711 MuLaw This is how G.729A (without silence suppression) is designated

20 How does the SIP Invite Map to an IAM? INVITE sip: 2127568000 @67.130.192.6:5060 SIP/2.0 f:" Kevin Hyden " ;tag=6ac1e3a4aa1f4e549ab21ea ea153ed20 m: t: 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: ;party=calling;id- type=subscriber;privacy=off Anonymity: uri Proxy-Require:privacy 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 Called Number Generic Name Calling Party Number DOES NOT MAP TO CHARGE NUMBER (CGN)

21 Example of an Invite With Caller ID Blocked INVITE sip:2128507797@67.130.192.6:5060 SIP/2.0 f:Anonymous ;tag=38fb29dc743e09a87fa0f40ce1e92906 t: i:3dd342b75e489191fc70a4d658ded835-43ba8cf2@67.133.234.161 CSeq:19718 INVITE 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: ;party=calling;id- type=subscriber;privacy=full P-Asserted-Identity: sip:6099448955@192.168.201.25 Privacy: id; user Anonymity: uri Proxy-Require:privacy m: 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 DOES NOT MAP TO CHARGE NUMBER (CGN) Called Number Generic Name No Calling Party Number will be present in the ISUP IAM

22 Example of G.711 INVITE sip:2125332600@67.130.192.6:5060 SIP/2.0 f:"Kevin Hyden" ;tag=f0af9415bfb610da4ba208f2cf39fe8e m: t: 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: ;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 m=audio 40294 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)

Download ppt "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."

Similar presentations

SIP(Session Initiation Protocol) - SIP Messages

SIP(Session Initiation Protocol) - SIP Messages
Multimedia Streaming Protocols. signalling and control protocols protocols conveying session setup information and VCR-like commands (play, pause, mute,

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.

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.

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.

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.

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.

Session Initiation Protocol Winelfred G. Pasamba.
Asterisk PBX: VoIP’s gateway to the future By Alex Ayala For Telecom class of 2003.

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 S2 2009.

Lecture 5 and 6 notes: Reji Mathew & Jian Zhang NICTA & CSE UNSW COMP9519 Multimedia Systems S
Session Initiation Protocol (SIP) By: Zhixin Chen.

Session Initiation Protocol (SIP) By: Zhixin Chen.
SIP/RTP/RTCP Implementation by George Fu, UCCS CS 525 Semester Project Fall 2006.

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.

VoIP Using SIP/RTP by George Fu, UCCS CS 522 Semester Project Fall 2004.
Application Layer Protocols For Real-Time Media Transmission

Application Layer Protocols For Real-Time Media Transmission
12/05/2000CS590F, Purdue University1 Sip Implementation Protocol Presented By: Sanjay Agrawal Sambhrama Mundkur.

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.

CSc 461/561 CSc 461/561 Multimedia Systems Part C: 2. SIP.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.

SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
An Introduction to SIP Moshe Sambol Services Research Lab November 18, 1998.

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.

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.

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.

Membership and Media Management in Centralized Multimedia Conferences based on Internet Engineering Task Force Protocol Building Blocks Author: Ritu Mittal.

Similar presentations

Ads by Google