# Cisco TelePresence Content Server 5.3  with Wowza Streaming Engine 4.0.1

**URL:** <https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357>\
**Category:** Wowza Streaming Engine\
**Created:** [March 21, 2014, 1:26pm UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357 "2014-03-21T13:26:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tom\_Leinos](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Tom\_Leinos](https://community.wowza.com/u/Tom_Leinos)\
**Post date:** [March 21, 2014, 1:26pm UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/1 "2014-03-21T13:26:41Z")

</div>

Hi, i have been using Wowza 3.6.2 for Cisco TelePresence Content Server 5.3, it worked fine. I am now testing Wowza Streaming Engine 4.0.1 and i cannot get it to work.

I have an identical configuration that worked in 3.6.2. Is there something that must be done for version 4.0.1 that is not included in:

[http://www.cisco.com/en/US/docs/telepresence/tcs/5\_0/media\_servers/configuration/guide/wowza.fm.html#wp117942](http://www.cisco.com/en/US/docs/telepresence/tcs/5_0/media_servers/configuration/guide/wowza.fm.html#wp117942)

I can’t figure it out:

INFO server comment - MediaCasterStreamValidator.init[_defapp_/_definst_]: Started

INFO application app-start _definst_ _defapp_/_definst_

INFO application app-stop _definst_ _defapp_/_definst_

TCS Error:

[https://dl.dropboxusercontent.com/u/62668454/tcs\_error.JPG](https://dl.dropboxusercontent.com/u/62668454/tcs_error.JPG) (RTSP Announce failed to server).

br. Tom

---

<div class="post-metadata">

**Author:** ![koorus\_bookan](https://avatars.discourse-cdn.com/v4/letter/k/ce73a5/32.png) [@koorus\_bookan](https://community.wowza.com/u/koorus_bookan)\
**Post date:** [April 10, 2014, 11:26am UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/2 "2014-04-10T11:26:09Z")

</div>

> Hi, i have been using Wowza 3.6.2 for Cisco TelePresence Content Server 5.3, it worked fine. I am now testing Wowza Streaming Engine 4.0.1 and i cannot get it to work.
> 
> I have an identical configuration that worked in 3.6.2. Is there something that must be done for version 4.0.1 that is not included in:
> 
> [http://www.cisco.com/en/US/docs/telepresence/tcs/5\_0/media\_servers/configuration/guide/wowza.fm.html#wp117942](http://www.cisco.com/en/US/docs/telepresence/tcs/5_0/media_servers/configuration/guide/wowza.fm.html#wp117942)
> 
> I can’t figure it out:
> 
> INFO server comment - MediaCasterStreamValidator.init[_defapp_/_definst_]: Started
> 
> INFO application app-start _definst_ _defapp_/_definst_
> 
> INFO application app-stop _definst_ _defapp_/_definst_
> 
> TCS Error:
> 
> [https://dl.dropboxusercontent.com/u/62668454/tcs\_error.JPG](https://dl.dropboxusercontent.com/u/62668454/tcs_error.JPG) (RTSP Announce failed to server).
> 
> br. Tom

Hello, was there a solution to this? I have the exact problem, so it seems.

---

<div class="post-metadata">

**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\
**Post date:** [March 21, 2014, 9:55am UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/3 "2014-03-21T09:55:33Z")

</div>

A couple things to check/try

Make sure you have a username and password set up in the /conf/publish.password file. Or for testing purposes you could disable authentication temporarily by editing conf/[application]/Application.xml and changing RTP/Authentication/Method to none.

Another idea is to turn on debug logging by editing conf/log4j.properties and changing the log level on the first line from INFO to DEBUG. Maybe something will show up as the culprit.

Salvadore

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [March 27, 2014, 2:19pm UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/4 "2014-03-27T14:19:36Z")

</div>

That guide is for Wowza 3, but it should work if you follow the instructions using the configuration files in Wowza 4. Do not copy old configuration files from Wowza 3 to Wowza 4, rather start with Wowza 4 files.

If you still do not have this working, do a short test then send us some files. First delete the current access log, then re-start Wowza (important to restart so we can see logging for startup), and run through testing, however you are using Wowza and Cisco Content Server. Then zip up the /conf folder and current access log showing the re-start and your testing to support@wowza.com. Include a link to this thread for reference.

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [March 27, 2014, 2:20pm UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/5 "2014-03-27T14:20:19Z")

</div>

Also, please revert to INFO level logging before you re-start.

Richard

---

<div class="post-metadata">

**Author:** ![koorus\_bookan](https://avatars.discourse-cdn.com/v4/letter/k/ce73a5/32.png) [@koorus\_bookan](https://community.wowza.com/u/koorus_bookan)\
**Post date:** [April 10, 2014, 11:49am UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/6 "2014-04-10T11:49:42Z")

</div>

Huh!

Take a look here:

Notes on Configuring Wowza 4.x on Content Server

When you configure a Wowza 4.x media server in the Content Server Management \> Recording Setup \> Media server configurations \> + Add Wowza server screen, you might see the following error when you click Save.

Failed to announce the RTSP to the wowza server

This is the workaround:

Step 1 Log in to the Wowza streaming manager. Navigate to the Applications page.

Step 2 Choose Add Application .

Step 3 Choose Live: Single Server or Origin .

Step 4 Name the application _defapp_ and click Save .

Step 5 Restart the Wowza server. Add the Wowza media server in the Content Server

[http://www.cisco.com/c/en/us/td/docs/video/digital\_media\_systems/5\_x/5\_3/showandshare/integration/notes/sns\_wowza.html](http://www.cisco.com/c/en/us/td/docs/video/digital_media_systems/5_x/5_3/showandshare/integration/notes/sns_wowza.html)

---

<div class="post-metadata">

**Author:** ![Tom\_Leinos](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Tom\_Leinos](https://community.wowza.com/u/Tom_Leinos)\
**Post date:** [March 27, 2014, 4:06pm UTC](https://community.wowza.com/t/cisco-telepresence-content-server-5-3-with-wowza-streaming-engine-4-0-1/40357/7 "2014-03-27T16:06:44Z")

</div>

Hi, there was no new errors, i tried disabling authentication and also put log level to debug:

> DEBUG server comment - explodeStorageDir: ${com.wowza.wms.context.VHostConfigHome}/content=/usr/local/WowzaStreamingEngine/content
> 
> DEBUG server comment - validateStoragePath: start: /usr/local/WowzaStreamingEngine/content
> 
> DEBUG server comment - explodeStorageDir: ${com.wowza.wms.context.VHostConfigHome}/keys=/usr/local/WowzaStreamingEngine/keys
> 
> DEBUG server comment - validateStoragePath: start: /usr/local/WowzaStreamingEngine/keys
> 
> DEBUG server comment - explodeStorageDir: ${com.wowza.wms.context.VHostConfigHome}/applications/${com.wowza.wms.context.Application}/sharedobjects/${com.wowza.wms.context.ApplicationInstance}=/usr/local/WowzaStreamingEngine/applications/_defapp_/sharedobjects/_definst_
> 
> DEBUG server comment - validateStoragePath: start: /usr/local/WowzaStreamingEngine/applications/_defapp_/sharedobjects/_definst_
> 
> INFO server comment - MediaCasterStreamValidator.init[_defapp_/_definst_]: Started
> 
> INFO application app-start _definst_ _defapp_/_definst_
> 
> INFO application app-stop _definst_ _defapp_/_definst_
