1 / 4

Design challenges in alerting (a personal view) Dale Worley (as individual) IETF 78 Maastricht

Design challenges in alerting (a personal view) Dale Worley (as individual) IETF 78 Maastricht. Purpose is to provide way of specifying ring tones to be presented to callee and ringback tones to be provided to caller. These will be specified by URN values in the Alert-Info header.

zeal
Download Presentation

Design challenges in alerting (a personal view) Dale Worley (as individual) IETF 78 Maastricht

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design challenges in alerting(a personal view)Dale Worley(as individual)IETF 78 Maastricht

  2. Purpose is to provide way of specifying ring tones to be presented to callee and ringback tones to be provided to caller. These will be specified by URN values in the Alert-Info header. • Many non-SIP systems (especially PBXs) provide a variety of ring/ringback tones to tell caller/callee the circumstances of the call (outside call, inside call, call waiting has been invoked, etc.) • Purpose is to provide way of specifying ring tones to be presented • to callee and ringback tones to be provided to caller. These will • be specified by URN values in the Alert-Info header. • Purpose is to provide way of specifying ring tones to be presented • to callee and ringback tones to be provided to caller. These will • be specified by URN values in the Alert-Info header.

  3. Current systems work entirely based on the rendering (short tone, long tone, fast tone, etc.), but we want to create "semantic" ring/ringtone indicators so interoperation can be based on ring tone meaning and to allow rendering in multiple modalities (e.g., visual indicators for the hearing impaired). • Different systems use somewhat compatible sets of ring tone meanings -- The goal is to provide "nearly best" approximations when interoperating. • Purpose is to provide way of specifying ring tones to be presented • to callee and ringback tones to be provided to caller. These will • be specified by URN values in the Alert-Info header. • Purpose is to provide way of specifying ring tones to be presented • to callee and ringback tones to be provided to caller. These will • be specified by URN values in the Alert-Info header.

  4. Need to provide extensibility in almost all aspects of the specification so that usage within one system can carry all of the existing ring tone information (which may include "proprietary" aspects that we aren't standardizing). • The current work is organized around specifying values for multiple "dimensions" desired for the rendering. Values for several dimensions are used to select a best-fit rendering. Most dimensions are orthogonal, but some are incompatible with others. The set of dimensions and the set of values within each dimension must be extensible.

More Related