These are chat archives for AxisCommunications/locomote-video-player

1st
Apr 2016
Alexander Olsson
@noseglid
Apr 01 2016 06:51
Caching perhaps. Or you’re not installing/reloading it from the correct place. Or there are even more ExternalInterface.call in the code.
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:52
i had to pull the source into my test project to get it to stop doing it, probably an IntelliJ compiler cache or something
Alexander Olsson
@noseglid
Apr 01 2016 06:53
Switch to Atom :elephant:
Good you got it working
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:53
now just trying to get it to play an RTSP url streaming from VLC - I added a policy socket server but I never see any requests come from AS3, after I call play() it waits a few seconds and then sends a streamStopped event
RTMP url plays fine, tested one just to make sure the Player class was running correctly
Alexander Olsson
@noseglid
Apr 01 2016 06:54
RTMP is not subject to socket policy, which may indicate a socket policy issue.
But you should get a error callback then.
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:55
yea that's what I figured, and I'm not seeing any requests come from AS3 to the policy server
Alexander Olsson
@noseglid
Apr 01 2016 06:55
Is it running on port 843 ?
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:55
yea

$ python -c 'print "<policy-file-request/>"' | nc 127.0.0.1 843
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>

<!-- This is a master socket policy file -->

<!-- No other socket policies on the host will be permitted -->

<site-control permitted-cross-domain-policies="master-only"/>

<!-- Instead of setting to-ports="*", administrator's can use ranges and commas -->

<!-- This will allow access to ports 123, 456, 457 and 458 -->

<allow-access-from domain="*" to-ports="*" />

</cross-domain-policy>

i tested it like that from the cli
Alexander Olsson
@noseglid
Apr 01 2016 06:56
Networking issues?
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:57
AIR app and VLC are both running on same computer
Alexander Olsson
@noseglid
Apr 01 2016 06:57
Odd, and how are you specifying the RTSP url?
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:57
i've tried "rtsp://:8554/" and "rtsp://192.168.1.11:8554/"
Alexander Olsson
@noseglid
Apr 01 2016 06:58
Is your socketpolicy server listening to all your interfaces (e.g. not only 127.0.0.1). If you do above test but use IP 192.168.1.11 instead
Omar Gonzalez
@s9tpepper
Apr 01 2016 06:58
let me tr
oh, it won't work w/ that IP
that's weird, ipconfig says IPv4 is 192.168.1.11
Alexander Olsson
@noseglid
Apr 01 2016 07:17
How are you starting the socketpolicy server?
My bet is it’s only listening to 127.0.0.1 (e.g. the loopback interface) and not the interface with ip 192.168.1.11
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:18
it's a PHP script, one sec
i'll try that, right now its using: socket_bind($socket, 'localhost', 843
Alexander Olsson
@noseglid
Apr 01 2016 07:18
change ’localhost’ to ’0.0.0.0’
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:20
cool yea that works, i was adding some event handlers and output window so I can try to get more info when its stopping or the other calls it makes
Alexander Olsson
@noseglid
Apr 01 2016 07:20
cool
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:20
appreciate the help
Alexander Olsson
@noseglid
Apr 01 2016 07:20
Not a problem
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:29
hm, still only sending streamStopped and no calls to the socket policy
Alexander Olsson
@noseglid
Apr 01 2016 07:29
Does it work with that IP now using nc ?
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:30

$ python -c 'print "<policy-file-request/>"' | nc 192.168.1.11 843
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>
<allow-access-from domain="*" to-ports="*" />
</cross-domain-policy

ya, i simplified the policy too
Alexander Olsson
@noseglid
Apr 01 2016 07:30
Could you pipe that response through hexdump and paste the output ?
Please surround it with three backticks
To get
code like this
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:31
let me try that, never used hexdump before one sec
0000000 3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 0000010 2e 30 22 3f 3e 0d 0a 3c 21 44 4f 43 54 59 50 45 0000020 20 63 72 6f 73 73 2d 64 6f 6d 61 69 6e 2d 70 6f 0000030 6c 69 63 79 20 53 59 53 54 45 4d 20 22 2f 78 6d 0000040 6c 2f 64 74 64 73 2f 63 72 6f 73 73 2d 64 6f 6d 0000050 61 69 6e 2d 70 6f 6c 69 63 79 2e 64 74 64 22 3e 0000060 0d 0a 3c 63 72 6f 73 73 2d 64 6f 6d 61 69 6e 2d 0000070 70 6f 6c 69 63 79 3e 20 0d 0a 20 20 20 3c 61 6c 0000080 6c 6f 77 2d 61 63 63 65 73 73 2d 66 72 6f 6d 20 0000090 64 6f 6d 61 69 6e 3d 22 2a 22 20 74 6f 2d 70 6f 00000a0 72 74 73 3d 22 2a 22 20 2f 3e 0d 0a 3c 2f 63 72 00000b0 6f 73 73 2d 64 6f 6d 61 69 6e 2d 70 6f 6c 69 63 00000c0 79 3e 0d 0a 0d 0a 00 00000c7
i tried three ``` in front and in the end
0000000 3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31
0000010 2e 30 22 3f 3e 0d 0a 3c 21 44 4f 43 54 59 50 45
0000020 20 63 72 6f 73 73 2d 64 6f 6d 61 69 6e 2d 70 6f
0000030 6c 69 63 79 20 53 59 53 54 45 4d 20 22 2f 78 6d
0000040 6c 2f 64 74 64 73 2f 63 72 6f 73 73 2d 64 6f 6d
0000050 61 69 6e 2d 70 6f 6c 69 63 79 2e 64 74 64 22 3e
0000060 0d 0a 3c 63 72 6f 73 73 2d 64 6f 6d 61 69 6e 2d
0000070 70 6f 6c 69 63 79 3e 20 0d 0a 20 20 20 3c 61 6c
0000080 6c 6f 77 2d 61 63 63 65 73 73 2d 66 72 6f 6d 20
0000090 64 6f 6d 61 69 6e 3d 22 2a 22 20 74 6f 2d 70 6f
00000a0 72 74 73 3d 22 2a 22 20 2f 3e 0d 0a 3c 2f 63 72
00000b0 6f 73 73 2d 64 6f 6d 61 69 6e 2d 70 6f 6c 69 63
00000c0 79 3e 0d 0a 0d 0a 00                           
00000c7
Alexander Olsson
@noseglid
Apr 01 2016 07:33
That’s what it should be. You see the little M and an arrow down next to the input field. Click that and you get formatting tips
There we go!
Yea so it ends in 00, which is correct.
Omar Gonzalez
@s9tpepper
Apr 01 2016 07:36
the request never even gets to the server right now, cause I'm outputting this when I call it from cli:

Client Resource id #11 connected!

<policy-file-request/>

Omar Gonzalez
@s9tpepper
Apr 01 2016 08:34
seems to be an issue with the RTSP stream itself, I used the rtsp stream from the demo earlier in the chat and that one works but the ones I tried from VLC and one from Wowza wouldn't work
Alexander Olsson
@noseglid
Apr 01 2016 08:35
Do you get any error callbacks?
Omar Gonzalez
@s9tpepper
Apr 01 2016 08:35
with the ones that dont work, one sec Im getting lots of output now
[trace] RTSP OUT: OPTIONS * RTSP/1.0
[trace] CSeq: 2
[trace] User-Agent: Locomote
[trace] RTSP IN:
[trace] RTSPClient: STATE_OPTIONS
[trace] RTSP OUT: DESCRIBE rtsp://192.168.1.11/ RTSP/1.0
[trace] CSeq: 3
[trace] User-Agent: Locomote
[trace] Accept: application/sdp
[trace] RTSP IN: v=0
[trace] o=- 15756038290400035918 15756038290400035918 IN IP4 WIN-NID0KIK2V7S
[trace] s=Unnamed
[trace] i=N/A
[trace] c=IN IP4 0.0.0.0
[trace] t=0 0
[trace] a=tool:vlc 2.2.2
[trace] a=recvonly
[trace] a=type:broadcast
[trace] a=charset:UTF-8
[trace] a=control:rtsp://192.168.1.11:8554/
[trace] m=audio 0 RTP/AVP 14
[trace] b=AS:128
[trace] b=RR:0
[trace] a=rtpmap:14 MPA/90000/2
[trace] a=control:rtsp://192.168.1.11:8554/trackID=0
[trace] m=video 0 RTP/AVP 96
[trace] b=RR:0
[trace] a=rtpmap:96 H264/90000
[trace] a=fmtp:96 packetization-mode=1;profile-level-id=64001f;sprop-parameter-sets=Z2QAH6zZQPAW7ARAAosKwExLQCPGDGWA,aOvjyyLA;
[trace] a=control:rtsp://192.168.1.11:8554/trackID=1
[trace] RTSPClient: STATE_DESCRIBE
[trace] v=0
[trace] o=- 15756038290400035918 15756038290400035918 IN IP4 WIN-NID0KIK2V7S
[trace] s=Unnamed
[trace] i=N/A
[trace] c=IN IP4 0.0.0.0
[trace] t=0 0
[trace] a=tool:vlc 2.2.2
[trace] a=recvonly
[trace] a=type:broadcast
[trace] a=charset:UTF-8
[trace] a=control:rtsp://192.168.1.11:8554/
[trace] m=audio 0 RTP/AVP 14
[trace] b=AS:128
[trace] b=RR:0
[trace] a=rtpmap:14 MPA/90000/2
[trace] a=control:rtsp://192.168.1.11:8554/trackID=0
[trace] m=video 0 RTP/AVP 96
[trace] b=RR:0
[trace] a=rtpmap:96 H264/90000
[trace] a=fmtp:96 packetization-mode=1;profile-level-id=64001f;sprop-parameter-sets=Z2QAH6zZQPAW7ARAAosKwExLQCPGDGWA,aOvjyyLA;
[trace] a=control:rtsp://192.168.1.11:8554/trackID=1
[trace] Ignored unknown SDP directive: i=N/A
[trace] Ignored unknown SDP directive: c=IN IP4 0.0.0.0
[trace] Ignored unknown SDP directive: b=AS:128
[trace] Ignored unknown SDP directive: b=RR:0
[trace] Ignored unknown SDP directive: b=RR:0
[trace] SDP contained 2 track(s). Calling SETUP for each.
[trace] RTSPClient: STATE_SETUP
[trace] undefined
[trace] Setting up track: rtsp://192.168.1.11:8554/trackID=0
[trace] RTSP OUT: SETUP rtsp://192.168.1.11:8554/trackID=0 RTSP/1.0
[trace] CSeq: 4
[trace] User-Agent: Locomote
[trace] Transport: RTP/AVP/TCP;unicast;interleaved=0-1
[trace] Date: Fri Apr 1 08:35:36 2016 UTC
[trace] RTSP IN:
it dumps that and gets stuck at that RTSP IN:
then eventually sends:
[trace] RTSP stream timed out [object Object]
[trace] RTSP stream closed [object Object]