Hi Brian,
Surely FS should tear down the call if the media is not suitable? I now see that 'G729a' does not conform to the IANA standard and is wrong.
Yeh, I've actually seen this issue before in proxy media mode with bad iana name flag enabled (which actually means fix specifically the string "g729a" to "g729") where the 200 OK or 183 response with SDP gets broken on the way back. By broken the SDP on the response to the B leg changes to dynamic payload type 96 and rtp port 0 instead of payload type 18/non-zero rtp port.
There's something I think in the sofia libs which is validating the SDP - even though technically in proxy media mode the codec list should just get passed through. I haven't yet found exactly where this is yet.
Let me get the m attribute fixed in the SDP & I will let you know.
With the correct iana name in the rtpmap then I think
your problem will go away, assuming you control the endpoints in your environment and can change them to
originate the call with the correct iana name in the rtpmap then I think
your problem will go away.
Or you could turn on full media mode too which would solve it but you just need to be careful with codec negotiation at that point.
Thanks for the input.
Regards,
Michael
Its not a bug. zero is an indication that we rejected the media.
/b
On Oct 31, 2011, at 6:07 AM, Michael Toop wrote:
Hi,
Is there someone in the list interested in some consulting work to assist
me to get to the bottom of this problem?
Happy to pay for assistance here.
Thanks,
Michael
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