PDA

View Full Version : Tandberg Video Streaming


MKVAZ
12-13-2004, 08:51 AM
Can anyone tell me if they have successfully been able to stream using the Tandberg 2500 ?

robertk
12-13-2004, 11:43 AM
Sure, works perfectly!

What kind of problems do you have?

//Robert

MKVAZ
12-15-2004, 02:23 PM
The problem I am having is that when you launch the stream via the web page, it appears to take, the Quick time comes up, but the video does not load nor play. I ensured I had proper software versions on both the Tandberg and the quicktime, and the correct broadcast IP set. This is not working on intranet nor internet.

Sean Lessman
12-16-2004, 08:06 AM
The problem I am having is that when you launch the stream via the web page, it appears to take, the Quick time comes up, but the video does not load nor play. I ensured I had proper software versions on both the Tandberg and the quicktime, and the correct broadcast IP set. This is not working on intranet nor internet.Try setting the streaming address on the video system to your specific PC address. If it works, its likely Multicast is not enabled on the network. I know it works, I was doing it yesterday by streaming A Christmas Story from my codec on the LAN :)

You can also go directly into QuickTime and open a 'new URL' and type in http://yourcodecIP/stream.sdp.

Sean

MKVAZ
12-16-2004, 12:49 PM
Thanks, I'll try that.

robertk
12-17-2004, 07:14 AM
You can also go directly into QuickTime and open a 'new URL' and type in http://yourcodecIP/stream.sdp.

It will not work on a MXP codec. Atleast not with F1.4 SW.

The Mime-type is not presented correctly from the MXP codec for the stream.sdp file:

On a Classic 880:

~$ lynx --head http://ipnumberof880codec/stream.sdp
HTTP/1.1 200 Document Follows
Content-type: application/sdp
Expires: 0
Pragma: no-cache
Cache-Control: no-cache
Content-length: 199


On a MXP:

~$ lynx --head http://ipnumberofMXPcodec/stream.sdp
HTTP/1.0 200 OK
Pragma: no-cache
Content-Type: text/html
Content-Length: 200

----------------------------------------------------------------------

This should be solved in the next MXP release from TANDBERG. Atleast that's what R&D promised :^)

//Robert

robertk
12-17-2004, 07:17 AM
Another thing to check is that the TTL(Time To Live) settings on the streaming packets, is configured accordingly to as many routers you have to pass trough.

I belive 1 is default.

If you have 2 routers between your computer and your Tandberg it will fail.

By increasing the number, you can solve this issue.


//Robert

Sean Lessman
12-17-2004, 09:51 AM
It will not work on a MXP codec. Atleast not with F1.4 SW.

The Mime-type is not presented correctly from the MXP codec for the stream.sdp file:

On a Classic 880:

~$ lynx --head http://ipnumberof880codec/stream.sdp
HTTP/1.1 200 Document Follows
Content-type: application/sdp
Expires: 0
Pragma: no-cache
Cache-Control: no-cache
Content-length: 199


On a MXP:

~$ lynx --head http://ipnumberofmxpcodec/stream.sdp
HTTP/1.0 200 OK
Pragma: no-cache
Content-Type: text/html
Content-Length: 200

----------------------------------------------------------------------

This should be solved in the next MXP release from TANDBERG. Atleast that's what R&D promised :^)

//Robert
Interesting. Works in my office.

Sean

robertk
12-17-2004, 10:53 AM
Sorry,

I was also going to say that this is only NOT working if you enter the URL in a Web-browser.

So try entering http://yourcodecIP/stream.sdp into your IE instead.

//Robert

robertk
12-21-2004, 02:55 PM
The R&D guys at Tandberg has fixed the MIME-bug in F1.5, thanks.

//Robert