Manual

14
Configuring the Cisco TelePresence Content Server Release 5.x to Use an External Windows Media Streaming Server
Troubleshooting
Publishing Point on External Windows Media Server
Troubleshooting
Problem Publishing point verification
Recommended Action Verify that the broadcast publishing point shows ‘started’ on the remote
windows media, which indicates a successful publish.
Recommended Action Verify proper live streaming functionality by pointing a compatible media
player at the publishing point with the following syntax:
mms://Content_Server_IP_Address/Publishing_Point_Name
Problem Windows authentication
Possible Cause If the Content Server is in Domain A and the external media server is in Domain B,
you might have a problem.
Check the Content Server logs for the following warning to verify that you are experiencing this
problem: Warning: Reporting Windows Media writer status, Error occurred in WMT_ERROR
[call_id = 1, address = http://Content_Server_IP_Address/Publishing_Point_Name, error = error
code = (0xc00d2f0b)]
Recommended Action Check your AD configuration, trust, and so on. The simplest case is where both
the Content Server and the external media server are in the same Domain or are both in a Workgroup.
Related Documentation
For more information about the Cisco TelePresence Content Server, see these documents:
Cisco TelePresence Content Server Release Administration and User Guide
Configuring the Cisco TelePresence Content Server for Streaming from a QuickTime Media Server
Configuring the Cisco TelePresence Content Server for Streaming Flash from a Wowza Media
Server
Cisco TCS Integration to Cisco Show and Share for Live WMV Streaming
1 Publishing point is started 2 Source is Push:*