Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 - Troubleshooting
No video through an ISDN gateway
Some ISDN endpoints initiate a call using one set of codecs, then before media is sent, change the
codecs to better codecs (for example an initial offering of H.261 is updated to H.263). Neither MOC
R1, nor MOC R2 accepts a change in codec before media is sent.
codecs to better codecs (for example an initial offering of H.261 is updated to H.263). Neither MOC
R1, nor MOC R2 accepts a change in codec before media is sent.
To work around this, “Meet me” on a conference, so that the ISDN endpoint sets up a call and
connects to the MCU and MOC sets up a call and connects to the MCU independently.
connects to the MCU and MOC sets up a call and connects to the MCU independently.
Call to PSTN or other device requiring caller to be authorized
fails with 404 not found.
fails with 404 not found.
In Some OCS configurations, especially where OCS PSTN gateways are used, calls are only allowed
to be made if the calling party is authorized. This actually means that the calling party’s domain must
be the OCS’s domain.
to be made if the calling party is authorized. This actually means that the calling party’s domain must
be the OCS’s domain.
For calls from endpoints that are not part of a FindMe™ this means that the endpoints must register to
the video network with a domain that is the same as the OCS domain.
the video network with a domain that is the same as the OCS domain.
For calls from endpoints that are part of a FindMe™ the endpoints can register with any domain so
long as the FindMe™ ID has the same domain as OCS and in the FindMe™ configuration Caller ID is
set to FindMeID (instead of IncomingID).
long as the FindMe™ ID has the same domain as OCS and in the FindMe™ configuration Caller ID is
set to FindMeID (instead of IncomingID).
MOC endpoints try to register with Cisco VCS Expressway.
SIP video endpoints usually use DNS SRV records:
_sips._tcp.<domain>
_sip._tcp.<domain>
_sip._tcp.<domain>
and
_sip._udp.<domain>
in that order to route calls to Cisco VCS.
MOC uses:
_sipinternaltls._tcp.<domain>
- for internal TLS connections
_sipinternal._tcp. <domain>
- for internal TCP connections (only if TCP is allowed)
_sip._tls. <domain>
- for external TLS connections
_sip._tcp.<domain>
- for external TCP connections (R1 only)
_sip._tcp.<domain> is common to both when MOC R1 is used on an external network. From R2 MOC
only supports TLS connection to the Edge Server. The _sip._tcp.<domain> DNS SRV record should
be used for the Cisco VCS Expressway. Configure MOC to use encryption (set OCS to ‘Supports
encryption’ – as specified in the configuration process) and ensure that TCP is not forced in the
Advanced section of the sign in address configuration on MOC.
only supports TLS connection to the Edge Server. The _sip._tcp.<domain> DNS SRV record should
be used for the Cisco VCS Expressway. Configure MOC to use encryption (set OCS to ‘Supports
encryption’ – as specified in the configuration process) and ensure that TCP is not forced in the
Advanced section of the sign in address configuration on MOC.
OCS Relay problems
OCS Relay FindMe™ users take a long time to register.
OCS Relay can take up to 3 minutes to pick up a new OCS Relay FindMe™ entry and register it. If a
number of entries get deleted and the same number get added, it can take OCS Relay up to 60
minutes to observe the change in identities and update the registrations.
number of entries get deleted and the same number get added, it can take OCS Relay up to 60
minutes to observe the change in identities and update the registrations.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2
Page 68 of 92