how to troubleshoot remote extension not working

[MillsapsPE]

First, this particular remote extension 500 (SPA841) was working fine for several days. Now, it will not connect at all. It may coincide with a DSL modem and Dlink router reboot that occured about the same time at the remote location (SBC was doing work on phone lines). I have a second extension (another SPA841) at another remote location that still connects fine.

I also tried moving the * box to DMZ.
Since the extension won't connect at all, I can't run sip debug 500.
I'm running AAH v.2.4, upgraded * to 1.2.4.

[500]
username=500
type=friend
secret=<secret>
record_out=Adhoc
record_in=Adhoc
qualify=yes
port=5060
nat=yes ;I have also tried a 1 here
mailbox=500@device
host=dynamic
dtmfmode=rfc2833
context=from-internal
canreinvite=no
callerid=device <500>

sip_nat.conf:
externip=24.1.1.1
localnet=192.168.1.0/255.255.255.0 ;actual IP address of * box is 192.168.1.24
nat=yes

partial debug log: (70.1.1.1 is IP address of remote office)
Feb 14 10:09:50 DEBUG[5749] chan_sip.c: Auto destroying call 'e6438bad-5094d7d2@192.168.1.5'
Feb 14 10:09:50 DEBUG[5749] chan_sip.c: Auto destroying call 'fb60f1f1-ce3b065e@192.168.1.5'
Feb 14 10:10:05 DEBUG[5749] acl.c: ##### Testing 70.1.1.1 with 192.168.1.0
Feb 14 10:10:05 DEBUG[5749] chan_sip.c: Target address 70.1.1.1 is not local, substituting externip
Feb 14 10:10:05 DEBUG[5749] acl.c: ##### Testing 70.1.1.1 with 192.168.1.0
Feb 14 10:10:05 DEBUG[5749] chan_sip.c: Target address 70.1.1.1 is not local, substituting externip
Feb 14 10:10:05 DEBUG[5749] chan_sip.c: Target address 70.1.1.1 is not local, substituting externip

sip show peers:
Name/username Host Dyn Nat ACL Port Status
500/500 (Unspecified) D N 0 UNKNOWN
3210/3210 67.1.1.1 D N 15060 OK (34 ms)
204/204 192.168.1.32 D 5060 Unmonitored
202/202 192.168.1.36 D 5060 Unmonitored
201/201 192.168.1.33 D 5060 Unmonitored
200/200 192.168.1.106 D 5060 Unmonitored
6 sip peers [5 online , 1 offline]

I finally got a little smarter and did a sip debug ip 70.1.1.1. I didn't want to post everything here, but I think this is an important line:
SIP/2.0 401 Unauthorized

Should I post more of the output?
I did a search for 401 unauthorized and didn't find anything that would help other than the fact it appears to be (obviously) a registration problem.

[mberlant]

First of all, if you have another SPA-841 working fine from another remote location and the sip.conf is the same for both SPAs, your problem is not at all likely to be in your Asterisk or its router.

Now, you mention that this remote location has a D-Link router. It could be that this D-Link router is one of their models that employs Symmetric NAT (incompatible with SIP) and that this router has lost the manual routing information necessary to allow the SPA-841 to connect to the outside world.

Since it is an SPA-841, I have a 50/50 chance in assuming that you have both the L1 and L2 buttons programmed for the same Asterisk extension (as the same "Line" number in the SPA). If this is the case (and, even if it isn't), you might want to run an experiment trying to program Line 2 to FWD to further isolate the trouble. I would expect that you will similarly fail to Register with FWD, as my logic here would start to have trouble if you succeed.

Let us know what you find.

[MillsapsPE]

Originally Posted by mberlant

First of all, if you have another SPA-841 working fine from another remote location and the sip.conf is the same for both SPAs, your problem is not at all likely to be in your Asterisk or its router.

I agree.

Originally Posted by mberlant

Now, you mention that this remote location has a D-Link router. It could be that this D-Link router is one of their models that employs Symmetric NAT (incompatible with SIP) and that this router has lost the manual routing information necessary to allow the SPA-841 to connect to the outside world.

Since this is the only SIP device in this office, would port forwarding the SIP ports directly to that phone solve this? (Normally, I would just try it to see what happens, but I'm not there and there are no tech people in that office.) I'm curious, why did the phone work initially if the router has an incompatibility issue?

Originally Posted by mberlant

Since it is an SPA-841, I have a 50/50 chance in assuming that you have both the L1 and L2 buttons programmed for the same Asterisk extension (as the same "Line" number in the SPA). If this is the case (and, even if it isn't), you might want to run an experiment trying to program Line 2 to FWD to further isolate the trouble. I would expect that you will similarly fail to Register with FWD, as my logic here would start to have trouble if you succeed.

You are correct, both line appearances are set up for the same extension, though I don't remember is I set up L2 to look at EXT1 settings or if I actually put the same settings in EXT2.

I'll see what I can do with the person in that office. If it is the router, I guess I'll replace with a Linksys WRT54GS (which is what I have here running SVEASOFT firmware).

[MillsapsPE]

The other thing I don't get is where does the 192.168.1.5 come from. I don't have anything in my local network with that address (including DHCP). Is this an IP address assigned to "match" a remote extension???

asterisk1*CLI> sip show channels
Peer User/ANR Call ID Seq (Tx/Rx) Form Hold Last Message
208.1.1.1 <name> 34f47a5518a 01217/00000 unkn No
192.168.1.5 (None) 4a2ade20-82 00101/05680 unkn No Rx: REGISTER
192.168.1.5 (None) 4a543f0-28c 00101/05680 unkn No Rx: REGISTER
192.168.1.103 206 cc047a4e-67 00101/00002 ulaw No Rx: ACK
4 active SIP channels

At this time, there was one current call from ext. 206 (SIP) through an IAX2 provider.