1 / 9

What would it take to overthrow the PSTN using SIP?

What would it take to overthrow the PSTN using SIP?. Dayton Turner ClueCon 2013. Objectives. Reduce (or eliminate!) the dependency on the PSTN Establish de-centralized routing database / phone book Increase functionality and flexibility of current routing mechanisms

petra
Télécharger la présentation

What would it take to overthrow the PSTN using 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. What would it take to overthrow the PSTN using SIP? Dayton Turner ClueCon 2013

  2. Objectives • Reduce (or eliminate!) the dependency on the PSTN • Establish de-centralized routing database / phone book • Increase functionality and flexibility of current routing mechanisms • Get the conversation started

  3. Similar systems • ENUM • Centralized • Requires explicit verification per DID • Simply provides raw SIP URI • DUNDi • Asterisk only • BGP • Operates on same basic principles of peers and trust

  4. What is necessary? • Identify areas where other systems failed to reach mass adoption • Define secure peering mechanism • Protocol for data exchange • Build ready-to-go implementation

  5. Ideas • Service broadcast (like Bonjour) • Peer to peer neighbor learning • Inbound DID directory • White/Yellow page replacement • Outbound routing possibilities

  6. More ideas • Health monitoring between sites • Potentially offer alternate media routing paths that were designed for voice • Allow for advanced routing criteria (avoid known un-trusted networks) • ?????

  7. Concerns • Security is huge • Need network operators to experiment and test • Privacy in an open directory?! • Love to hear your concerns and ideas!

  8. Where do we start? • Discussion • ClueCon, mailing list • We are starting work using Kazoo • Building with API abstraction in mind for connecting to arbitrary data stores

  9. More information? • theMesh.io Thank you! (I'll be here all week)

More Related