Realities of Multi-Domain Gateway Network Management Jonathan Rosenberg Chief Scientist Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
Limitations of Single Provider Vo. IP l Single Provider Vo. IP Networks are a Barrier to Entry n Difficult for a single carrier to get national or international coverage A n Wide coverage needed for cost B advantages n Capital investment of many international POPs is significant l Solution - Multi-Provider C n Each provider owns a set of POPs n Calls originating in POP of one provider can terminate in POP of another Insert Tradeshow or Event Name -- Date Insert Presentation Title D www. dynamicsoft. c om
Multi-Provider Agreements l Multi-Provider Case Requires P 2 P Agreements Between Entities l Many Possible Organizations of Agreements n Peer to peer bilateral n Settlement House (star) Settlement House n Confederation (full mesh) l Each Organizational Arrangement is a Series of Bilateral Agreements l Results in a Requirement of Bilateral Information Flow Insert Tradeshow or Event Name -- Date Insert Presentation Title Confederation www. dynamicsoft. c om
Information Exchange l Main Question: Where to Route an Incoming Call? l Depends on a Number of Factors: n The set of phone numbers each provider is willing to terminate n Cost/billing/pricing arrangements n Preferences for a particular provider n POLICY l Decision Must be Made Quickly n Affects call setup time l How is it Accomplished? Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
Solution: TRIP l Telephony Routing over IP l Being Developed in IP Telephony Working Group in IETF l Specification is Mature, RFC Shortly l What does it do? n Exchange of routing information between peer providers n Exchange happens outside of call setup n Routing information consists of phone prefixes and associated data n Allows for aggregation and redistribution n Strong policy support Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
TRIP Components Gateways l Internet Telephony Administrative Domain (ITAD) n Owner of GW, LS, users l Location Server (LS) Location Server n Primary component n Exchanges routing information ITAD B with internal and external peers TRIP l Front End n Protocol mechanism used to access TRIP data n Typically SIP End Users ITAD A Front End Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
What are its main features? l Based on Scalable IP Routing Technology n Combination of BGP 4 and IS-IS n Proven algorithms and operation l Support for LNP and Routing Numbers n includes international codes with hex values l Works for both SIP and H. 323 n Can even enable routing through conversion boxes Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
What are its Main Features cont. l Capabilities Exchange n Agree upon address family for routing l Send Only, Receive Only, Bidirectional Modes n Allows for domains that wish to only export or import routes l Extensibility n Support for new attributes built in n Attributes provide parameters for a route Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
How does it work? l An LS is Statically Configured with its Internal and External peers n No autodiscovery n External relationships need to be driven from business needs l LS Connects to Peers n TCP connection l Route Exchange n Complete synchronization of routing tables with external peers n Sharing of learned routes with internal peers n Only happens initially l Keepalives n After route exchange, period n Basic capabilities negotiation keepalives l Address families n Small in size l Send/Receive/Send-only n Agree on keepalive interval l Updates n If route changes, modified route is sent n Incremental updates Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
Location Server Processing l An LS Will Receive Routes from Internal Routes Adj. TRIB In Many Sources Local Routes n External Peers n Internal Peers n Statically configured l Needs to Generate n Local Telephony Routing Policy Decision Process Information Base (TRIB) n Routes to send to peers l Accomplished with Decision Local TRIB Process n Combines routes from sources n Generates Local TRIB n Outputs Routes Insert Tradeshow or Event Name -- Date Insert Presentation Title Adj. TRIB Out www. dynamicsoft. c om
Summary l Problem: n Single provider cannot own all gateways n Need for a way to support multi-provider operation l Solution: n Telephony Routing over IP (TRIP) n Protocol for inter-domain exchange of routes bilaterally Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
Information Resource l Jonathan Rosenberg n jdrosen@dynamicsoft. com n +1 732. 741. 7244 Insert Tradeshow or Event Name -- Date Insert Presentation Title www. dynamicsoft. c om
Скачать презентацию Realities of Multi-Domain Gateway Network Management Jonathan Rosenberg
0453b4b262763e7cf8f0ebd9ee31ed0d.ppt