Hi Dale
sipx1 box has been running for 5 weeks with no changes from network point of
view. This problem just happened after a reboot. last reboot was 2 weeks ago.
What would cause this problem, which must only exist from the sipx1 box. More
important how to fix it?
a.. From: "Dale Worley"
On Fri, 2009-07-17 at 14:09 -0500, voice wrote:
> i rand dig from the sipx box. I'm using sipx1.xxx.org, which is the
> domain of sipx1 but it resovles to the public sipx1.xxx.org which is
> the public ip of eth1 on the inGate which is its public ipaddr. i was
> thinking that dig from the sipx sh
I don't want to just reinstalled and side step this problem but may have too.
Primary DNS does not seem to be the problem for if it was i would not be able
to access the admin runing FQDM of sipX1 box from another networked box,
right? is it possible to reinstall bind running on the sipx1 box
Hi Kevin
I ran the DNS advisor from a MS server box and this is what was said. What is
my callserver-name? It looks like i should be running the sipx-dns on the
sipx1 box. The dns-advisor statement is under-stated. Please advise.
i guess it should look like this from the linux command line:
Hi Robert
i rand dig from the sipx box. I'm using sipx1.xxx.org, which is the domain of
sipx1 but it resovles to the public sipx1.xxx.org which is the public ip of
eth1 on the inGate which is its public ipaddr. i was thinking that dig from
the sipx should have given the priivate ipadd not the
users] SIP route to SIP_DOMAIN_NAME does not
match theconfigured IP address
Hi
Just got this Error after a reboot of 4.1.0 just now.
SIP route to SIP_DOMAIN_NAME does not match the configured IP
address
Server has been w
