Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPO 500 10.0 SSA Resolved Address: 0.0.0.0 2

Status
Not open for further replies.

Wallysworld

Technical User
Feb 20, 2007
255
CA
Hi All;

I haven't seen this before.
The ipo was functioning with it's sip trunk fine, until we lost the internet just recently.

I'm able to ping to the router but not to their public ip address. However, from a computer plugged into the same router, I can ping to the public ip & the sip provider.

The SIP trunk summary keeps telling me the Resolved Address: is 0.0.0.0 and it doesn't matter if I change "Use Network Topology Info" field or not.

Has anyone had this happen before? What am I missing other than not a good explanation...
 
Sounds like you need to change the IP route, soinds like they changed the IP of the gateway/router, also make sure DNS has an entry :)

nte-transmall.gif
 
Or maybe it can't get to the DNS server

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Yes Wallysworld, I too have the problem on my office IPO. My DNS resolution breaks in the IPO as indicated in Monitor with the DNS filter on. If internet is lost while DNS is broken, I get the 0.0.0.0 for resolved address on the SIP trunk. My first "make it work" because it is our production phone system was change the DNS to a 3rd party external DNS server on the IPO and reboot. It broke again after a couple of days. Not having time to isolate further at this time, I ended up getting a static address from the SIP provider for my ITSP Domain and ITSP SIP Proxy address settings in the IPO.
I am suspecting either my IPO with a possible firmware bug, or setup in my production firewall. I hope soon I will find the time to isolate the issue instead of my current work around.
Please share your IPO release, mine is 9.1.1.0. Have not had a reason to update until now, lol!
 
This one is at 10.0.0.2.

I'm going to try the static ip route.

 
I changed the ITSP Proxy Address, to the static ip address, that made the line go out of service. The "Resolved Address" in SSA changed to the static ip but the line went oos.

Until that time the lines were showing idle, but not registering.

From another computer onsite I can ping the dns addresses (ip and named).

Why is the system not able to talk to the dns server?

 
Not sure why your IPO cannot talk to the DNS.

My SIP provider had to provide me with a static address. When I used the one that my IPO had previously resolved to, my trunks would be out of service. They provided me with a completely different static address.

Did you try a new DNS server in the IPO? Level3 DNS is 209.244.0.3 if interested.
 
Where do you have the DNS server specified system>DNS or Lines>SIP Line>Transport>Explicit DNS? If you have the ITSP proxy address set generally I set the explicit DNS as well.

The truth is just an excuse for lack of imagination.
 
Weird.

I don't know if this is going to be helpful to anyone else but this is what happened.

I was getting the "Resolved address" is 0.0.0.0.
Screwed with almost every other setting and the only one that changed it was Under Transport>ITSP Proxy Address I changed that from the dns name to the static ip of the provider. That did not fix the problem but in "Resolved Address" the static ip showed up. My lines were then OOS.
Changed ITSP back to the DNS Name.

Following critchey's suggestion I changed the Transport>Explicit DNS Server(s)address to the static ip of the provider. Did not fix the issue.
I put the Explicit DNS Server(s) back to 0.0.0.0 and unchecked "Calls Route via Registrar".
The system immediately came back online.

I have never previously had to uncheck the Calls Route via Registrar. In fact this system was working with it checked. Maybe a bug, maybe a ghost. If this makes any sense to anyone that can shed some more light, that would be great. I'm not holding my breath, but it's always good to understand the solution instead of just forgetting about it!.

Thanks to everyone for your input!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top