Abstract

AbstractThis paper considers H.323 v4 VoIP networks consisting of gateways and gatekeepers, addressing the task of terminating calls to multiple ISDN networks. Our goal is the maximal utilization of the gatekeeper's centralized routing mechanism for call termination to ISDN networks based on load balancing and resource availability indication (RAI), thus minimizing the need for usage of unwanted (second attempt) overflow mechanisms. We elaborate on the drawbacks of overflow mechanisms and give an overview on different solutions offered in practice by vendors. The discussion justifies the emphasis on load balancing, thus we present an algorithm and tool assisted approach for the systematic assignment of PRIs from ISDN networks to gateways. We follow strictly defined design criteria that lead to an optimized network dial‐plan. We thus offer a stand alone, off‐line solution without the need of any extra add‐ons or upgrades. This is intended to replace the purely intuitive approach followed by today's planners.Our scope is the design rather than the runtime environment; the latter continues to feature the simplicity of a single global RAI per gateway. We consider desirable and non‐desirable link distribution topologies between gateways and ISDN networks based on operational and economic evaluation criteria. These measure the number of ‘wasted’ gateway ports or ‘inappropriately’ allocated network interfaces. Our approach is illustrated through a worked out example showing key features of the proposed algorithm and revealing characteristic cases met in the ISDN interface allocation.Finally, we show how the presented methodology, which presently addresses a H.323 design issue, can provide performance benefits in the VoIP technologies of the immediate future. Copyright © 2005 John Wiley & Sons, Ltd.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.