1 / 5

Enhancing Session Priority Control in SIP

This document discusses prioritizing sessions in SIP to manage competition for resources, focusing on telephony gateways. It outlines changes, error behaviors, and open issues related to resource priority. The aim is to optimize call completion.

bgaston
Download Presentation

Enhancing Session Priority Control in SIP

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. SIP Resource Priority James Polk/Cisco Henning Schulzrinne/Columbia University 53rd IETF -- SIPPING

  2. Resource-Priority Header • Goal: • establish preferential (or deferential...) treatment for sessions when competing for destination UA resources • typically telephony gateways (not necessarily PSTN) • usually MLP, but could be gateway resources only • cf. SIP Priority header: influence treatment by human user 53rd IETF -- SIPPING

  3. Changes since last time • Namespace.priority • e.g., dsn.flash,q735.0 • IANA registration procedure • Clearer definition of default behavior • overall goal: maximize call completion • Resource-Priority expected, but none • policy issue, recommend treat at default level • recipient doesn’t understand name space • policy issue, recommend ignore and treat as if no Resource-Priority header • recipient doesn’t understand priority level 53rd IETF -- SIPPING

  4. Error behavior • 503 (Service Unavailable) if insufficient priority • Warning: 370 (Insufficient Bandwidth) • Open issue: separate codes? 53rd IETF -- SIPPING

  5. Open issues • All comments integrated – new I-D after IETF53 • Minor issue: Accept-Resource-Priority? • Otherwise considered done • Authors request hand-off to SIP (since new header) for PS track 53rd IETF -- SIPPING

More Related