Cannot re-stream from a Cisco Content Server
Hi,
I tried to configure WMS 3.5 to re-stream a live RTSP stream coming from a Cisco Content Server (TCS) 5.1, but I cannot seem to get it to work correctly.
As per the article at http://www.wowza.com/forums/content.php?99-How-to-use-the-Cisco-Content-Server-with-Wowza-Media-Server, I followed the deployment guide at http://www.cisco.com/en/US/docs/telepresence/tcs/5_0/media_servers/configuration/guide/wowza.fm.html, with the only relevant difference of having set an alternate application up since the "live" application was already used for other purposes.
After both the WMS and TCS had been set up correctly, I went on trying to get the stream played following the guide at http://www.wowza.com/forums/showthread.php?9076-Re-streaming-an-RTSP-stream-through-Wowza-Pro-%28RTSP-RTP. I created a .stream file containing the IP address of the TCS in WMS content directory, then I published the stream from the Stream Manager and tried to get it playing in the Live Stream Player example that comes bundled with Wowza, inputting rtmp://my-server-ip/myapp as the server and mystreamname.stream as the stream name. The result was a "Failed to play mystreamname.stream; stream not found." message.
The TCS apparently can connect and send its stream to WMS, and this is shown in the Wowza access log file:
However, it appears that TCS is using the live application, instead of the specifically created "myapp", even though it was specified in the TCS control panel.
An attempt was made at changing the Application.xml file of the "live" application with the "myapp" one, but the error persisted.
The Cisco support team was contacted, and they found that on TCS side the stream is being correctly sent, but something is not working in the re-streaming. Also, it was noted that the deployment guide was not updated to WMS versions > 2, so maybe there have been some changes to the WMS that aren't taken into account in that document.
Finally, if this can be of any help, the WMS is running on a CentOS 5.5, 64bit.
Can you help me in sorting this out?
I tried to configure WMS 3.5 to re-stream a live RTSP stream coming from a Cisco Content Server (TCS) 5.1, but I cannot seem to get it to work correctly.
As per the article at http://www.wowza.com/forums/content.php?99-How-to-use-the-Cisco-Content-Server-with-Wowza-Media-Server, I followed the deployment guide at http://www.cisco.com/en/US/docs/telepresence/tcs/5_0/media_servers/configuration/guide/wowza.fm.html, with the only relevant difference of having set an alternate application up since the "live" application was already used for other purposes.
After both the WMS and TCS had been set up correctly, I went on trying to get the stream played following the guide at http://www.wowza.com/forums/showthread.php?9076-Re-streaming-an-RTSP-stream-through-Wowza-Pro-%28RTSP-RTP. I created a .stream file containing the IP address of the TCS in WMS content directory, then I published the stream from the Stream Manager and tried to get it playing in the Live Stream Player example that comes bundled with Wowza, inputting rtmp://my-server-ip/myapp as the server and mystreamname.stream as the stream name. The result was a "Failed to play mystreamname.stream; stream not found." message.
The TCS apparently can connect and send its stream to WMS, and this is shown in the Wowza access log file:
2012-12-06 17:47:38 CET connect rtsp INFO 200 380891797 - _defaultVHost_ live _definst_ 4293.739 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 - - - - - - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:47:38 CET create stream INFO 200 - - _defaultVHost_ live _definst_ 0.001 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 1 0 0 0 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:47:38 CET announce rtsp INFO 200 380891797 - _defaultVHost_ live _definst_ 0.073 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 - - - - 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:47:38 CET publish stream INFO 200 135481280522-24551711.sdp - _defaultVHost_ live _definst_ 0.02 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 1 0 0 0 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:47:38 CET publish rtsp INFO 200 380891797 - _defaultVHost_ live _definst_ 0.092 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 - - - - 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:49:08 CET unpublish stream INFO 200 135481280522-24551711.sdp - _defaultVHost_ live _definst_ 90.204 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 1 0 0 0 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:49:08 CET destroy stream INFO 200 135481280522-24551711.sdp - _defaultVHost_ live _definst_ 90.208 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 1 0 0 0 135481280522-24551711.sdp - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp - 2012-12-06 17:49:08 CET disconnect rtsp INFO 200 380891797 - _defaultVHost_ live _definst_ 4383.951 my-server-ip 554 rtmp://my-server-ip/live/135481280522-24551711.sdp tcs-ip rtsp - Cisco TelePresence Content Server/5.1 380891797 0 0 - - - - - - - - - - rtmp://my-server-ip/live/135481280522-24551711.sdp rtmp://my-server-ip/live/135481280522-24551711.sdp - rtmp://my-server-ip/live/135481280522-24551711.sdp -
However, it appears that TCS is using the live application, instead of the specifically created "myapp", even though it was specified in the TCS control panel.
An attempt was made at changing the Application.xml file of the "live" application with the "myapp" one, but the error persisted.
The Cisco support team was contacted, and they found that on TCS side the stream is being correctly sent, but something is not working in the re-streaming. Also, it was noted that the deployment guide was not updated to WMS versions > 2, so maybe there have been some changes to the WMS that aren't taken into account in that document.
Finally, if this can be of any help, the WMS is running on a CentOS 5.5, 64bit.
Can you help me in sorting this out?
Restart Wowza, go through all these steps again, including playback in the Wowza player, then zip up the /conf and /logs folders and send them to
support@wowza.com.
Include a link to this thread for reference
Richard
Include a link to this thread for reference
Richard
