Results 1 to 7 of 7

Thread: Cisco TelePresence Content Server 5.3 with Wowza Streaming Engine 4.0.1

  1. #1
    Join Date
    Apr 2013
    Posts
    3

    Default Cisco TelePresence Content Server 5.3 with Wowza Streaming Engine 4.0.1

    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/tele....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/.../tcs_error.JPG (RTSP Announce failed to server).

    br. Tom

  2. #2

    Default

    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

  3. #3
    Join Date
    Apr 2013
    Posts
    3

    Default

    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_

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    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

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

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

    Richard

  6. #6
    Join Date
    Sep 2011
    Posts
    2

    Default

    Quote Originally Posted by tretorn View Post
    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/tele....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/.../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.

  7. #7
    Join Date
    Sep 2011
    Posts
    2

    Default

    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...sns_wowza.html

Similar Threads

  1. Replies: 3
    Last Post: 08-28-2014, 11:31 PM
  2. Live Streaming of HLS and HDS content packaged from a Cisco Encoder
    By koons5159 in forum Live Streaming and Encoder Discussion
    Replies: 1
    Last Post: 07-25-2013, 06:43 PM
  3. Cisco Content Server
    By deanomeara in forum Video On Demand Streaming Discussion
    Replies: 2
    Last Post: 04-11-2013, 01:29 AM
  4. Cannot re-stream from a Cisco Content Server
    By tigicongress in forum Live Streaming and Encoder Discussion
    Replies: 2
    Last Post: 12-11-2012, 07:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •