Live streaming error with Tricaster on Linux

[system]

Hi,

we have a customer that wants to live stream with a Newtek Tricaster (http://www.newtek.com/tricaster/). But this is not working on a Linux server running Wowza.

On a windows server there is no problem.

So we have setup two Wowza servers. One is on windows and one is on Linux.

The publish token is on both machines the same.

So the connection url is:

rtmp://[SERVER]/live/definst/doPublish=[UNIQUEKEY]

And when it connects to a windows servers, it is ok. But when they switch to the Linux server, the got the error: “Flash Media Encoder Error, Flash Media Encoder terminated prematurely, Please try again!”

Are there some OS dependencies in Wowza? And how can we get more debug information about the connection procedure?

Kind regards,

Joshua

[Richard_Lanham]

It sounds like security is setup differently on the two machines. Different tokens maybe.

Richard

[Richard_Lanham]

Is it Tricaster vs FMLE, or Windows vs Linux? What works and what doesn’t work?

The way you form the FMLE FMS url for security is different then other encoders where you can use a normal querystring.

Try it like this in Tricaster:

rtmp://[SERVER]/live?doPublish=[UNIQUEKEY]

You can turn on debug logging in /conf/log4j.properties by change “INFO” to “DEBUG” in the first line, to get more detailed logging.

Richard

[Joshua_Rubingh]

I don’t think so. When we use the Flash Media Encoder to connect to the Linux sever, there is no problem. Then the publish url is working.

So the token is valid and we can publish. But the same url in the Tricaster gives an error.

Where to debug…??

Kind regards,

Joshua

[Joshua_Rubingh]

Ok,

small summary:

Working:

FME to Wowza on a Windows Server

FME to Wowza on a Linux Server

TriCaster to Wowza on a Windows Server

Not Working

TriCaster to Wowza on a Linux Server

Also our customer is sending an inquiry to the Tricaster developer. Maybe they see something in there system.

Also we can look in the DEBUG file.

Thanks

[Superior_Productions]

Ok,

small summary:

Working:

FME to Wowza on a Windows Server

FME to Wowza on a Linux Server

TriCaster to Wowza on a Windows Server

Not Working

TriCaster to Wowza on a Linux Server

Also our customer is sending an inquiry to the Tricaster developer. Maybe they see something in there system.

Also we can look in the DEBUG file.

Thanks

I was having the same issue as you. I looked in the log file, and noticed that Tricaster had converted the stream path to all lowercase letters.

Changed all my conf and application directories to lowercase, and everything worked.