Thanks Scott and Dale
Unless something changed on the inGate everything looks good. Primary public
DNS is providing the right bindings. When attempting to reboot the sipX i
now gives a list of DNS errors as if named on sipx box is failing or failed and
is looking to the primary for bindings. When sipx boots up it should be
looking at the local DNS to resolve SRV, local certs and bindings before is
should attempt to run or does it have to go to primairy DNS to begin it's boot
process to point back to sipX?
Althought sipx/dns has failed i can still bring up sipx admin and login using
the the usually domain running from IE or firefox. i was wondering how is this
possible to run the admin but sipx fails to resolve it's domain name binding?
but when i try to create a server too use in conjunction with sipxbridge it
will not allow me to create the server. error "SIP route to SIP_DOMAIN_NAME
does not match the configured IP address"
I have another sipX running on the public address space i would hate to reboot
it but will if it could help resolve this issue. But then the mail and web
servers should also fail after rebooting but have not.
have you run into this issue before. I'm running 4.1.0 not 4.0.1.
r
On Fri, 2009-07-17 at 12:28 -0500, voice wrote:
> 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 working aok for weeks.
At least at the moment in question, the code couldn't get the right DNS
info for SIP_DOMAIN_NAME, or the box had a different IP address than the
DNS records pointed to. Check by hand that the DNS records all say the
right thing. (And do the DNS lookups on the sipXecs box -- it might be
seeing the wrong DNS records.)
Dale
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
