RFC 3261 - New Services

Customized ringing
- A trusted proxy can insert an Alert-Info header field into an INVITE
Screen Pops
- A trusted proxy can insert an Call-Info header field into an INVITE
- URI can be HTTP and can contain call control “soft keys”
Callback
- Reply-to and In-Reply-To header - to assist in returning calls
Announcement handling
- UAS or proxy need not make a decision about playing an early media announcement ⇒ Error response contains new Error-Info header field which contains the URI of the announcement
- UAC makes a decision based on the user’s interface

Slide Notes

J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, Sparks, M. Handley, and E. Schooler,”SIP: Session Initiation Protocol”, IETF, Network Working Group, RFC 3261, June 2002, Updated by RFC 3265, RFC 3853, RFC 4320, RFC 4916, RFC 5393, RFC 5621, RFC 5626, RFC 5630, RFC 5922, http://datatracker.ietf.org/doc/rfc3261/ Links to an external site.

Transcript

[slide168] We can do customized ring signals where, you know, if your friend calls you, you can have a ring signal associated with them or have screen popups. Or we can do automatic callbacks. And we can do various sorts of things about announcements.