Old NAT info shows in sip debug - can't answer inbound calls

General Help
1

I had some problems with the machine and had to restore a backup from a time when the machine had a different IP address. It was 192.168.2.5 and now it’s 192.168.1.5.

The fact that I couldn’t answer incoming calls made me think I had a NAT problem so I turned on sip debug. Sure enough, even though none of my conf files show any reference to the old address at 2.5 it shows up in the debug.

I removed all my trunks, extensions and rebuilt them but it won’t go away.

Asterisk 1.6.2.6
Ubuntu 9.10
FreePBX 2.7.0

Does anyone know where the reference to 192.168.2.5 in my config??

<------------->
— (11 headers 0 lines) —
Really destroying SIP dialog ‘[email protected]’ Method: OPTIONS
REGISTER 12 headers, 0 lines
Reliably Transmitting (NAT) to 204.11.192.37:5060:
REGISTER sip:callcentric.com SIP/2.0
Via: SIP/2.0/UDP 74.140.120.205:5060;branch=z9hG4bK5a1495cc;rport
Max-Forwards: 70
From: sip:[email protected];tag=as27570767
To: sip:[email protected]
Call-ID: [email protected]
CSeq: 145 REGISTER
User-Agent: Asterisk PBX 1.6.2.6
Authorization: Digest username=“17772789640”, realm=“callcentric.com”, algorithm=MD5, uri=“sip:callcentric.com”, nonce=“ba10f5fb500fa302479f69646eba83e3”, response="a343f7f36f0a6cd05a55bc42e45a4eee"
Expires: 120
Contact: sip:[email protected]
Content-Length: 0

eco-router*CLI>
<— SIP read from UDP:204.11.192.37:5060 —>
SIP/2.0 200 Ok
v: SIP/2.0/UDP 74.140.120.205:5060;branch=z9hG4bK5a1495cc;rport=5060
f: sip:[email protected];tag=as27570767
t: sip:[email protected]
i: [email protected]
CSeq: 145 REGISTER
m: sip:[email protected];expires=61
l: 0

2

The easiest way to find out where address is coming from is to do this in a shell:

cd /etc/asterisk
grep -H '192.168.2.5' *

The -H will tell you in which file the address is defined.

3

I found a reference to the old 192.168.2.5 outside of Asterisk and changed it. Now I see the right address in SIP debug but I still can’t pickup an inbound call. I see a message in CLI that it was answered but it keeps right on ringing and I can’t talk to the caller.

I’ve got 5060-5065 and 10000-20000 open on IPtables. Also 5038 and 5080.

Outbound calls are fine.

4

What is the contents of your sip_nat.conf or sip_general_custom.conf?

5

Thanks for your input guys,

sip_nat.conf is empty
sip_general_custom.conf is empty

I found the problem with the address and fixed it.

But, I still can’t answer an inbound call.

6

The original build was Asterisk 1.4.2x.

The rebuild after the crash was 1.6.26. I fought with it for 5 days.

I scuddled the whole thing, dropped the firewall and rebuilt a whole new box with Asterisk 1.6.2.6 and have the exact, same problem.

Outbound and internal calling is perfect. Inbound calls STILL, CAN NOT, be answered.

I am putting one in the chamber.

Any advice or thoughts would be greatly appreciated.