Streaming h.264 to a G5 panel - URI format
markh
Junior Member
Hi All,
I have an Avigilon h.264 camera but it requires basic HTTP auth. In VLC I can enter the URI in the form
rtsp://USERNAME:PASSWORD@192.168.41.10/defaultPrimary?streamType=u
and it works a treat. The same URI format entered into TPDesign5 does not.
I can see when i telnet into the panel and use "msg on" that the panel is trying to connect by throwing away the USERNAME:PASSWORD part of the URI, but does not then respond with the auth options.
12-19 06:45:21.104 2109 21439 I OMXPlayer: --
12-19 06:45:21.104 2109 21439 I OMXPlayer: Sending:
12-19 06:45:21.104 2109 21439 I OMXPlayer: OPTIONS rtsp://192.168.41.10:554/defaultPrimary?streamType=u RTSP/1.0
12-19 06:45:21.104 2109 21439 I OMXPlayer: CSeq: 1
12-19 06:45:21.104 2109 21439 I OMXPlayer:
12-19 06:45:21.104 2109 21439 I OMXPlayer:
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='RTSP/1.0 401 Unauthorized'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='WWW-Authenticate: Digest realm="101504222611", nonce="eXkhnxj3k9av48654OfhOXVTOT2O0owd34l1wsb30a0000", charset=utf-8, qop="auth"'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='CSeq: 1'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='Content-Length: 0'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='Date: Thu, 01 Jan 1970 00:45:39 GMT'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line=''
12-19 06:45:21.134 2109 21439 I OMXPlayer: --
I've done a Wireshark capture of the VLC interraction, and when it gets the same response (RTSP/1.0 401 Unauthorised) it then responds with the auth options and all is good.
So what I'm really wondering if there is a different format for entering user/pass that the panel will understand and use correctly. Any ideas anyone?
Page 137 of the Modero.G5.Programming.Configuration.Guide.pdf has a disclaimer at the bottom of the page:
"NOTE: Third-party encoders and digital television devices have not been tested with ModeroX Series G5 touch panels, and are not supported by AMX."
So I am also wondering if I've been sold a lemon in this case.
any comments or help greatly appreciated
thanks
Mark
I have an Avigilon h.264 camera but it requires basic HTTP auth. In VLC I can enter the URI in the form
rtsp://USERNAME:PASSWORD@192.168.41.10/defaultPrimary?streamType=u
and it works a treat. The same URI format entered into TPDesign5 does not.
I can see when i telnet into the panel and use "msg on" that the panel is trying to connect by throwing away the USERNAME:PASSWORD part of the URI, but does not then respond with the auth options.
12-19 06:45:21.104 2109 21439 I OMXPlayer: --
12-19 06:45:21.104 2109 21439 I OMXPlayer: Sending:
12-19 06:45:21.104 2109 21439 I OMXPlayer: OPTIONS rtsp://192.168.41.10:554/defaultPrimary?streamType=u RTSP/1.0
12-19 06:45:21.104 2109 21439 I OMXPlayer: CSeq: 1
12-19 06:45:21.104 2109 21439 I OMXPlayer:
12-19 06:45:21.104 2109 21439 I OMXPlayer:
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='RTSP/1.0 401 Unauthorized'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='WWW-Authenticate: Digest realm="101504222611", nonce="eXkhnxj3k9av48654OfhOXVTOT2O0owd34l1wsb30a0000", charset=utf-8, qop="auth"'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='CSeq: 1'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='Content-Length: 0'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line='Date: Thu, 01 Jan 1970 00:45:39 GMT'
12-19 06:45:21.134 2109 21439 I OMXPlayer: line=''
12-19 06:45:21.134 2109 21439 I OMXPlayer: --
I've done a Wireshark capture of the VLC interraction, and when it gets the same response (RTSP/1.0 401 Unauthorised) it then responds with the auth options and all is good.
So what I'm really wondering if there is a different format for entering user/pass that the panel will understand and use correctly. Any ideas anyone?
Page 137 of the Modero.G5.Programming.Configuration.Guide.pdf has a disclaimer at the bottom of the page:
"NOTE: Third-party encoders and digital television devices have not been tested with ModeroX Series G5 touch panels, and are not supported by AMX."
So I am also wondering if I've been sold a lemon in this case.
any comments or help greatly appreciated
thanks
Mark
Comments
-
How are you entering it in TPD5? In TPD5 > Panel > Resource Manager > Dynamic Images or
TPD5 > click on the button for video fill > Button Properties > STATE > Video Fill > select "Streaming Video" and entering the URI in "Streaming Source below.
I've never used TPD5 or this 2nd video fill method but I seem to recollect hearing something about this once upon a time. -
I decided to try via button properties and it does work, at least on my MXT-1000 G4, using TPD4.
Older Axis Network Camsrtsp://user:pass@192.168.1.52/mpeg4/media.amp
Newer Axis Network Camsrtsp://user:pass@192.168.1.52/axis-media/media.amp
So it does work on an axis camera using button properties Video Fill: Steaming Video and putting that URI in Streaming Source.
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums
