On Thu, 24 Jun 2010 15:33:28 +0200, Benoit Panizzon <[email protected]> said:
> Hi out there > The last few days I noticed quite a large delay when I first dial a number > from my asterisk server. > I found that the problem is that the 1.4.e164.arpa lookup takes enormous time > to return a NXDOMAIN > == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.arpa', > options='', record=1 > == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.arpa, 5148 ms That looks like a timeout of 5 seconds. Maybe your cache is unable to reach some of the e164.arpa servers? > compared to the e164.org or e164.info lookups: > == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.org', > options='', record=1 > == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.org, 141 ms > == ast_get_enum(num='+41618269309', tech='sip', suffix='e164.info', > options='', record=1 > == ast_get_enum() profiling: FAIL, 9.0.3.9.6.2.8.1.6.1.4.e164.info, 167 ms > Of course, as soon as the NXDOMAIN is in the local DNS cache, dialing the > same > number is fast again. > Also the previously working ETHZ e164.arpa test-tone number cannot be > resolved > anymore: > == ast_get_enum(num='+41446580004', tech='sip', suffix='e164.arpa', > options='', record=1 > == ast_get_enum() profiling: FAIL, 4.0.0.0.8.5.6.4.4.1.4.e164.arpa, 5150 ms > Has switch ceased to offer e164.arpa entries? 1.4.e164.arpa does not seem to > be delegated anymore: This "enum pilot" was terminated many, many moons ago. The zone was still delegated to us until November last year, but it has been empty for several years. -- Alex _______________________________________________ swinog mailing list [email protected] http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
