Port 0 is absolutely correct its part of SOA and its rejected the media so it sends port 0 to reject it. Now the payload changing is odd but port zero is def. correct if its rejected. /b On Jan 20, 2012, at 12:55 PM, Roland Hänel wrote:
Hello Brian,
As I wrote, I was already aware of that. However I think it would make sense to improve the handling on the FS side because
- the response of FS is clearly faulty, if FS doesn't like the FB offer it could reject the call, but sending 200 OK with port 0 is incorrect. Especially when the SDP data in debugging is not the same as the data we see in the SIP packet
- though incorrect, the G722/16000 thing is not uncommon. According to some reports I googled Grandstream and others also misbehave in that way. Because FS is friendly, I'd suggest to answer the request for G722/16000 with G722/8000 and everything will probably just work out fine. By the way, the debugging output suggests that exactly this was the intent of the author - but there seems to be a bug that prevents this SDP from making it into the 200 OK packet.
Roland
-- Brian West FreeSWITCH Solutions, LLC Phone: +1 (918) 420-9266 Fax: +1 (918) 420-9267 brian@freeswitch.org http://www.freeswitch.org