
Interoperability 189
IP Telephony Configuration Guide
• SIP trunks do not support the MCDN networking protocol
• Business Communications Manager call redirection and conferencing are supported
• a third-party SIP parser is used for encoding and decoding -- oSIP from GNU software
• SIP trunks are available between Business Communications Managers running BCM 3.5 or
newer software.
T.38 fax restrictions and requirements
Hardware restriction: IP telephony, including T.38 fax cannot operate on a system that has PEC
Is installed on the MSC.
The following is a list of restrictions and requirements for the T.38 fax protocol.
Table 49 T.38 restrictions and requirements
Supported Not supported
only UDP transport MCDN
only UDP redundancy TCP
T.38 version 0 Forward Error Correction (FEC)
on H.323 VoIP trunks between BCMs or between
BCMs and Meridian 1-IPT
Fill removal
MMR transcoding
JBIG transcoding
Norstar systems
SIP trunking
Resource limitations
T.38 fax transactions require significant DSP resources. They use the same resources as the fax/modem
task. Each task consumes one DSP; or two DSPs if the session terminates on an application port, such as
voice mail. Heavy fax traffic could affect IP telephone service if a number of faxes simultaneously come in
on shared DSPs. Refer to the Programming Operations Guide, MSC section, for details about setting up
DSP configuration.
Comentarios a estos manuales