1 / 4

Peer-to-Peer 3rd party call control

This proposal suggests a distributed control model for Peer-to-Peer 3rd Party Call Control, aiming to replace the centralized control model. By parsing SIP URIs with method parameters and headers, support REFER, and use REFER-To URLs with method parameters, this solution enables improved call control and status retrieval. Potential next steps include defining SIP-Status events, selecting an appropriate method (REFER, PHONECTL, or new), determining an authentication model, and ensuring compatibility with the call control framework.

pzimmerman
Download Presentation

Peer-to-Peer 3rd party call control

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. Peer-to-Peer 3rd party call control Rohan Mahy—Cisco Systems rohan@cisco.com

  2. Peer to peer 3pcc — Problem Set • Current 3pcc reproduces centralized control model of xGCP or PSTN (but needed for SIP interworking with H.323, RTSP, HTTP, etc.) • Make 3pcc distributed • Softphone directs my phone to dial, etc. • Use request vs. control model • Get status via notifications

  3. Peer-to-peer 3pcc — Proposal • If you can parse SIP URIs with method parameters and headers (needed for VoiceXML, etc.) and... • If you support REFER, turns out you have everything you need for “control” • Use Refer-To URLs with method parameter • SUBSCRIBE/NOTIFY is a reasonable way to get status

  4. Next steps • Come up with SIP-Status event • Choose REFER, PHONECTL, or some new method • Choose authentication model • Does this fit in call control framework?

More Related