
188 Interoperability
P0609327 02
The following table shows which networking applications are supported for each Business
Communications Manager software release.
SIP trunk interoperability issues
The following bullets list the restrictions and requirements for using SIP trunks on a Business
Communications Manager.
SIP trunking uses SIP ALG (Application Level Gateway), which has the following limitations:
• no support for nested NAT
• no support for non-SIP third-party NAT
• no support for domain names that require NAT or firewall translation
• the application only uses an IP address in URI (Uniform Resources Identifiers) format
• no third-party SIP endpoints behind Business Communications Manager NAT are supported
in this release
• multiple media types are supported on the same call, but multiple codecs for the same media
type are not
• multicast is not supported
• no encryption/decryption is supported within the body of a SIPs message; VPN encryption
between Business Communications Managers is supported.
• SIP trunks use the UDP signaling protocol on a fixed port (5060)
• the Business Communications Manager is a SIP UA client only
• SIP trunks are not supported across a NAT boundary as they assume the Business
Communications Manager published and public IP addresses are the same address
• SIP call forming is not supported
Table 48 Software network communications application compatibility
BCM version
Application compatibility
BCM
2.03
BCM
2.5*
2.5
FP1*
2.5 FP1
MR1*
BCM 3.0/
3.0.1*
BCM
3.5
Net
Meeting
ITG/IPT v.
X.X Symbol GK CSE1K
BCM 2.03 X basic call
to/from
ITG v.
25.24
BCM 2.5 X X basic call
to/from
ITG v.
25.25
BCM 2.5 FP1 X X X X ITG 25.25 X
FP1 MR 1.1 X X X X ITG 25.25 X X
BCM 3.0 X X X X ITG 26.26^ X X X
BCM 3.5 X* X* X* X* X X IPT 3.0/3.1 X X X
BCM 3.6 X* X* X* X* X X IPT 3.0/3.1 X X X
* with QoS patch 3.0.0.25 or greater
^ITG is not supported on a private network that has any Business Communications Managers
running BCM 3.5 or newer software.
Comentarios a estos manuales