No compatible codecs, not accepting this offer!

i install frepbx14 Distro .asterisk 13
when i make call between tow softphones (103-104)on desktop using a-law
i see (faile call)
[2020-11-08 17:27:13] NOTICE[2021][C-00000000]: chan_sip.c:10877 process_sdp: No compatible codecs, not accepting this offer!

{sip debug}
SIP Debugging enabled

<— SIP read from UDP:192.168.1.3:48422 —>

<------------->
Really destroying SIP dialog ‘eNbsh4WUSlXB6-gj5I9yDg…’ Method: REGISTER
Reliably Transmitting (no NAT) to 192.168.1.3:57534:
OPTIONS sip:[email protected]:57534;rinstance=6bceed08f8a43117;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK0144a0ea
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as4d019045
To: sip:[email protected]:57534;rinstance=6bceed08f8a43117;transport=UDP
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.3.1(13.19.1)
Date: Sun, 08 Nov 2020 15:34:13 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— SIP read from UDP:192.168.1.3:57534 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK0144a0ea
Contact: sip:192.168.1.3:57534
To: sip:[email protected]:57534;rinstance=6bceed08f8a43117;transport=UDP;tag=607e9554
From: “Unknown” sip:[email protected];tag=as4d019045
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Accept: application/sdp, application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Z 3.7.30891 r30851
Allow-Events: presence, kpml
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.3:48422 —>
REGISTER sip:192.168.1.6:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.3:48422;branch=z9hG4bK-524287-1—45b8ce5fef074031;rport
Max-Forwards: 70
Contact: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP
To: sip:[email protected]:5060;transport=UDP
From: sip:[email protected]:5060;transport=UDP;tag=de3c387b
Call-ID: eNbsh4WUSlXB6-gj5I9yDg…
CSeq: 86 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Z 5.2.28 rv2.8.115
Authorization: Digest username=“103”,realm=“asterisk”,nonce=“7ff25cd5”,uri=“sip:192.168.1.6:5060;transport=UDP”,response=“82c8eebd021205a871db7ee74543ca5c”,algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 192.168.1.3:48422 (no NAT)
Sending to 192.168.1.3:48422 (no NAT)

<— Transmitting (no NAT) to 192.168.1.3:48422 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.3:48422;branch=z9hG4bK-524287-1—45b8ce5fef074031;received=192.168.1.3;rport=48422
From: sip:[email protected]:5060;transport=UDP;tag=de3c387b
To: sip:[email protected]:5060;transport=UDP;tag=as17b66e46
Call-ID: eNbsh4WUSlXB6-gj5I9yDg…
CSeq: 86 REGISTER
Server: FPBX-14.0.3.1(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“2e75a5b6”
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘eNbsh4WUSlXB6-gj5I9yDg…’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:192.168.1.3:48422 —>
REGISTER sip:192.168.1.6:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.3:48422;branch=z9hG4bK-524287-1—52c943ceec4564b9;rport
Max-Forwards: 70
Contact: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP
To: sip:[email protected]:5060;transport=UDP
From: sip:[email protected]:5060;transport=UDP;tag=de3c387b
Call-ID: eNbsh4WUSlXB6-gj5I9yDg…
CSeq: 87 REGISTER
Expires: 60
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
User-Agent: Z 5.2.28 rv2.8.115
Authorization: Digest username=“103”,realm=“asterisk”,nonce=“2e75a5b6”,uri=“sip:192.168.1.6:5060;transport=UDP”,response=“da3b766fd129c1fdfc495ceb424a449a”,algorithm=MD5
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Sending to 192.168.1.3:48422 (no NAT)
Reliably Transmitting (no NAT) to 192.168.1.3:48422:
OPTIONS sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK346e4cb6
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as570acceb
To: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-14.0.3.1(13.19.1)
Date: Sun, 08 Nov 2020 15:34:18 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<— Transmitting (no NAT) to 192.168.1.3:48422 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.3:48422;branch=z9hG4bK-524287-1—52c943ceec4564b9;received=192.168.1.3;rport=48422
From: sip:[email protected]:5060;transport=UDP;tag=de3c387b
To: sip:[email protected]:5060;transport=UDP;tag=as17b66e46
Call-ID: eNbsh4WUSlXB6-gj5I9yDg…
CSeq: 87 REGISTER
Server: FPBX-14.0.3.1(13.19.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP;expires=60
Date: Sun, 08 Nov 2020 15:34:18 GMT
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘[email protected]:5060’ in 6400 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.1.3:48422:
NOTIFY sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK4a676c7f
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as50f35560
To: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-14.0.3.1(13.19.1)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 86

Messages-Waiting: no
Message-Account: sip:*[email protected]
Voice-Message: 0/0 (0/0)


Scheduling destruction of SIP dialog ‘eNbsh4WUSlXB6-gj5I9yDg…’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:192.168.1.3:48422 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK346e4cb6
Contact: sip:192.168.1.3:48422
To: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP;tag=a2047e46
From: “Unknown” sip:[email protected];tag=as570acceb
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Accept: application/sdp, application/sdp
Accept-Language: en
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Z 5.2.28 rv2.8.115
Allow-Events: presence, kpml, talk
Content-Length: 0

<------------->
— (14 headers 0 lines) —
Really destroying SIP dialog ‘[email protected]:5060’ Method: OPTIONS

<— SIP read from UDP:192.168.1.3:48422 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK4a676c7f
Contact: sip:192.168.1.3:48422
To: sip:[email protected]:48422;rinstance=908d2dfe215b4a56;transport=UDP;tag=ad213101
From: “Unknown” sip:[email protected];tag=as50f35560
Call-ID: [email protected]:5060
CSeq: 102 NOTIFY
User-Agent: Z 5.2.28 rv2.8.115
Content-Length: 0

<------------->
— (9 headers 0 lines) —
Really destroying SIP dialog ‘[email protected]:5060’ Method: NOTIFY

[sip .config]
[103]
deny=0.0.0.0/0.0.0.0
secret=333
dtmfmode=rfc2833
canreinvite=no
context=from-internal
host=dynamic
defaultuser=
trustrpid=yes
sendrpid=pai
type=friend
session-timers=accept
nat=no
port=5060
qualify=yes
qualifyfreq=60
transport=udp
avpf=no
force_avp=no
icesupport=no
rtcp_mux=no
encryption=no
namedcallgroup=
namedpickupgroup=
dial=SIP/103
mailbox=103@default
permit=0.0.0.0/0.0.0.0
callerid=extension 103 <103>
callcounter=yes
faxdetect=no
cc_monitor_policy=generic

[104]
deny=0.0.0.0/0.0.0.0
secret=444
dtmfmode=rfc2833
canreinvite=no
context=from-internal
host=dynamic
defaultuser=
trustrpid=yes
sendrpid=pai
type=friend
session-timers=accept
nat=no
port=5060
qualify=yes
qualifyfreq=60
transport=udp
avpf=no
force_avp=no
icesupport=no
rtcp_mux=no
encryption=no
namedcallgroup=
namedpickupgroup=
dial=SIP/104
mailbox=104@default
permit=0.0.0.0/0.0.0.0
callerid=extension 104 <104>
callcounter=yes
faxdetect=no
cc_monitor_policy=generic

Unfortunately, the SIP debug posted does not contain the INVITEs and responses that would help debug the problem.

With SIP debugging enabled, make a failing test call between the extensions. Paste the Asterisk log for the call (which will include the SIP trace) at pastebin.freepbx.org and post the link here.

If this is a new installation, I’m curious why you chose relatively old versions of FreePBX and Asterisk. If it’s something that just started failing, please provide details.

Do I change asterisk from 13 to 15 or 16?

For a new system, I recommend installing the Distro, which avoids many possible inconsistencies.


If your platform is incompatible, please provide details.

However, feel free to paste the Asterisk log for a failed call on your existing system; we’ll try to see what’s wrong.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.