Cisco Cisco TelePresence Management Suite (TMS) Version 15
Problem or
Message
Message
Possible Causes
Recommended Action
Dial sequence
cannot be
issued on the
fly via TSP API
(unlike NBR).
cannot be
issued on the
fly via TSP API
(unlike NBR).
The dial sequence for OT 2.0 integration with TSPs is only
statically configurable in the Telephony Domain of site. This
restricts a TSP somewhat, in case they might have different
audio bridge infrastructures, different dial in numbers, etc.
statically configurable in the Telephony Domain of site. This
restricts a TSP somewhat, in case they might have different
audio bridge infrastructures, different dial in numbers, etc.
NBR, by contrast, allows for the static configuration as well as
a dynamic configuration. The dynamic configuration is done
by having the partner TSP Adapter send WebEx the NBR dial
string at the time of meeting start via A2W_
RspCreateConference[NBRPhoneNumber].
a dynamic configuration. The dynamic configuration is done
by having the partner TSP Adapter send WebEx the NBR dial
string at the time of meeting start via A2W_
RspCreateConference[NBRPhoneNumber].
n
Change the MCU logic,
so that it starts the WebEx
meeting and then collects
the dial in string from
WebEx at that time. The
sequence will allow for
WebEx to collect the dial
string dynamically from
the TSP as follows:
so that it starts the WebEx
meeting and then collects
the dial in string from
WebEx at that time. The
sequence will allow for
WebEx to collect the dial
string dynamically from
the TSP as follows:
a. TelePresence starts
TelePresence
meeting.
meeting.
b. TelePresence starts
WebEx meeting.
c. WebEx sends W2A_
CreateConference to
TSP.
TSP.
d. TSP sends A2W_
RspCreateConference
to WebEx (this would
contain the TP dial
string).
to WebEx (this would
contain the TP dial
string).
e. WebEx sends dial
string to MCU.
f. MCU dials into the
TSP bridge.
The TSP API and TSP
Server would need to
change (among other
components, of course).
Server would need to
change (among other
components, of course).
The TSP Audio
account info,
used by the
MCU dial string,
is obsolete.
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.
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.
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 22: 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.
Server and MCU.
Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 14.4 - WebEx WBS29)
Page 181 of 186
Troubleshooting
Troubleshooting Tips