voipeer-7----Page:3
1 2 3 4 5 6 7 8 9 10
|
The Context for ENUM in VoIP Peering Without ENUM: Each switch (CMS) is largely an island unto itself. Linking many CMSs is difficult to scale. Vendor-specific methods to share TN / IP data. Legacy / PSTN-centric solutions (inefficient via IP). ENUM can tell me, for a dialed TN, what IP network element (CMS, Proxy, SBC, etc.) to send a call to. Can help to enable easily scalable: CMS-to-CMS calling (all PacketCable). PacketCable-to-SIP calling. Fixed-to-wireless calling. MSO-to-MSO calling. MSO-to-any IP-based carrier calling. BUT, ENUM is just one part of the solution (lest we forget SIP). Laying the foundation now: (1) Working to use ENUM as part of a solution to simplify call routing; peering work is incremental. (2) Working on backbone for peering and other uses (takes time). |