Cisco Cisco TelePresence MX700 Nota Di Rilascio
Interoperability
Cisco TelePresence System C/EX/SX/MX Series Software Release Notes
Page 113 of 194
Interoperability
The systems below have been tested and verified with this software release.
H.323 gatekeepers/traversal servers
Equipment
Software revision
Comments
TANDBERG
Gatekeeper
Gatekeeper
N6.1
TANDBERG
Border
Controller
Border
Controller
Q6.1
Both Assent and H.460.18/.19 traversal
technologies are supported
technologies are supported
Cisco
TelePresence
System Video
Communication
Server (VCS)
TelePresence
System Video
Communication
Server (VCS)
X6.1, X7.0.1
Both Assent and H.460.18/.19 traversal
technologies are supported
technologies are supported
SIP registrars/proxies
Equipment
Software revision
Comments
CUCM
8.6
! Native registration. Encrypted calls are not
supported.
! DTMF: KPML is not supported. If you use
an H.323 Gateway to access a public
telephone line, DTMF will not work. To
resolve this:
telephone line, DTMF will not work. To
resolve this:
Convert IOS Gateway to SIP or
MGCP.
MGCP.
Insert a Unified Border Element
between the CUCM and the H.323
Gateway to do SIP to H.323
conversion (CUCM-SIP-CUBE-
H.323-GW).
between the CUCM and the H.323
Gateway to do SIP to H.323
conversion (CUCM-SIP-CUBE-
H.323-GW).
! If you experience random call drops make
sure the default max size for SIP message
in CUCM is set to 11000 bytes (default is
5000 bytes)
in CUCM is set to 11000 bytes (default is
5000 bytes)
! If dual stream (BFCP) does not work:
Enable BFCP on SIP profile for
endpoints in CUCM.
endpoints in CUCM.
Enable BFCP for SIP trunk profile if
calling to/from a Cisco VCS.
calling to/from a Cisco VCS.
! NTP: Configure Unicast NTP references
for endpoints in CUCM.
! Provisioning: Make sure the endpoint has
a DNS server that can resolve the host
name, or change CUCM > System >
Server, to be IP address instead of
hostname.
name, or change CUCM > System >
Server, to be IP address instead of
hostname.
Cisco
TelePresence
System Video
Communication
TelePresence
System Video
Communication
X6.1, X7.0.1
If you configure a trunk towards CUCM 8.6, you
must create a custom SIP trunk that does not
remove BFCP lines towards CUCM. If you
choose CUCM as profile in the VCS, BFCP will
be removed and dual stream (BFCP) will not be
must create a custom SIP trunk that does not
remove BFCP lines towards CUCM. If you
choose CUCM as profile in the VCS, BFCP will
be removed and dual stream (BFCP) will not be