[App_rpt-users] DNS issues with Dial

Jim Kutsch, KY2D Jim.Kutsch at ky2d.com
Mon Feb 1 11:04:40 EST 2016


I had similar issues during boot when I started using Dial on my RPi. I
found that Asterisk was starting too quickly before other needed processes
had initialized. By putting a "sleep 30" statement in the asterisk start RC
script, all issues were solved, even the failure to register Echolink. It
appeared that the network hadn't fully initialized before Asterisk was
trying to do DNS lookups. In my case, I'm using DHCP on the RPi and the home
router forces the same address to it each time.

73, Jim, KY2D, node 2396


-----Original Message-----
From: app_rpt-users-bounces at ohnosec.org
[mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Mark Johnston
Sent: Sunday, January 31, 2016 2:55 AM
To: app_rpt-users at ohnosec.org
Subject: [App_rpt-users] DNS issues with Dial

/var/log/asterisk/messages:

[Jan 30 23:45:03] NOTICE[675] dnsmgr.c: Managed DNS entries will be
refreshed every 300 seconds.
[Jan 30 23:45:03] NOTICE[675] cdr.c: CDR simple logging enabled.
[Jan 30 23:45:03] NOTICE[675] loader.c: 57 modules will be loaded.
[Jan 30 23:45:03] WARNING[675] acl.c: Unable to lookup 'callcentric.com'
[Jan 30 23:45:04] WARNING[711] chan_sip.c: No such host: callcentric.com
[Jan 30 23:45:04] WARNING[711] chan_sip.c: Probably a DNS error for
registration to 1777......101 at callcentric.com, trying REGISTER again (after
60 seconds) [Jan 30 23:45:04] WARNING[675] pbx.c: Unable to register
extension '_1.', priority 1 in 'allstar-sys', already in use [Jan 30
23:45:04] NOTICE[696] app_rpt.c: Normal Repeater Init  29626 [Jan 30
23:45:04] NOTICE[696] app_rpt.c: Normal Repeater Init  29627 [Jan 30
23:45:04] NOTICE[696] app_rpt.c: Normal Repeater Init  1001 [Jan 30
23:45:05] WARNING[718] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb29627.conf for device usb29627 .
[Jan 30 23:45:05] WARNING[715] chan_usbradio.c: Possibly stuck USB read
channel. [usb29627] [Jan 30 23:45:05] WARNING[715] chan_usbradio.c: Nope,
USB read channel [usb29627] wasn't stuck after all.
[Jan 30 23:45:05] NOTICE[716] chan_simpleusb.c: Assigned USB device
4-2:1.0 to simpleusb channel usb29626
[Jan 30 23:45:05] WARNING[716] chan_simpleusb.c: Loaded parameters from
simpleusb_tune_usb29626.conf for device usb29626 .
[Jan 30 23:45:05] WARNING[719] chan_usbradio.c: Loaded parameters from
usbradio_tune_usb1001.conf for device usb1001 .
[Jan 30 23:45:05] WARNING[717] chan_usbradio.c: Possibly stuck USB read
channel. [usb1001] [Jan 30 23:45:05] WARNING[717] chan_usbradio.c: Nope, USB
read channel [usb1001] wasn't stuck after all.


Using nslookup -
# nslookup callcentric.com
Server: 216.228.160.3
Address: 216.228.160.3#53

Non-authoritative answer:
Name: callcentric.com
Address: 204.11.192.159
Name: callcentric.com
Address: 204.11.192.169
Name: callcentric.com
Address: 204.11.192.163
Name: callcentric.com
Address: 204.11.192.171
Name: callcentric.com
Address: 204.11.192.160
Name: callcentric.com
Address: 204.11.192.170
Name: callcentric.com
Address: 204.11.192.161

If I run
asterisk -rx "sip reload"
everything is fine with the sip connection - now shows the peer is
registered and I can make calls - autopatch

asterisk -rx "sip show peers"

Name/username              Host                   Dyn Nat ACL Port
Status
callcentric/1777......101  204.11.192.170                         5080
   Unmonitored

where as before I did the sip reload, it shows the port as 0


Anyone come across this type of issue?
I tried disabling the dnsmgr, but did not change anything.



73's

Mark KC7DMF
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to
the bottom of the page. Enter your email address and press the "Unsubscribe
or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem. 




More information about the App_rpt-users mailing list