Oh okay, it's just from your previous comment, it sounded like you said the opposite. I.e., if the other side offered 96, FS would listen on 96.
I don't actually have access to the box in question atm, I'm getting this issue second hand. You wouldn't happen to know roughly when this was changed (which you seem to be implying)? The box is definitely running a much older version maybe 1.0.3 or 1.0.4 at the latest.
Dan
Yes thats how I read it... have you downloaded the latest freeswitch?/bOn Apr 5, 2010, at 4:54 PM, Dan Le wrote:Sorry to dig up an old thread, but ran into this same problem, and trying to understand the RFC as what is actually the expected behaviour.
So in the RFC (http://www.ietf.org/rfc/rfc3264.txt) in the Unicast Streams section:For sendrecv RTP
streams, the payload type numbers indicate the value of the payload
type field the offerer expects to receive, and would prefer to send
Doesn't that mean if they say 96 and FS says 101, they should be listening on 96 and FS should be listening on 101? Kinda like how ports work, you listen on the port that you offer.
Am I completely misinterpreting?
Thanks,
Dan
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org