[asterisk-users] SPA3102 registration problem

[Tim Johnson]

Quoting Jaap Winius <jwinius at umrk.to>:

> Hi list,
>
> After failing to get a Sipura/Linksys SPA3000, which I've configured
> as a PSTN gateway, to pass on the Caller ID, I decided to try my luck
> with a Linksys SPA3102 after hearing some promising stories.
> Unfortunately, I've run into a completely new problem: it seems
> Asterisk won't let this device register.
>
> I went about configuring the SPA3102 in much the same way as I did the
> SPA3000 and the Linksys PAP2T. For example, in all three cases this is
> the way I configured /etc/asterisk/sip.conf for Line 1:
>
>     [4000]
>     type=friend
>     host=dynamic
>     context=phones-m
>     secret=1234
>     dtmfmode=rfc2833
>     disallow=all
>     allow=ulaw
>     qualify=yes
>
> The device is configured to register Line 1 with the SIP proxy and as
> a result the command "sip show peers" would eventually say the
> following:
>
>     Name/username  Host           Dyn  Nat  ACL  Port    Status
>     4000/4000      192.168.1.3     D             5060    OK   (13 ms)
>
> Not so with the SPA3102, in which case I always get:
>
>     Name/username  Host           Dyn  Nat  ACL  Port    Status
>     4000           (Unspecified)   D             0       UNKNOWN
>
> After some tests, I found out that the SPA3102 is indeed trying to
> register, but that Asterisk seems to be ignoring it. Using tcpdump, I
> can see that registration packets are regularly being sent to the
> Asterisk server (bitis):
>
> 15:30:49.567288 IP spa3102.umrk.to.sip > bitis.umrk.to.sip: SIP, length: 482
> Eh........%........
> .......xREGISTER sip:192.168.1.10 SIP/2.0
> Via: SIP/2.0/UDP 12
> 15:30:49.568390 IP spa3102.umrk.to.sip-tls > bitis.umrk.to.sip: SIP,
> length: 492
> Eh........%x.......
> .......%REGISTER sip:192.168.1.10 SIP/2.0
> Via: SIP/2.0/UDP 12
>
> This sequence keeps on repeating. Also, if I change the sip.conf
> settings above to "type=peer" and "host=192.168.1.3", I'll see these
> messages appear on the Asterisk console:
>
> [Feb 27 15:17:34] NOTICE[10893]: chan_sip.c:12414
> handle_response_peerpoke: Peer '4000' is now Reachable. (7ms / 2000ms)
> [Feb 27 15:17:35] ERROR[10893]: chan_sip.c:8513 register_verify: Peer
> '4000' is trying to register, but not configured as host=dynamic
> [Feb 27 15:17:35] NOTICE[10893]: chan_sip.c:14943
> handle_request_register: Registration from 'Margriet
> <sip:8000 at 192.168.1.10>' failed for '192.168.1.3' - Peer is not
> supposed to register
>
> If, in this case, I configure the SPA3102 not to register any of its
> extensions, Asterisk will report them to be reachable and there won't
> be any more errors on the console, but in actual fact the extensions
> won't be available: I won't be able to call the phone attached to it
> due to congestion, and if I pick up that phone to make a call, I'll
> immediately hear a busy signal.
>
> What could be causing this situation? I'm using Asterisk 1.4.14 and
> the SPA3102 has the latest firmware version: 5.1.7(GW). I should also
> mention that I'm not interested in using this device's broadband
> router functionality.
>
> Any help would be much appreciated!
>
> Thanks,
>
> Jaap

I see you put a password line in your sip.conf, but I do not see a  
username line. Also, you might want to check the port #'s for both the  
Line 1 and PSTN line. I use 5060 and 5061, respectively.  Hopefully  
this either helps, or puts you on the right track.

Tim