1 / 5

SIP Proxy-Supported Extension: Enabling Capabilities Query in SIP Requests

This draft proposes a SIP extension for User Agents to query record-routing proxy servers' capabilities in INITIAL requests. The subsequent requests can use these capabilities for call leg selection, error handling, and session establishment strategy. Contrasting Proxy-Supported with Proxy-Require, it ensures seamless session continuation even if some proxies lack support. The draft discusses challenges, potential use cases, and suggests a simpler technical solution for wider applicability.

cherylturner
Download Presentation

SIP Proxy-Supported Extension: Enabling Capabilities Query in SIP Requests

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. draft-hoeneisen-sip-proxy-supported-00 Table of Contents: • Motivation of Proxy-Supported • Differences Proxy-Supported vs. Proxy-Require • Issues • Questions and discussion

  2. Motivation of Proxy-Supported • Define a SIP extension that allows UAs to queryin an INITIAL request the capabilities of all record-routing proxy servers. • The (proxy-)supported capabilities can then be used in SUBSEQUENT requests. These include: • New methods that require special handling in proxy servers • Selecting a suitable call leg after (parallel) forking • No error responses when a capability is not supported; session establishment can continue undisturbed. Note: This proposal assumes Route header specifies strict source routing.

  3. Differences to Proxy-Require Using Proxy-Supported… ...a request goes through even if any of the intermediate proxy servers doesn't support an indicated extension, whereas Proxy-Require results in a 420 error response in the proxy server. ...only Record-Routing proxy servers are queried, whereas Proxy-Require concerns all proxy servers in a signalling path. …the features are used only in subsequent requests, whereas features in Proxy-Require can be used also in the first request.

  4. Issues From the SIP mailing list: • Concerns, that onlyfew features can be negotiated with Proxy-Supported, as most need support in the initial request. • Are there further use cases? • A more generic solution, which also allows UAs to query, whether at least one proxy server supports a certain feature, might be considered as well. • Technical solution could be somewhat simpler • More?

  5. Questions and Discussion • Is there a general interest for this proposal? • How to continue? • Additional comments to the technical solution? Thank you!

More Related