Mitel MiVOICE BUSINESS, Engineering Manualline

Page: 206 / 381

Engineering Guidelines
192
IP NETWORKING ROUTES AND COMPRESSION
Compression can be enabled in IP networking routes between 3300 ICP units if the end devices
are capable of this operation. For more details see “Compression zones” on page 192.
Compression zones
This section briefly describes compression zones, IP trunk routes, and network issues to
consider when planning the location of different devices.
Figure 27: IP Networking Compression Zones Example
Although the network shown in the figure above is not a real network, it highlights some of the
areas to consider in allocating bandwidth in different parts of the network:
• Calls within Zone 1 of both controllers are not compressed.
• Calls between controller A and controller B are sent over an IP networking route (IP trunk)
and are compressed but can be set up as non-compressed.
• All IP networking connections are considered as originating from Zone 1. If the IP network
connection is not compressed, but a call originates in a zone that normally uses compres-
sion and it goes back to Zone 1, the call is completed with compression.
• Although the two units are logically separated, they share a common physical infrastructure.
This is similar to network VLAN operation, but can lead to some unusual operations, similar
to VLAN, where local devices talk through a router. In effect, the controllers can be consid-
ered as voice routers.
• The IP phone in controller A, Zone 3 registers with controller A over the WAN link. Bandwidth
used by this device to talk to other devices on controller A is not counted against the IP
networking limits. Bandwidth for this remote phone should be considered in addition to the
IP networking requirements, since both IP network connections and remote connections
share a common infrastructure.
• If the phone in controller A, Zone 3 wants to communicate with the phone in controller B
Zone 1, it consumes an IP trunk session or channel, but no actual WAN bandwidth since