30 likes | 85 Views
Document specific charter tasks, solve real problems with SIP, identify commonalities for reusable functionalities. Address PSTN, 3G applications, messaging, multi-party calls, and media servers. Develop guideline frameworks and requirements for SIP usage.
E N D
SIPPING Principles • Document requirements of specific charter tasks. • Document usage of SIP to solve real problems in a standardized way. • Look for commonalities among chartered tasks and ongoing SIP-related development; indicate need for general, reusable functionality in SIP. • For any needed extension, describe requirements and hand to SIP WG.
SIPPING Tasks (1 of 2) • 1. PSTN and/or 3G telephony-equivalent applications that need a standardized approach • informational guide to common call flows • support for T.38 fax • requirements from 3GPP for SIP usage • framework of SIP for telephony (SIP-T) • call transfer and call forwarding • AAA application in SIP telephony • mapping between SIP and ISUP • 2. Messaging-like applications of SIP - • support for hearing-/speech-impaired calling • development of usage guidelines for subscribe-notify (RFC 2848, SIP events) to ensure commonality among applications using them, including SIMPLE WG's instant messaging.
SIPPING Tasks (2 of 2) • 3. Multi-party applications of SIP • Review a number of technical pieces including: • call transfer • subscribe-notify • SIP features negotiation • SDP capability negotiation • Develop requirements and initial design/ framework for multi-party conferencing with SIP. • 4. SIP calling to media servers • Develop requirements draft for approach to SIP interaction with media servers. An example: is voicemail server just a box that a caller can send an INVITE to?