1 / 5

Straw Man Proposal for SIP Media Traceroute Function

This straw-man proposal outlines a media-based traceroute function for SIP, addressing challenges in troubleshooting poor media calls, particularly during emergency calls. Traditional traceroute methods in IP cannot be seamlessly applied to SIP media sessions. The proposal introduces a new header, 'B2bua-hops', to track the media path through B2BUAs. This header allows for decrementing hops while providing useful information when it reaches zero. Open questions remain about implementation details and stakeholder interest, presenting an opportunity for discussion on potential next steps.

vance
Télécharger la présentation

Straw Man Proposal for SIP Media Traceroute Function

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. A straw-man proposal for amedia-based traceroutefunction for SIP draft-kaplan-straw-sip-traceroute-00 Hadriel Kaplan

  2. The Problem(s) How do we find out this is the problem? App Server PBX PBX • Troubleshooting failed or poor media calls is difficult • If you call a 911/112 test number and media is bad, what do you do next? • In IP, people start running traceroute • It would be nice to have the same for SIP media sessions Alice Bob

  3. Can’t we use Max-Forwards? • Kinda sorta but not really • Problem-1: Max-Forwards gets reset by B2BUAs • Trying to address that in another straw draft • Problem-2: Even if Max-Forwards works, the reached hop will respond with 483 error • Not what we want – we want it to answer the call

  4. The Proposed Solution App Server B2bua-hops:2 PBX PBX • A new header (surprise!) • ‘B2bua-hops: 70’ • Like Max-Forwards, this header gets decremented by middleboxes • but only media-plane B2BUAs • When it reaches 0, the B2BUA answers it • Or responds with 483 if it can’t answer it, with Contact-URI Answers B2bua-hops:1 B2bua-hops:0 Alice Bob

  5. Open Issues • Lots of open issues – this is just a straw-man proposal after all • But the big question right now: is anyone interested in this type of thing? • Should we use a new header, or something in SDP?

More Related