Cisco Cisco TelePresence Management Suite (TMS) Version 15
Problem or
Message
Possible Causes
Recommended Action
The TSP Audio
account info,
used by the
MCU dial string,
is obsolete.
Since the MCU collects and stores the TSP dial string at the
time of meeting schedule, to be used at the time of meeting
start (which can be many weeks later), there is a possibility
that the dial string will be obsolete and hence the call into the
TSP conference will fail. This will happen if the default (first)
TSP Audio account is changed during the time between
TelePresence meeting schedule and TelePresence meeting
start.
n
The above suggestion will
solve this problem
(making the TelePresence
equipment collect the
TelePresence dial string
from WebEx at the time of
meeting start, instead of at
the time of meeting
schedule.
Table 24: Problems with a TSP Meeting (continued)
Problems with TelePresence Server and MCU
This section describes possible issues with a meeting caused by TelePresence Server and MCU.
Refer to troubleshooting information in the table on how to solve common problems with TelePresence
Server and MCU.
Problem or Message
Possible Causes
Recommended Action
MCU/TelePresence Server disconnects shortly
after connecting to WebEx. A SIP Bye
message is received from the WebEx cloud.
WebEx host joins a meeting
while already joined to a meeting
of which they are also the host.
n
Do not use the same
WebEx host ID to join
multiple meetings at the
same time.
Note: Only one CMR
Hybrid meeting can be run
per host at a time.
Table 25: Problems with TelePresence Server and MCU
Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 14.6 - WebEx WBS29.11)
Page 238 of 254
Troubleshooting
Troubleshooting Tips