OK then!
Looking at my call logs, it seems to mostly happen with one particular carrier. Can I set verbose_sdp=true in the bridge string? e.g. "[verbose_sdp=true]sofia/gateway/... "?

Thanks,
-Avi


On Tue, Sep 13, 2011 at 6:28 PM, Michael Collins <msc@freeswitch.org> wrote:
For the record, line #107 contains the codecs (and other stuff) that FS offered:

m=audio 16480 RTP/AVP 8 0 9 101 13

The "8 0 9 101 13" represent the codecs (and other stuff). What do those numbers mean? This wiki page has the list:

http://wiki.freeswitch.org/wiki/RTP_payload_list

The SDP spec says that for non-dynamic payload numbers you are NOT required to have the "a=rtpmap" lines. This makes sense because those payload numbers don't change meaning until you get up to 96 and higher. The issue is that some devices are broken and require the "a=rtpmap" lines for the payload types below number 96. The verbose_sdp chan var mentioned by KK tells FS to add all those a=rtpmap lines for the non-dynamic payload types. You should only set this var when absolutely necessary because those verbose SDP's can cause the packets to be larger than the allowable MTU size.

Dontcha just *love* SIP/SDP interop? :)

-MC 

On Tue, Sep 13, 2011 at 8:01 AM, Avi Marcus <avi@avimarcus.net> wrote:
I see a failed bridge to my second carrier. The  sip_local_sdp_str doesn't show PCMU in it - did FS not offer any codecs?

Can someone tell me what's going on here?

-Avi





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