1 / 6

BINDing URIs to SIP AORs

BINDing URIs to SIP AORs. Henning Schulzrinne Columbia University. Summary. Information and actions associated with AOR: scripts and call processing logic conference control (floor control, conference management) via non-SIP protocols upload presence user provisioning

yoko
Download Presentation

BINDing URIs to SIP AORs

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. BINDing URIs to SIP AORs Henning Schulzrinne Columbia University

  2. Summary • Information and actions associated with AOR: • scripts and call processing logic • conference control (floor control, conference management) via non-SIP protocols • upload presence • user provisioning • binding: SIP AOR  set of URIs • different degrees of indirection: • data URI • mid/cid URI • http, acap, ldap, ... URIs

  3. Binding vs. content indirection • Same: non-SIP URI references external data • content indirection: replace data carried in SIP body • binding: associate data with AOR

  4. Binding header field • Binding header field updates binding for particular purpose Binding: <http://www.tweak-me.com> ;disposition=configuration ;expires=0 ;q=0.1 Binding: <tftp://store.example.com> ;disposition=boot ;expires=36000 Binding: ;disposition=conference ;expires=0 • May be returned in by REGISTER, OPTIONS

  5. BIND method • REGISTER not appropriate to maintain bindings  multiple failure reasons, refresh intervals • Almost like REGISTER, but: • address to SIP URI  use methods parameter to direct to particular entity • handle both AOR and per-SIP URI bindings • ;expires=0  Delete all bindings for one disposition or individual URI • event package for updates

  6. Open issues • Is this useful in general? • For the applications envisioned? • Alternative: generalized PUBLISH • Details: • Status code "Maximum number of bindings exceeded"? • Tagged bindings for replacement?

More Related