The document discusses Session Initiation Protocol (SIP) which is used to establish multimedia sessions over IP networks. It has a client-server architecture and uses requests and responses to manage transactions in a peer-to-peer manner. SIP messages can carry different payloads like SDP, ISUP, emails or pictures. The key functional blocks of SIP are user location, availability, capabilities and session setup. Architectural elements include proxies, redirects, registrars and user agents. SIP has a simple text-based format like HTTP and allows for flexible headers and reconfiguration of media during a session.
The document discusses Session Initiation Protocol (SIP) which is used to establish multimedia sessions over IP networks. It has a client-server architecture and uses requests and responses to manage transactions in a peer-to-peer manner. SIP messages can carry different payloads like SDP, ISUP, emails or pictures. The key functional blocks of SIP are user location, availability, capabilities and session setup. Architectural elements include proxies, redirects, registrars and user agents. SIP has a simple text-based format like HTTP and allows for flexible headers and reconfiguration of media during a session.
The document discusses Session Initiation Protocol (SIP) which is used to establish multimedia sessions over IP networks. It has a client-server architecture and uses requests and responses to manage transactions in a peer-to-peer manner. SIP messages can carry different payloads like SDP, ISUP, emails or pictures. The key functional blocks of SIP are user location, availability, capabilities and session setup. Architectural elements include proxies, redirects, registrars and user agents. SIP has a simple text-based format like HTTP and allows for flexible headers and reconfiguration of media during a session.
The document discusses Session Initiation Protocol (SIP) which is used to establish multimedia sessions over IP networks. It has a client-server architecture and uses requests and responses to manage transactions in a peer-to-peer manner. SIP messages can carry different payloads like SDP, ISUP, emails or pictures. The key functional blocks of SIP are user location, availability, capabilities and session setup. Architectural elements include proxies, redirects, registrars and user agents. SIP has a simple text-based format like HTTP and allows for flexible headers and reconfiguration of media during a session.
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
You are on page 1/ 6
SIP and SDP Overview
SIP OVERVIEW SIP FUNCTIONAL BLOCKS SIP ARCHITECTURAL ELEMENTS SIP BASICS SIP DIALOGUES SIP DIALOGUES, RTP SEGMENT SESSION BETWEEN A 4G AND FIXED MOBILE SUBSCRIBER SESSION BETWEEN TWO 4G SUBSCRIBER SESSION SETUP & RELEASE SIP REQUEST FORMAT SIP REQUEST LAYOUT SIP HEADER STANDARD SIP REQUEST SIP RESPONSE LAYOUT STANDARD SIP RESPONSES CATEGORIES SIP Overview
SIP- Session Initiation Protocol
Establishing of multimedia sessions in IP networks SIP is a peer-to-peer protocol SIP has a client/server architecture Transaction based (requests & responses) IETF signaling protocol RFC2543,RFC3261 SIP messages may carry different contents (SDP,ISUP,E-Mail, Picture) SIP Functional Blocks User Location: It determines the address (IP address) of the end-point of SIP session User Location between two SIP terminal / users. User Availability User Availability: Once the end system is User Capability invited for the session, its willingness of availability to participate the session must be Session Setup checked. SIP User Capability: If two or more end systems are found that will establish the session, the TLS associated media type and bearer parameters SCT must be negotiated UDP TCP TCP P IP IP IP IP Session Setup: This includes “ringing” and establishment of the session between the end systems. SIP ARCHITECTURAL ELEMENTS Proxy Server (Proxy):- act as server & client, represent the original client, • Its main task is routing of request towards final destination.
Redirect Server:- sends responses for client’s requests, which inform the client to • send the request again but to another server entity.
Registrar:- a permanent /transient data base, user agent can register its current • address for reachability here.
User Agent:-combine UAC which sends request and UAS which accepts, rejects, • requests, typically a user agent is a software for the end user terminal.
Back-to-Back User Agent:- consists of two user agents working back-to-back. It
• control the calls going through it. SIP BASICS
Application layer control protocol
HTTP like transaction model User Agent Client request User Agent Server Syntax: start-line/header/[body] Private header->flexible Coded as text string->easy to read Independent from the media description protocol Reconfiguration of media stream possible-> first audio , then video SIP Basics
