[Freeswitch-users] Problem with flex client connecting to mod_rtmp

Peter Steinbach lists at telefaks.de
Tue Aug 7 14:26:31 MSD 2012


Hello Antonio,

I added this:
> var params  = {
> allowScriptAccess: 'always'
> };

and removed the /phone from the URL. This did not change anything. Log
is still like this:

2012-08-07 11:56:48.105667 [NOTICE] mod_rtmp.c:744 New RTMP session
[b31edb8a-50d3-4100-9b7f-ab49b6ba06b5]
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:702 Sent handshake response
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:727 Done with handshake
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:892 [chunk_stream=3 type=0x14
ts=0 stream_id=0x0] len=331
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:170 [amfnumber=3] Got INVOKE
for connect
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=2 type=0x1
stream_id=0x0] len=4
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=2 type=0x5
stream_id=0x0] len=4
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=2 type=0x6
stream_id=0x0] len=5
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=2 type=0x4
stream_id=0x0] len=6
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=3 type=0x14
stream_id=0x0] len=201
2012-08-07 11:56:48.205670 [DEBUG] rtmp.c:566 [amfnumber=3 type=0x14
stream_id=0x0] len=61
2012-08-07 11:56:48.205670 [NOTICE] rtmp_sig.c:121 Sent connect reply
2012-08-07 11:56:48.215667 [DEBUG] rtmp.c:892 [chunk_stream=2 type=0x5
ts=11917881 stream_id=0x0] len=4
2012-08-07 11:56:48.215667 [DEBUG] rtmp.c:945 Set window size: 131072 bytes

Ngrep on the traffic shows the following last packets starting with
connect: (192.168.178.103 is the PC, 192.168.178.220 is Freeswitch)
T 192.168.178.103:48179 -> 192.168.178.220:1935 [AP]
..............................................................................................K........connect.?..........app.....flashVer...LNX
11,2,202,236..swfUrl..,http://my.domain.com/flex/freeswitch.swf..tcUrl...rtmp:/./my.domain.com..fpad....capabilities.@m........audioCodecs.@.........videoCodecs.@o........videoFunction.?.........pageUrl....http://my.domain.com/flex/freeswitch.html#..objectEncoding............
##
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
............
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
....
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
............
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
....
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
............
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
.....
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
............
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
......
#
T 192.168.178.220:1935 -> 192.168.178.103:48179 [AP]
............
##
T 192.168.178.103:48179 -> 192.168.178.220:1935 [AP]
...9............
Then traffic stops.

The packet freeswitch answeres after the connect requests is (from
wireshark):
2.109254    192.168.178.220    192.168.178.220    1935   
192.168.178.103    36804    RTMP    Unknown (0x7) | Unknown (0xf3) |
Unknown (0x21) | Unknown (0x50) | Unknown (0xff)[Packet size limited
during capture]



With kind regards
Peter



Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list