16 Sep
2009
16 Sep
'09
4:56 p.m.
Hello
Im getting this error in my Kamailio-1.5.2:
Sep 16 15:43:08 sip kamailio[25298]: ERROR:core:sip_resolvehost: NATPR
query timed out, no server could be reached, stop resolving (Connection
timed out)
Sep 16 15:43:08 sip kamailio[25298]: CRITICAL:core:mk_proxy: could not
resolve hostname: "sip.server.pt"
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:uri2proxy: bad host name
in URI <sip:sip.server.pt>
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:t_forward_nonack: failure
to add branches
Why cant Kamailio resolve the name?
Could this be causing my clients SIP registrations to fail?
Thanks
regards
Joao Pereira
16 Sep
16 Sep
5:50 p.m.
Hello,
On 16.09.2009 16:56 Uhr, Joao Gomes Pereira wrote:
Hello
Im getting this error in my Kamailio-1.5.2:
Sep 16 15:43:08 sip kamailio[25298]: ERROR:core:sip_resolvehost: NATPR
query timed out, no server could be reached, stop resolving
(Connection timed out)
Sep 16 15:43:08 sip kamailio[25298]: CRITICAL:core:mk_proxy: could not
resolve hostname: "sip.server.pt"
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:uri2proxy: bad host name
in URI <sip:sip.server.pt>
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:t_forward_nonack:
failure to add branches
Why cant Kamailio resolve the name?
Could this be causing my clients SIP registrations to fail?
dns configuration in
the server is broken. As message says, no DNS
server could be reached while attempting to get the IP address of
destination, therefore forwarding fails.
You can check it using dns tools on the system.
Not sure how is your architecture, but registers should be handled
locally without forwarding -- you can set alias in config file to match
hostnames as local domains.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
8:09 p.m.
Thanks a lot
You were wright, the DNS server that I was using was taking too much to
answer....and that caused Kamailio to produce those errors.
Im now using another DNS server and the problem is solved.
Thanks again
Joao Pereira
Daniel-Constantin Mierla wrote:
Hello,
On 16.09.2009 16:56 Uhr, Joao Gomes Pereira wrote:
--
StarTel - A Rede Livre
Joao Gomes Pereira
www.startel.pt
+351 304500650
sip: gomespereira(a)startel.pt
Hello
Im getting this error in my Kamailio-1.5.2:
Sep 16 15:43:08 sip kamailio[25298]: ERROR:core:sip_resolvehost:
NATPR query timed out, no server could be reached, stop resolving
(Connection timed out)
Sep 16 15:43:08 sip kamailio[25298]: CRITICAL:core:mk_proxy: could
not resolve hostname: "sip.server.pt"
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:uri2proxy: bad host
name in URI <sip:sip.server.pt>
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:t_forward_nonack:
failure to add branches
Why cant Kamailio resolve the name?
Could this be causing my clients SIP registrations to fail?
dns configuration in
the server is broken. As message says, no DNS
server could be reached while attempting to get the IP address of
destination, therefore forwarding fails.
You can check it using dns tools on the system.
Not sure how is your architecture, but registers should be handled
locally without forwarding -- you can set alias in config file to
match hostnames as local domains.
Cheers,
Daniel
8:15 p.m.
On 16.09.2009 20:09 Uhr, Joao Gomes Pereira wrote:
Thanks a lot
You were wright, the DNS server that I was using was taking too much
to answer....and that caused Kamailio to produce those errors.
Im now using another DNS server and the problem is solved.
good! the registrations are ok?
Cheers,
Daniel
Thanks again
Joao Pereira
Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla
* http://www.asipto.com/
Hello,
On 16.09.2009 16:56 Uhr, Joao Gomes Pereira wrote:
Hello
Im getting this error in my Kamailio-1.5.2:
Sep 16 15:43:08 sip kamailio[25298]: ERROR:core:sip_resolvehost:
NATPR query timed out, no server could be reached, stop resolving
(Connection timed out)
Sep 16 15:43:08 sip kamailio[25298]: CRITICAL:core:mk_proxy: could
not resolve hostname: "sip.server.pt"
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:uri2proxy: bad host
name in URI <sip:sip.server.pt>
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:t_forward_nonack:
failure to add branches
Why cant Kamailio resolve the name?
Could this be causing my clients SIP registrations to fail?
dns configuration in
the server is broken. As message says, no DNS
server could be reached while attempting to get the IP address of
destination, therefore forwarding fails.
You can check it using dns tools on the system.
Not sure how is your architecture, but registers should be handled
locally without forwarding -- you can set alias in config file to
match hostnames as local domains.
Cheers,
Daniel
8:28 p.m.
Yes, now Kamailio is again working 100%
Thank you
Joao Pereira
Daniel-Constantin Mierla wrote:
On 16.09.2009 20:09 Uhr, Joao Gomes Pereira wrote:
--
StarTel - A Rede Livre
Joao Gomes Pereira
www.startel.pt
+351 304500650
sip: gomespereira(a)startel.pt
Thanks a lot
You were wright, the DNS server that I was using was taking too much
to answer....and that caused Kamailio to produce those errors.
Im now using another DNS server and the problem is solved.
good! the registrations are ok?
Cheers,
Daniel
Thanks again
Joao Pereira
Daniel-Constantin Mierla wrote:
Hello,
On 16.09.2009 16:56 Uhr, Joao Gomes Pereira wrote:
Hello
Im getting this error in my Kamailio-1.5.2:
Sep 16 15:43:08 sip kamailio[25298]: ERROR:core:sip_resolvehost:
NATPR query timed out, no server could be reached, stop resolving
(Connection timed out)
Sep 16 15:43:08 sip kamailio[25298]: CRITICAL:core:mk_proxy: could
not resolve hostname: "sip.server.pt"
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:uri2proxy: bad host
name in URI <sip:sip.server.pt>
Sep 16 15:43:08 sip kamailio[25298]: ERROR:tm:t_forward_nonack:
failure to add branches
Why cant Kamailio resolve the name?
Could this be causing my clients SIP registrations to fail?
dns configuration in
the server is broken. As message says, no DNS
server could be reached while attempting to get the IP address of
destination, therefore forwarding fails.
You can check it using dns tools on the system.
Not sure how is your architecture, but registers should be handled
locally without forwarding -- you can set alias in config file to
match hostnames as local domains.
Cheers,
Daniel
5557
days inactive
5557
days old
4 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Joao Gomes Pereira