Response 406 "Not Acceptable" from SPA-3102

Just noticed yesterday that if someone calls me with caller ID blocked my device (SPA-3102) is not accepting the call and it goes straight to voicemail. Calls with callerID work fine.

Product Name: SPA-3102
Software Version: 5.1.7(GW)

[2014-04-04 14:54:53] VERBOSE[31537][C-00000040] app_dial.c: – Called SIP/6000
[2014-04-04 14:54:53] VERBOSE[1850][C-00000040] chan_sip.c: – Got SIP response 406 “Not Acceptable” back from 192.168.1.211:5060

As a test, I redirected my incoming route to my polycom and it works properly.

Anyone noticed this before? It’s almost a feature :slight_smile:

Opps -
Distro version 5.211.65-8
All modules updated to latest (as of today)

Here is the debug trace of the call. The problem started when I rebuilt to the latest stable distro. I had one of the very early ones. I’m guessing it is more a setting change than a real problem, but I don’t quite know how to address it. It is for my home phone system. I saved the old disk, so I guess I could put it back and try a debug trace as well.

Also, I didn’t change anything on the SPA. But of course, that doesn’t mean it was always correct either…

IP Debugging Enabled for IP: 192.168.1.211
Audio is at 17698
Adding codec 100003 (ulaw) to SDP
Adding codec 100004 (alaw) to SDP
Adding codec 100002 (gsm) to SDP
Adding non-codec 0x1 (telephone-event) to SDP
Reliably Transmitting (no NAT) to 192.168.1.211:5060:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK0b05e453
Max-Forwards: 70
From: “Anonymous” sip:[email protected];tag=as093b4989
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 INVITE
User-Agent: FPBX-2.11.0(11.8.1)
Date: Thu, 10 Apr 2014 12:47:19 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 280

v=0
o=root 730868077 730868077 IN IP4 192.168.1.50
s=Asterisk PBX 11.8.1
c=IN IP4 192.168.1.50
t=0 0
m=audio 17698 RTP/AVP 0 8 3 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv


<— SIP read from UDP:192.168.1.211:5060 —>
SIP/2.0 100 Trying
To: sip:[email protected]:5060
From: “Anonymous” sip:[email protected];tag=as093b4989
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK0b05e453
Server: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:192.168.1.211:5060 —>
SIP/2.0 406 Not Acceptable
To: sip:[email protected]:5060;tag=2f376a6ef6601c46i0
From: “Anonymous” sip:[email protected];tag=as093b4989
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK0b05e453
Server: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0

<------------->
— (8 headers 0 lines) —
Transmitting (no NAT) to 192.168.1.211:5060:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK0b05e453
Max-Forwards: 70
From: “Anonymous” sip:[email protected];tag=as093b4989
To: sip:[email protected]:5060;tag=2f376a6ef6601c46i0
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 ACK
User-Agent: FPBX-2.11.0(11.8.1)
Content-Length: 0


Really destroying SIP dialog ‘[email protected]:5060’ Method: INVITE

<— SIP read from UDP:192.168.1.211:5060 —>
REGISTER sip:192.168.1.50 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.211:5060;branch=z9hG4bK-61b65
From: 6000 sip:[email protected];tag=562f544e7463be6o0
To: 6000 sip:[email protected]
Call-ID: [email protected]
CSeq: 34932 REGISTER
Max-Forwards: 70
Authorization: Digest username=“6000”,realm=“asterisk”,nonce=“75d4897b”,uri=“sip:192.168.1.50”,algorithm=MD5,response="8094712fabf0531af97334e05188f8ef"
Contact: 6000 sip:[email protected]:5060;expires=60
User-Agent: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces

<------------->
— (13 headers 0 lines) —
Sending to 192.168.1.211:5060 (NAT)
Sending to 192.168.1.211:5060 (NAT)

<— Transmitting (no NAT) to 192.168.1.211:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.211:5060;branch=z9hG4bK-61b65;received=192.168.1.211
From: 6000 sip:[email protected];tag=562f544e7463be6o0
To: 6000 sip:[email protected];tag=as2c36598b
Call-ID: [email protected]
CSeq: 34932 REGISTER
Server: FPBX-2.11.0(11.8.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="28f0a38d"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘[email protected]’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:192.168.1.211:5060 —>
REGISTER sip:192.168.1.50 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.211:5060;branch=z9hG4bK-ff61d0c6
From: 6000 sip:[email protected];tag=562f544e7463be6o0
To: 6000 sip:[email protected]
Call-ID: [email protected]
CSeq: 34933 REGISTER
Max-Forwards: 70
Authorization: Digest username=“6000”,realm=“asterisk”,nonce=“28f0a38d”,uri=“sip:192.168.1.50”,algorithm=MD5,response="397d3181a7775b16d308048f6f83a312"
Contact: 6000 sip:[email protected]:5060;expires=60
User-Agent: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces

<------------->
— (13 headers 0 lines) —
Sending to 192.168.1.211:5060 (no NAT)
Reliably Transmitting (no NAT) to 192.168.1.211:5060:
OPTIONS sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK128fea4b
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as46640209
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
User-Agent: FPBX-2.11.0(11.8.1)
Date: Thu, 10 Apr 2014 12:47:29 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<— Transmitting (no NAT) to 192.168.1.211:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.211:5060;branch=z9hG4bK-ff61d0c6;received=192.168.1.211
From: 6000 sip:[email protected];tag=562f544e7463be6o0
To: 6000 sip:[email protected];tag=as2c36598b
Call-ID: [email protected]
CSeq: 34933 REGISTER
Server: FPBX-2.11.0(11.8.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 60
Contact: sip:[email protected]:5060;expires=60
Date: Thu, 10 Apr 2014 12:47:29 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.211:5060:
NOTIFY sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK7f201da0
Max-Forwards: 70
From: “Unknown” sip:[email protected];tag=as17422c71
To: sip:[email protected]:5060
Contact: sip:[email protected]:5060
Call-ID: [email protected]:5060
CSeq: 102 NOTIFY
User-Agent: FPBX-2.11.0(11.8.1)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 88

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


Scheduling destruction of SIP dialog ‘[email protected]’ in 32000 ms (Method: REGISTER)

<— SIP read from UDP:192.168.1.211:5060 —>
SIP/2.0 200 OK
To: sip:[email protected]:5060;tag=2f376a6ef6601c46i0
From: “Unknown” sip:[email protected];tag=as46640209
Call-ID: [email protected]:5060
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK128fea4b
Server: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces

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

<— SIP read from UDP:192.168.1.211:5060 —>
SIP/2.0 200 OK
To: sip:[email protected]:5060;tag=2f376a6ef6601c46i0
From: “Unknown” sip:[email protected];tag=as17422c71
Call-ID: [email protected]:5060
CSeq: 102 NOTIFY
Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK7f201da0
Server: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0

<------------->
— (8 headers 0 lines) —

Good news. A little more google and found a solution.

Changed “Block ANC Setting” to “no” on the SPA and it now rings for anonymous calls.

Not sure how it worked before… or thinking about it, perhaps if it worked before.