3300 ICP General Information Guide
32
Malicious Call Trace
For incoming SIP calls that are tagged for Malicious Call, the 3300 records the Media IP address
and port used remotely. As well, the SIP signalling information is captured. This information
cannot be sent to the SIP Service Provider, but the information is recorded if needed.
Note: Malicious Call SMDR records are logged on the 3300 ICP. SIP endpoints cannot
invoke Malicious Call Trace, but is it recommended that SMDR be enabled for SIP devices
and gateways.
FAX
The SIP Trunking for Service Provider configuration supports FAX calls over G.711. Attempts
to switch to T.38 are rejected, and the call continues as G.711. It is recommended that FAX
machines be connected locally or through TDM to the 3300 ICP that is connected to the Service
Provider through SIP trunks.
Compression
Optimization of bandwidth is a key requirement in a VoIP system. In order to meet this
requirement, the 3300 ICP supports G.729a voice compression. G.729a compression reduces
the bandwidth required for a call from 64 kbps to 8 kbps plus packet overhead. By using voice
compression across the LAN/WAN infrastructure, customers can ensure that they are able to
optimize their bandwidth usage for voice calls. The mechanism for managing this feature is
based on a zone concept. Groups of devices on the 3300 ICP can be placed in a zone so that
calls between zones can be compressed while calls within the same zone are not. Zones can
be defined within a controller's LAN infrastructure, between remote IP devices and the controller
and across the WAN for multiple controller networks.
Most Mitel IP phones inherently support G.729a voice compression. Calls between IP Phones
on the LAN/WAN infrastructure can thus be compressed to G.729a as required. For example,
a call between IP Phone B and IP Phone D (over the LAN or WAN) can be compressed without
system compression resources.
G.729a Compression is also supported for calls that have TDM (Digital or Analog) endpoints
that cross the LAN/WAN infrastructure. For example, a call from TDM phone A to IP Phone D
can be compressed using compression resources in controller A to compress the LAN/WAN
segment between Controller A and IP Phone D. The same compression occurs if TDM Phone
A called TDM Phone C over the LAN/WAN except that in this case compression resources
would be required on both controllers.
To Next Page
Loading...
