Cisco Cisco TelePresence Video Communication Server Expressway
Check for errors
Event Log
Check the VCS Event Log (
Status > Logs > Event Log
).
Tracing calls
Tracing calls at SIP / H.323 level
1. Log in to VCS Control web interface.
2. Go to
Maintenance > Diagnostics > Diagnostics logging
.
3. Click Start new log.
4. Retry the action for which the problem occurs (such as setting up a call or similar).
5. Click Stop logging followed by Download log.
The log file will contain information related to the events triggered by the action performed in step 4.
MXP will not create a Multiway call
Whether the MXP uses H.323 signaling or SIP signaling to call the Multiway Conference Factory Alias is
defined by the Multiway URI configured on the MXP.
defined by the Multiway URI configured on the MXP.
If the Multiway URI is prefixed with “sip:”, e.g. sip:multiway@domain then the MXP will always make the call
to the Multiway™ Conference Factory Alias using SIP signaling; if it does not have the ‘sip:’ prefix e.g.
multiway@domain or has an h323: prefix, e.g. h323:multiway@domain then the MXP will always make the
call to the Multiway Conference Factory Alias using H.323 signaling.
to the Multiway™ Conference Factory Alias using SIP signaling; if it does not have the ‘sip:’ prefix e.g.
multiway@domain or has an h323: prefix, e.g. h323:multiway@domain then the MXP will always make the
call to the Multiway Conference Factory Alias using H.323 signaling.
The Multiway Conference Factory Alias must be in URI format name@domain as the underlying Conference
Factory operation is SIP based and operates on SIP URIs.
Factory operation is SIP based and operates on SIP URIs.
The MXP must therefore be registered to the VCS, or be configured so that it can route calls to the VCS using
the appropriate protocol (H.323 or SIP). Otherwise although “Merge” will be presented on the screen, when
pressed the Multiway call will fail.
the appropriate protocol (H.323 or SIP). Otherwise although “Merge” will be presented on the screen, when
pressed the Multiway call will fail.
n
If the Multiway URI has a “sip:” prefix, ensure that SIP calls can be made from the MXP to the VCS.
n
If the Multiway URI does not have a “sip:” prefix, ensure that H.323 calls can be made from the MXP to the
VCS.
VCS.
Calls use less bandwidth than expected
When a Multiway conference is created, the bandwidth assigned to the original call is not released until after
the merged Multiway call is established. Therefore, in limited bandwidth situations the Multiway call could
connect at a lower bandwidth than the original call.
the merged Multiway call is established. Therefore, in limited bandwidth situations the Multiway call could
connect at a lower bandwidth than the original call.
The following example explains what could happen:
1. Pipe01 is configured with a total bandwidth restriction of 900kbps.
2. EP01 in SZ01 calls EP02 in SZ02 consuming 384kbps on Pipe01.
3. EP01 puts EP02 on hold.
Cisco TelePresence Multiway™ Deployment Guide (X8.2, XC2.3)
Page 25 of 36
Appendix 1: Troubleshooting