Unable to lookup

FreePBX
1

Hi.
I’m new forum user, and I have a problem with outgoing calls. Firstly, I used a raspbx for my private phone exchange. All perfect, from July 2017 to two weeks ago, aproximately. From this time, the incoming calls are OK, no problem to manage, but to make calls it’s not working. All tries filed. I listen the message “All circuits are busy now, please try your call later” forever…
Desperate, I load the freepbx on a bigger system, in my case a HP Proliant ML110, with same results… I don’t understand. The fail ocurred without human intervention. Before April 2018, all work fine…
I try with softpnones like Phonerlite, and also with Grandstream HT802 pointing directly SIP settings of Movistar (Spain) networks and works fine, both incoming and outgoing… Is only when use the Freepbx when the fails appears…
Please, can anyone help me? Thanks in advance. I include a small portion of Asteris log file:

[2018-04-24 09:34:43] VERBOSE[30149][C-00000019] res_agi.c: <SIP/23-0000001f>AGI Script sangomacrm.agi completed, returning 0
[2018-04-24 09:34:43] VERBOSE[30149][C-00000019] pbx.c: Executing [s@crm-hangup:8] Return("SIP/23-0000001f", "") in new stack
[2018-04-24 09:34:43] VERBOSE[30149][C-00000019] app_stack.c: Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/23-0000001f'
[2018-04-24 09:34:43] VERBOSE[30149][C-00000019] app_stack.c: SIP/23-0000001f Internal Gosub(crm-hangup,s,1) complete GOSUB_RETVAL=
**[2018-04-24 09:36:37] ERROR[2042] netsock2.c: getaddrinfo("telefonica.net", "(null)", ...): Name or service not known**
**[2018-04-24 09:36:37] WARNING[2042] acl.c: Unable to lookup 'telefonica.net'**
[2018-04-24 09:37:27] VERBOSE[2083][C-0000001a] netsock2.c: Using SIP RTP TOS bits 184
[2018-04-24 09:37:27] VERBOSE[2083][C-0000001a] netsock2.c: Using SIP RTP CoS mark 5

The highlighted text shows the (I think) problem…
Best Regards. Miguel

2

You seem to have an issue with DNS lookup. Can you check if DNS lookup works on the FreePBX server? You can use nslookup from commandline.

3

HI. Thanks for your fast answer. Trying to ping with external site, as www.google.com, I can reach with him without problem. I include a screen capture.
This is very strange. I also include the SIP settings outgoing section from trunk. Really, its the first time that I absolutely out to know how is possible that without modify nothing the system ceases the outgoing calls…
Obviously, the labels “outgoing”, “incoming” and “register string”, also the dashed line are added here to clrarify. At machine only text appears…
Thanks a lot!!. Regards. Miguel.

outgoing sip
------------
type=peer
fromuser=95xxxxxxx
secret=95xxxxxxx
fromdomain=telefonica.net
host=telefonica.net
outboundproxy=10.31.255.134:5070
port=5070
nat=yes
insecure=port,invite
dtmfmode=inband
disallow=all
allow=alaw,ulaw


incoming
---------
type=peer
username=95xxxxxxx
secret=95xxxxxxx
fromdomain=telefonica.net
host=10.31.255.134
port=5060
outboundproxy=10.31.255.134
qualify=no
nat=yes
insecure=port,invite
dtmfmode=inband
trustrpid=yes
canreinvite=no
disallow=all
allow=alaw,ulaw
outboundproxyport=5070

Register string

95xxxxxxx#telefonica. net:95xxxxxxx#10.31.255.134:5070

Note: I change the @ with # for permissions problems

MMMMM...! The system cannot permits to me to include images!. No problem. I include text. The ping to google.com working fine.
4

Is this the actual domain you need to connect to? Can you try to ping that? I can’t.

Also, if you can’t upload images, but can post links, use https://imgur.com/ or a similar service

5

SOLVED!! I readed on another forum, “comunidad_movistar_es” with title “Problema Asterisk y host telefonica_net” that the problem origin is the SIP provider, telefonica (Spain). This company, I don’t know why, changed the IP associated with his domain, and not reflects it on DNS servers.
Adding a line as
“213.4.130.95 telefonica_net”
on /etc/hosts file, the problem was solved.
Thanks a lot. Regards, Miguel.

Note: I change “.” by “_” to avoid link problem, because I’m novice on this forum…

6

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.