
178 Interoperability
P0604630 03
2.5 FP
2.5 FP1 MR1.1
3.0, 3.0.1, 3.5
Long tones do not work over IP trunks.
2.5 FP1
2.5 FP1 MR1.1
3.0 , 3.0.1, 3.5
Firewall Default Rules, when enabled, block call processing and signaling. You must add an
additional rule to pass Protocol TCP\UDP, Destination Port H.323 for speech path to
initialize.
2.5 FP1
2.5 FP1 MR1.1
3.0, 3.0.1, 3.5
If an IP Telephony Remote Gateway IP address is pointed at a Wan Link Interface, which is
a Published IP address, the ISDN WAN Backup Feature will not support VoIP Traffic from
any set type to that Published IP Address in some Network Topologies.
2.5 FP1
2.5 FP1 MR1.1
3.0, 3.0.1
3.5
Symbol portable IP handsets
• Login by Extension is login option offered by the telephone, but is not currently
supported by Business Communications manager. The work-around is to administer the
extension as the username in Unified Manager.
• The NetVision handsets do not support G.723, so they will be unable to negotiate a call
on a VoIP trunk if the trunk is set to G.723 only.
• Call Center (ACD) FEATURE 909 is not supported. This is an unworkable feature on
single line display sets, including the M7100, and especially on Symbol.
• Calls between Symbol sets do not support the Call Record feature.
• There is sometimes significant echo heard on the Symbol set during ringback on
outgoing calls over analog lines.
• Business Communications Manager does not support remote registration for symbol
sets if these sets are behind another device, for example, another Business
Communications Manager, or a third-party router, which has NAT turned on.
• Each H323 Terminal configured utilizes one IP Client Resource, whether the H323
Terminal is being used or not.
• Firewall Default Rules, when enabled, block Symbol Registration and call processing.
You must add two additional rules. (1) Pass Protocol TCP\UDP, Destination Port H.323
and (2) Pass Protocol UDP, Destination port 1719.
• Ring cadence on Symbol handsets does not distinguish between Internal and External
callers.
• Symbol sets work fine as members of hunt groups, but when they are answer DN
twinned with other sets, they do not ring under some circumstances.
• When configured with an answer DN for a set in a hunt group, Symbol sets sometimes
do not ring, or ring but do not display CLID information, and cannot answer the incoming
call. It is recommended that the Symbol set be added to the hunt group before the
answer DN set, or that the Symbol set be designated as the prime DN, with the
answer DN for it applied to the twinned desk set. This does address most of the
functionality problems. There still appears to be a problem for calls routed by CCR.
2.5 FP1 MR1.1 *Gatekeeper
• Officially Business Communications Manager supports only ECS 2.1.0.1 gatekeeper.
Business Communications Manager does not support Call Setup (Q.931) routing mode.
• Business Communications Manager does not support the Radvision Dialing plan
package.
• ECS option Check that call is active every XXX seconds must be unchecked.
• Radvision ECS 2.1.0.1 gatekeeper limitations: ECS does not support fast start in the Call
Setup (Q.931) and Call Control (H.245) routing mode.
Table 46 Software interoperability restrictions and limitations for IP trunking (Continued)
Software release Description of restriction/limitation
Comentarios a estos manuales