1 / 18

VeriSign IP Connect Connecting communities of interest

VeriSign IP Connect Connecting communities of interest . Internet Telephony Conference (VP-02 and VP-03 Sessions) Sean Kent – Product Manager Email: skent@verisign.com Tel: (703)346-9907. Agenda . Technical Issues of VoIP Peering (VP-02) Thursday 01/26/06 12:30-1:15PM

alohilani
Download Presentation

VeriSign IP Connect Connecting communities of interest

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. VeriSign IP Connect Connecting communities of interest Internet Telephony Conference (VP-02 and VP-03 Sessions) Sean Kent – Product Manager Email: skent@verisign.com Tel: (703)346-9907

  2. Agenda Technical Issues of VoIP Peering (VP-02) Thursday 01/26/06 12:30-1:15PM VoIP Peering Business Case Studies (VP-03) Thursday 01/26/06 1:30-3:15PM

  3. Directory Connectivity Security Mediation VeriSign Know-How Long history of proving peering services • Recent acquisitions inter-carrier mobile messaging Inter-carrier short messaging (SMS) experience • Taught mobile operators it pays to cooperate • VeriSign practiced in core components of peering VoIP peering products (IP Connect) launched Fall’04 • Peering across broadband, cellular and enterprise networks Integration of company assets “One VeriSign” initiative • Dot-com/-net DNS registry platform • SS7 network and databases • Inter-carrier roaming and messaging

  4. Lessons Learned Security • Most security appliances (B/SC) do not scale down to enterprise • Very few support encryption (TLS and SRTP) Directory • Many carriers’ own intra-community VoIP traffic traverses PSTN!!! • Should leverage existing number management systems • Not as simple as storing telephone number and associated URL Mediation • End to end IP calls often do not trigger PSTN databases • Poor interoperability across enterprise Connectivity • Poor quality unacceptable for cheap dial tone • ISP-CLEC peering in co-location centers

  5. Intra-Community Centralized Policy Server Central repository of subscription and topology information • Regulates operating costs (scales operations, enables forced on-net) Combination of ENUM and IMS specifications • Number block/pool route selection (destination, origination, time, cost) • Subscription discovery, one or more service URIs per user • Callout (service trigger) to PSTN/PLMN databases Centralized Routing Directory PSTN Databases CNAM LNP HLR PSTN/PLMN Call Agent/ Softswitch Trunk Gateway Application Server • PSTN Breakout Gateway/Border Element Selection • Intra-Community Service and Location Discovery • Trigger SIP/ENUM reachable PSTN Databases

  6. 1 3 5 6 4 2 Inter-Community TN2URL Mapping Tier 1 (common directory) resolves number ownership • Industry data sources (number pools and portability) • Service provider supplied “Authoritative List” (overrides industry data) • TN to SPid or TN to NS Record (Tier 2 ENUM Server) LERG and NPAC TN to SPid industry data “Authoritative List” manually entry or bulk upload via portal Tier 1 ENUM Server Service Provider A Service Provider B Tier 2 discovery (SPid or NS record) Tier 2 ENUM Server Tier 2 ENUM Server Service and location discovery (NAPTR record) Border Element IP Peering Exchanges Call Agent Call Agent Border Element

  7. DATA PARTITION Data Partitioning Peering managed by way of data types • Classification specifies level of sharing Data classifications • Private – visible only to enterprise/service provider (intra-domain) • Restricted – visible to “closed user group” of peers (restricted inter-domain) • Federated – visible to all publishing to directory (unrestricted inter-domain) Peering entities may query one another’s topology data but may not view one another’s data via portal Secure Self-Management Portal - Upload service provider’s dial plan or enterprise’s corporate directory - Optionally establish closed user group of peers or opt all-in peering with all Peers

  8. Inter-Enterprise Enterprise Peering Introduction of inter-working equipment on customer premises • Security and interoperability across major equipment vendors Self-Management Portal - Publication of corporate directory - Management of peering enterprises Signaling encryption (TLS) Authentication (HTTP Digest) Private dial plan Telephone # to URL address resolution Fault tolerant routing and load balancing Enterprise A (Site 1) Routing Directory Intra-Enterprise Security • Application level NAT (topology hiding) • Signaling encryption (TLS) Interoperability • Legacy PBXs • H.323 inter-working w/ SIP • Vendor variants Enterprise B Enterprise A (Site 2)

  9. Agenda Technical Issues of VoIP Peering (VP-02) Thursday 01/26/06 12:30-1:15PM VoIP Peering Business Case Studies (VP-03) Thursday 01/26/06 1:30-3:15PM

  10. State of VoIP Peering Market PSTN replacement slow not explosive growth • Forced on-net weak VoIP community still small International termination loosing steam • Toll bypass marginalized thru price erosion Local and fixed-mobile convergence gaining momentum • Cheap dial-tone bundled local and long distance • International demand for country code “1” telephone numbers • Domestic and international roaming bypass (dual mode roam to Wi-Fi) The players • CLECs altering business model to include wholesale VoIP • ISPs marketing telephony services to subscriber base • Portals with advertisement revenue model add voice to grow user base

  11. Positioning In-network value proposition enhances CLEC or IPX service • PSTN bound calls forced on-net between customers • Value increases as size of community grows (# of telephone numbers) Addition of voice to enterprise extranets • Sharing of corporate dial plans • Exchange rich media (voice, video, presence & IM) within supply chain Disaster recovery services • Automatic or manual switch to backup site • Target market include financial institutions Bundle w/ other managed services • Integration w/ IN Databases (Calling Name…) • Fixed-mobile convergence (SMS, MMS, cellular roaming clearing/settlement…)

  12. VoIP Peering Ecosystem Partner • Internet Peering Exchange (QoS-enabled Interconnect) VeriSign • Registry Services (Topology Publication) • Security Services (Topology Hiding) • Interoperability (Protocol and Vendor Variants) Customers • Service Provider (ISPs…) • Enterprise verticals (financial institutions…)

  13. In Network Value Proposition Mobile network operators successful “In-Network Calling” rate plans • Inexpensive “sticky” method of attracting and keeping customers Private peering solution • Allows CLEC or IPX to establish club of peering customers • Force off-net calls on-net and save customer added expense of PSTN Network Routing Directory Web Portal (self-management - manual entry or bulk upload) Member opts into the managed peering “club”, publishing their address space to all members or a sub-set of members Broadband Telephony User Communities Voice (RTP) Traffic Private IP Peering Exchange

  14. IP Enabling Trader Voice Networks Trader systems interconnect w/ resilient Session Initiation Protocol (SIP) • Ring down/hotline dial plan • Sites connected over redundant IP backbone Near real-time MAC and improved reliability (disaster recovery) • Calls switched seamlessly between TDM (Turrets) and IP (transport) • Simultaneous or sequential ring down Redirect Server[1] (Network Routing Directory) Telephone Number to URI Mapping Primary Site Proxy Server[1] (SIP Forking) Simultaneous Ring (Primary/Backup) Turrets Egress Ingress Primary Gateway Disaster Recovery Site Voice Gateway Managed IP Network[1] Backup Gateway [1] All core network systems deployed to geographically redundantdispersed sites.

  15. 6 2 4 3 1 5 Fixed Mobile Convergence Launched in early 2004 and branded Wireless IP Connect • Building market experience thru live trials • Mobile operators, internet service providers and universities Serving-MSC model (Roaming to Wi-Fi) • Microsoft Windows Mobile Pocket PC (HP iPAQ and i-mate PDA2K) • SIP based soft-phone client manages handset radio interfaces • Protocol inter-working function performs SIP to MAP interoperability Enterprise IS-41/SIP Peering (Interoperability) Mobile Network HLR (Presence update) SS7 Network (TLDN discovery) (TLDN to IP mapping) PBX/Media Gateway (TLDN call setup) PSTN Gateway-MSC (Inbound Call)

  16. DID On-Demand (Peering CLECs and ISPs) Acquiring local numbers is difficult • FCC has historically required CLEC certification to obtain numbers • Numbers assigned in thousands blocks by rate center – ITSPs often do not have a sufficient customer base in any region to use a block • Complex porting issues and government reporting requirements Acquiring local numbers is expensive • ISDN PRIs to connect to the media gateway • Unnecessary long-distance switched access costs VeriSign’s DID-On-Demand service gives ITSPs a single source for ordering and provisioning telephone numbers (DIDs) • Service allows the allocation of phone numbers on an as-need-basis CLEC ISP/ITSP

More Related