Linksys spa3000 Host '<ip-address>:5060' does not implement 'REGISTER'


#1

I have a linksys spa3000 and I’m trying to get a sip trunk working with it in freepbx-13. The trunk will not work. The linksys is configured as ip 172.16.1.210 port 5060, freepbx is on 172.16.1.61 The error I get in the console is:
Host ‘172.16.1.210:5060’ does not implement 'REGISTER’
I’ve been carefully through the instructions at:
http://wiki.freepbx.org/pages/viewpage.action?pageId=55476525
and I’ve been trawling google but no luck so far.

This is a debug of the sip trunk:

REGISTER sip:172.16.1.210 SIP/2.0
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK191dde5f;rport
Max-Forwards: 70
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
To: <sip:2468@172.16.1.210>
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 178 REGISTER
User-Agent: FPBX-13.0.188.8(11.21.2)
Expires: 120
Contact: <sip:2468@172.16.1.61:5060>
Content-Length: 0


---
[2016-10-12 08:51:57] NOTICE[29815] chan_sip.c:    -- Registration for '2468@172.16.1.210' timed out, trying again (Attempt #77)
[2016-10-12 08:51:57] VERBOSE[29815] chan_sip.c: Really destroying SIP dialog '7355b21750348b285094ce4f7e3501d0@127.0.0.1' Method: REGISTER
[2016-10-12 08:51:57] VERBOSE[29815] chan_sip.c:
<--- SIP read from UDP:172.16.1.210:5060 --->
SIP/2.0 501 Not Implemented
To: <sip:2468@172.16.1.210>;tag=d260d6d8ee728a59i0
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 178 REGISTER
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK191dde5f
Server: Sipura/SPA3000-3.1.7(GWg)
Content-Length: 0

<------------->
[2016-10-12 08:51:57] VERBOSE[29815] chan_sip.c: --- (8 headers 0 lines) ---
[2016-10-12 08:51:57] WARNING[29815] chan_sip.c: Host '172.16.1.210:5060' does not implement 'REGISTER'
[2016-10-12 08:52:17] VERBOSE[29815] chan_sip.c: REGISTER 10 headers, 0 lines
[2016-10-12 08:52:17] VERBOSE[29815] chan_sip.c: Reliably Transmitting (NAT) to 172.16.1.210:5060:
REGISTER sip:172.16.1.210 SIP/2.0
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK3fad98f3;rport
Max-Forwards: 70
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
To: <sip:2468@172.16.1.210>
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 179 REGISTER
User-Agent: FPBX-13.0.188.8(11.21.2)
Expires: 120
Contact: <sip:2468@172.16.1.61:5060>
Content-Length: 0




---
[2016-10-12 08:52:17] NOTICE[29815] chan_sip.c:    -- Registration for '2468@172.16.1.210' timed out, trying again (Attempt #78)
[2016-10-12 08:52:17] VERBOSE[29815] chan_sip.c: Really destroying SIP dialog '7355b21750348b285094ce4f7e3501d0@127.0.0.1' Method: REGISTER
[2016-10-12 08:52:17] VERBOSE[29815] chan_sip.c:
<--- SIP read from UDP:172.16.1.210:5060 --->
SIP/2.0 501 Not Implemented
To: <sip:2468@172.16.1.210>;tag=d260d6d8ee728a59i0
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 179 REGISTER
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK3fad98f3
Server: Sipura/SPA3000-3.1.7(GWg)
Content-Length: 0

<------------->
[2016-10-12 08:52:17] VERBOSE[29815] chan_sip.c: --- (8 headers 0 lines) ---
[2016-10-12 08:52:17] WARNING[29815] chan_sip.c: Host '172.16.1.210:5060' does not implement 'REGISTER'
[2016-10-12 08:52:37] VERBOSE[29815] chan_sip.c: REGISTER 10 headers, 0 lines
[2016-10-12 08:52:37] VERBOSE[29815] chan_sip.c: Reliably Transmitting (NAT) to 172.16.1.210:5060:
REGISTER sip:172.16.1.210 SIP/2.0
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK55b3e9ec;rport
Max-Forwards: 70
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
To: <sip:2468@172.16.1.210>
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 180 REGISTER
User-Agent: FPBX-13.0.188.8(11.21.2)
Expires: 120
Contact: <sip:2468@172.16.1.61:5060>
Content-Length: 0


[2016-10-12 08:52:37] NOTICE[29815] chan_sip.c:    -- Registration for '2468@172.16.1.210' timed out, trying again (Attempt #79)
[2016-10-12 08:52:37] VERBOSE[29815] chan_sip.c: Really destroying SIP dialog '7355b21750348b285094ce4f7e3501d0@127.0.0.1' Method: REGISTER
[2016-10-12 08:52:37] VERBOSE[29815] chan_sip.c:
<--- SIP read from UDP:172.16.1.210:5060 --->
SIP/2.0 501 Not Implemented
To: <sip:2468@172.16.1.210>;tag=d260d6d8ee728a59i0
From: <sip:2468@172.16.1.210>;tag=as3a6031cd
Call-ID: 7355b21750348b285094ce4f7e3501d0@127.0.0.1
CSeq: 180 REGISTER
Via: SIP/2.0/UDP 172.16.1.61:5060;branch=z9hG4bK55b3e9ec
Server: Sipura/SPA3000-3.1.7(GWg)
Content-Length: 0

I see “501 Not Implemented” as the cause but I don’t know what it means. I don’t know whether the problem lies in the linksys settings or the freebox trunk settings.
Here is a screenshot of top half the linksys spa3000 PSTN-Line page using Advanced:
http://198.91.92.112/linksys1.jpg
here;s the bottom half:
http://198.91.92.112/linksys2.jpg

Here’s a screenshot of the freepbx-13 trunk outgoing sip settings:
http://198.91.92.112/outgoing.jpg
and here’s the sip incoming settings:
http://198.91.92.112/incoming.jpg

if anyone can spot where the problem is I’d be grateful, I’ve been on this for hours.


#2

I am not familiar with this setup but i believe there is a misunderstanding. on linksys it seems like you are trying to register to freepbx while on freepbx you are trying to register to linksys. I dont think there is nothing wrong with that but probably this is your problem…

So what i believe is just remove the PSTN line config from linksys and let freepbx be UAC and send the register request. Then take your pcaps and see if it still responds with 501.

Also 501 means that the UAS sending the 501 doesnt understand the request that UAC sent which is register here.


(Rob Thomas) #3

You do not register TO the thing, it registers to you. Set the type to be ‘friend’, and ignore the outgoing page.


#4

rob thanks for your response however it’s confusing. Do you mean freepbx does not register to the linksys? or vice versa? The type in freepbx is already set to ‘friend’ however the trunk will still not come up. Are there errors in the freepbx outgoing settings?


#5

thanks takobaba I can’t remove the pstn line config from linksys becuase I need to connect to it from freepbx, otherwise i’ll never get a working trunk. Also, what’s a UAS?


(Rob Thomas) #6

When I said ignore, I meant dont use. Leave it blank. All of it. Including the registration.


(Mm999) #7

I have several Linksys devices - as noted Linksys register to FPBX, not the other way around. Your Linksys device settings look ok. Here are my FPBX Peer details. Note, my Linksys is at a remote site and NAT is applicable.

username=Shaw547
type=friend
secret=xxxxxx
qualify=yes
port=5060
nat=yes
incominglimit=1
host=dynamic
dtmfmode=rfc2833
disallow=all
context=from-trunk
canreinvite=no
allow=ulaw&g729

My FPBX User Details is blank.


(Dave Burgess) #8

Technically, on the server, the type shouldn’t be “Friend”, it should be “Peer”. Friend establishes the same thing as “Peer” and “User” at the same time.


#9

thanks mm999, I now have the device registered however I can’t get incoming calls on it. I have an inbound route set up for the sip trunk but there’s no action in the console when a call comes in on the pstn lline.


(Mm999) #10

I checked my Inbound Route for thew Linksys and basically all I have set are the route name and the DID as well as where the call destination. Maybe check the logs to see where it’s going wrong.

I’ll check into the Friend setting, thanks!