Received SAVPF Profle In Audio Offer But AVPF Is Not Enabled

Home » Asterisk Users » Received SAVPF Profle In Audio Offer But AVPF Is Not Enabled
Asterisk Users 7 Comments

Dear All,

I use sipml5 to register two users from browser and the two clients are successfully connected. But when I made a call from one of the users, the other user doen’st have call notification and for a while the calling process ended. I check the /var/log/asterisk/messages got the following log:

[Dec 17 14:54:11] WARNING[11471][C-00000000] chan_sip.c: Received SAVPF
profle in audio offer but AVPF is not enabled: audio 52760 RTP/SAVPF 103
104 0 8 107 106 105 13 126
[Dec 17 14:54:11] WARNING[11471][C-00000000] chan_sip.c: Received SAVPF
profle in video offer but AVPF is not enabled: video 52760 RTP/SAVPF 100
101 102
[Dec 17 14:54:11] WARNING[11471][C-00000000] chan_sip.c: Insufficient information in SDP (c=)…

I already compile the asterisk with configuration option “–with-srtp”.

Could you please indicate what problem is?

Thank you!
barco

7 thoughts on - Received SAVPF Profle In Audio Offer But AVPF Is Not Enabled

  • I’m trying to call from DruCall to Asterisk and I get this error:

    WARNING[11021]: chan_sip.c:8687 process_sdp: Error in codec string ‘F
    103 104 111 0 8 107 106 105 13 126’
    == Problem setting up ssl connection:
    error:00000000:lib(0):func(0):reason(0)

    I’m guessing my Asterisk is too old (it is 1.8 from Debian). Can you confirm which version is needed to parse a media descriptor with SAVPF?
    Do I need to upgrade all the way to v11 with WebRTC support, or was avpf support added in some intermediate version?

    Also, I’m using a SIP proxy and it takes care of handling all the WebRTC
    connections and proxying the requests into a normal TCP/TLS connection to Asterisk. I was hoping to avoid opening up WebRTC access directly on Asterisk. One effect this has is that I can’t control the `avpf=yes’
    setting on a per-peer basis, as the proxy is carrying requests from various types of peer, some public, some private. Is there any outright reason Asterisk can’t support (S)AVPF on demand?

  • Daniel Pocock wrote:

    Asterisk 1.8 does not have any knowledge of AVPF, and since it’s a new feature it was only added to Asterisk 11. You could try to backport the changes but chan_sip has changed quite a bit, so it could be rough.

  • Thanks for the fast reply. I agree backporting full support for AVPF
    would not be justified for many use cases (including my own). What I
    was more curious about is whether the F can be tolerated (in other words, ignored or silently removed), as described here:

    http://www.ietf.org/mail-archive/web/rtcweb/current/msg01145.html
    “1) RTCWEB end-point will always signal AVPF or SAVPF. I signalling gateway to legacy will change that by removing the F to AVP or SAVP.”

    and whether such behavior is possible even without setting avpf=yes on a per-peer basis?

  • Daniel Pocock wrote:

    From a code perspective, it could. Still not something I would be comfortable with putting in Asterisk 1.8.

    This is fine for incoming but what about outgoing to a device?

  • Excellent question… I’ve seen one of my Polycom devices reboot itself each time it receives a raw SDP from WebRTC, so if such a hack is implemented, I’d guess that stripping the F is better than ignoring it.

  • Daniel Pocock wrote:

    Asterisk doesn’t forward SDP through, each leg is completely independent. Without configurability of avpf then if you call a device you have to either not offer it, offer it only, or offer both. Doing both will probably make many devices unhappy, as you have mentioned. So to have stuff really be functional you have to backport AVPF.

    Cheers,