Thanks!
Looks to me like you may be talking about this one sent to the server:
1 0 0 20071025 0 guest:guest
And receiving this from the server:
1 0 6592xxxx 0 0 Guestxxxxx
Where 6592xxxx is the session ID, is that right?
Ok, so far so good then!
Now for something else. Having objectEncoding appended to PageUrl seems important, right?
I´ve tried alot of different things, but cannot make it occur in the same way as done in the packets sniffed from an mfc session:
Code:
0x0200 74 6F 72 79 3D 74 72 75-65 26 77 69 64 74 68 3D tory=true&width=
0x0210 C3 33 32 30 26 68 65 69-67 68 74 3D 32 34 30 26 ?320&height=240&
0x0220 6D 75 74 65 3D 6F 66 66-26 00 0E 6F 62 6A 65 63 mute=off&..objec
0x0230 74 45 6E 63 6F 64 69 6E-67 00 00 00 00 00 00 00 tEncoding.......
Not sure what this will look like, directly pasted from my packet monitor, but what it´s showing is that between mute=off& and objectEncoding, there´s two bytes with the values 0 and 0E (14).
How do I get those two bytes into RTMPDUMP?
Tried using -C but that added alot more...
If anybody´s using RTMPDUMP in a commandline, and had it working fine, could they perhaps share an example here?
Thanks!