Network Considerations for IPECS
Integrating VoIP with your existing network takes a significant amount of careful planning. You must ensure the existing network infrastructure can support the additional bandwidth and performance requirements. Ideally, the IPECS Network should be able to logically separate voice and data networks, applying specific levels of service to each.

While seamlessly integrating the IPECS Platform with your existing network can be a complex process, careful planning and liason with your telephony specialist will help you reach the end goal of a IP-based telephony network that provides additional features and cost savings.

Arrow Network Bandwidth Calculations

The standard method of transporting voice packets through IP-based networks requires the addition of three headers, these are IP, UDP and RTP. The speech is called the 'payload' and varies dependant upon the codec used to compress the speech. The diagram below gives a good indication of the make-up of VoIP network traffic. 

IP BAR

Different codecs can be used to compress the speech, resulting in different Network bandwidth considerations. The IPECS Platform is capable of using different codes to fit with your Network.

G.711 |  High bandwidth requirement (175 Kbps) but best speech quality

G.723 .1 |  Medium bandwidth requirement (45 Kbps) with average speech quality

G.729A |  Low bandwidth requirement (35Kbps) but sacrifices some speech quality

 

This site is operated by iData, an approved LG-Ericsson UK Partner. IPECS and ipLDK are registered Trademarks, parts of this site are copyright LG-Ericsson. Ltd 2009