- An application layer control protocol (works with both IPv4 and IPv6), that can
- establish modify and terminate multimedia sessions (conferences), such as IP telephony calls
- invite participants to existing sessions (like multicast conferences)
- existing sessions can be modified by adding/removing media from an existing session
- transparently supports name mapping and redirection services (support to personal mobility)
- a single externally visible ID can be maintained regardless of the network location (SIP URI)
- establish modify and terminate multimedia sessions (conferences), such as IP telephony calls
- creation and management of session between internet endpoints, some of the things involves in doing so are
- discovering one another (using proxy servers)
- registering on the network (to be visible to others)
- agreeing on parameters of the session
- discovering one another (using proxy servers)
- SIP supports five facets of establishing and terminating multimedia communications
- location of user (end system to be used for communication)
- availability of user (willingness of the called party, to engage in communication)
- capabilities of user (media and media parameters)
- session setup (ringing, establishment of session parameters)
- session management (transfer/termination of sessions, modifying session parameters, and invoking services)
- location of user (end system to be used for communication)
- needs other protocols to provide the service providing a complete multimedia architecture, some of them are
- SDP (Session Description Protocol)
- RTP (Real-time Transport Protocol), RTCP (Real-time Transport Control Protocol), RTSP (Real Time Streaming Protocol)
- MEGACO (Media Gateway Control Protocol)
- SDP (Session Description Protocol)
- security services provided by SIP
- denial-of-service prevention
- authentication
- integrity protection
- encryption and privacy services
- denial-of-service prevention
- What SIP does not offer
- No services, but primitives to be used and implement different services
- No conference control services (like floor control and voting)
- No Network Resource Reservation (as SIP messages and sessions can pass through entirely different networks)
- No services, but primitives to be used and implement different services
Tuesday, September 14, 2010
SIP Overview
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment