New Installation-Cannot Make Outbound Calls

[escondido]

After a bit of grief I was able to install Vicibox 8.1 ISO on a remote server. I'm really impressed with the amount of features, and I can clearly see how much is missing from GoAutoDial. I should have switched over a while ago, but live and learn. Anyways, my test server is as follows and I'm 100% focused on outbound calling in the USA. My PBX's handle inbound calls.

ViciBox 8.1.2
VERSION: 2.14-694a
BUILD: 181005-1738
SVN 3053
Asterisk 13.21.1-vici
No extra software
Cloud based

I copied over my old Carrier settings from the GAD signature listed in my signature to the new ViciBox server. Unfortunately, those settings do not work with the latest ViciBox installation.

Code: Select all

***GAD v3.3*** (working)
Carrier ID: justgovoip 
Carrier Name: justgovoip
Carrier Description: justgovoip
Admin User Group: ALL
Registration String: BLANK
Template ID: none selected

Account Entry:
[justgovoip]
disallow=all
allow=gsm
allow=ulaw
type=friend
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=invite,port
nat=yes
host=dal.justgovoip.com

Dialplan Entry:
exten => _XXXXXXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _XXXXXXXXXX.,2,Dial(SIP/${EXTEN:1}@justgovoip,,tTo)
exten => _XXXXXXXXXX.,3,Hangup

Campaign>XXXX>
Dial Prefix Prefix: BLANK (NOT USING X)
Manual Dial Prefix: BLANK
Dial Method: RATIO
Auto Dial Level: 1

Manual Dialing = Works great.
AutoDial = Also Works great.


This is the error message I've pretty much memorized at this point trying to figure out a solution for the past few hours.

Code: Select all

[Nov 17 19:35:08]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known
[Nov 17 19:35:08] WARNING[2063]: acl.c:835 resolve_first: Unable to lookup 'vicibox81'
[Nov 17 19:35:08]   == Using SIP RTP CoS mark 5
[Nov 17 19:35:08]     -- Called 8675309
[Nov 17 19:35:09]     -- SIP/8675309-00000018 is ringing
[Nov 17 19:35:13]        > 0x1721e80 -- Strict RTP learning after remote address set to: OFFICEIPADDRESS:8000
[Nov 17 19:35:13]     -- SIP/8675309-00000018 answered
[Nov 17 19:35:13]     -- Executing [8600051@default:1] MeetMe("SIP/8675309-00000018", "8600051,F") in new stack
[Nov 17 19:35:13]     -- Created MeetMe conference 1023 for conference '8600051'
[Nov 17 19:35:13]     -- <SIP/8675309-00000018> Playing 'conf-onlyperson.gsm' (language 'en')
[Nov 17 19:35:13]        > 0x1721e80 -- Strict RTP switching to RTP target address OFFICEIPADDRESS:8000 as source
[Nov 17 19:35:14]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 17 19:35:18]        > 0x1721e80 -- Strict RTP learning complete - Locking on source address OFFICEIPADDRESS:8000
[Nov 17 19:35:18]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:35:18] NOTICE[2083]: core_local.c:756 local_call: No such extension/context 913124661212@default while calling Local channel
[Nov 17 19:35:19]   == Manager 'sendcron' logged off from 127.0.0.1
vicibox81*CLI> that was an autodial number
No such command 'that was an autodial number' (type 'core show help that was' for other possible commands)
[Nov 17 19:35:40]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:35:41]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:35:41]     -- Called 58600051@default
[Nov 17 19:35:41]     -- Executing [58600051@default:1] MeetMe("Local/58600051@default-00000032;2", "8600051,Fmq") in new stack
[Nov 17 19:35:41]     -- Local/58600051@default-00000032;1 answered
[Nov 17 19:35:41]     -- Executing [8309@default:1] Answer("Local/58600051@default-00000032;1", "") in new stack
[Nov 17 19:35:41]     -- Executing [8309@default:2] Monitor("Local/58600051@default-00000032;1", "wav,20181117-193539_2816789876_1000_8675309") in new stack
[Nov 17 19:35:41]     -- Executing [8309@default:3] Wait("Local/58600051@default-00000032;1", "3600") in new stack
[Nov 17 19:35:41]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 17 19:35:42]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 17 19:35:58]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:35:58]     -- Manager 'sendcron' from 127.0.0.1, hanging up channel: Local/58600051@default-00000032;2
[Nov 17 19:35:58]   == Spawn extension (default, 58600051, 1) exited non-zero on 'Local/58600051@default-00000032;2'
[Nov 17 19:35:58] WARNING[2120][C-0000004e]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Nov 17 19:35:58]     -- Executing [h@default:1] AGI("Local/58600051@default-00000032;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------)") in new stack
[Nov 17 19:35:58]     -- <Local/58600051@default-00000032;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------) completed, returning 0
[Nov 17 19:35:58]   == Spawn extension (default, 8309, 3) exited non-zero on 'Local/58600051@default-00000032;1'
[Nov 17 19:35:58] WARNING[2119][C-0000004f]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Nov 17 19:35:58]     -- Executing [h@default:1] AGI("Local/58600051@default-00000032;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------)") in new stack
[Nov 17 19:35:58]     -- <Local/58600051@default-00000032;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------) completed, returning 0
[Nov 17 19:35:59]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 17 19:36:02]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 17 19:36:02]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 17 19:36:02]   == Manager 'sendcron' logged on from 127.0.0.1


As you can clearly see a 9 is being added to the dial string for some odd reason. I have no idea what the other error/warnings are for, and figure I'll get to that later unless it's important. Hopefully somebody would be kind enough to shed some light on those parts.

The managers manual does a great job about explaining username:password authorization, but truth be told, I've never been able to get that to work with JustgoVoip, so I opted for IP authorization instead. Their customer service is VERY lacking!

This is what I changed to see if I could get auto/manual dialing working for a test campaign.

Code: Select all

***Vicibox Setup*** (# 2)
Carrier ID: justgovoip 
Carrier Name: justgovoip
Carrier Description: justgovoip
Admin User Group: ALL
Registration String: BLANK
Template ID: none selected

Account Entry:
[justgovoip]
disallow=all
allow=gsm
allow=ulaw
type=friend
dtmfmode=rfc2833
context=trunkinbound (not sure if it's needed, but doesn't hurt)
qualify=yes
insecure=invite,port
nat=force_rport,comedia
host=dal.justgovoip.com

Dialplan Entry:
exten => _91XXXXXXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX.,2,Dial(SIP/${EXTEN:1}@justgovoip3,,tTo)
exten => _91XXXXXXXXXX.,3,Hangup

Campaign>XXXX>
Dial Prefix Prefix: 9
Manual Dial Prefix: 9
Dial Method: RATIO
Auto Dial Level: 1


Error message below

Code: Select all

[Nov 18 01:56:56]     -- Executing [8600051@default:1] MeetMe("SIP/8675309-00000007", "8600051,F") in new stack
[Nov 18 01:56:56]     -- Created MeetMe conference 1023 for conference '8600051'
[Nov 18 01:56:56]     -- <SIP/8675309-00000007> Playing 'conf-onlyperson.gsm' (language 'en')
[Nov 18 01:56:56]        > 0x7f9bf003ef60 -- Strict RTP switching to RTP target address OFFICEIPADDRESS:8000 as source
[Nov 18 01:56:57]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 18 01:57:01]        > 0x7f9bf003ef60 -- Strict RTP learning complete - Locking on source address OFFICEIPADDRESS:8000
[Nov 18 01:57:02]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 18 01:57:02]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 18 01:57:02]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 18 01:57:02]   == Manager 'sendcron' logged off from 127.0.0.1
[Nov 18 01:57:04]   == Manager 'sendcron' logged on from 127.0.0.1
[Nov 18 01:57:04] NOTICE[19197]: core_local.c:756 local_call: No such extension/context 918162381212@default while calling Local channel


That last line has been driving me nuts for hours. It doesn't make sense to me why the 9 is added. I've tested a few variations of EXTEN (no number or 2), and tried different variations of _91XXXXXXXXXX (NXXNXXXXXX, XXXXXXXXXX, for example), as well as played around with the Dial Prefix section listed in the campaign menu (BLANK, X 9 or 1). The one time the outbound number showed up perfectly (12223334444) in the CLI I got that annoying local channel error message listed below.

Sip Show Registry shows active for the User/Phone, as well as JustGoVoip. I've also been pretty relentless about using Sip Reload and Dialplan Reload just to be on the safe after updating CARRIER and CAMPAIGN settings.

I really want to get away from using GAD. More than likely I'll be going with a different voip provider very soon, but before I do that, I'd love to know what I'm doing wrong because I cannot figure what is causing the issue with making outbound calls.

Thanks.

[thephaseusa]

You have [justgovoip] in account entry then in dialplan justgovoip3


In campaign settings Dial Prefix is set to 9 by default.

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(SIP/${EXTEN:1}@enterprise,,tTo)
exten => _91XXXXXXXXXX,3,Hangup

That’s what my carrier dial plan entry looks like.

And on making the switch over to Vicibox “welcome to the desert of the real”)))

Congrats! Now you can do everything vicidial was meant to do!

[williamconley]

Code: Select all

Cloud based

This has no meaning. There is no cloud. Is this on a Amazon EC2 server? Or at a colo? Best to name the colo and server type.

Code: Select all

[Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known

Where do you have "vicibox81" in your system? Wherever it is, the system can't resolve that name to an IP. Since this also appears to be the host name of your server, you may need to verify that this entry is in /etc/hosts or change the entry (wherever it is) to an IP or other valid domain or even localhost.

Code: Select all

[Nov 17 19:35:18] NOTICE[2083]: core_local.c:756 local_call: No such extension/context 913124661212@default while calling Local channel

And there is your final "can't dial out" problem.

Code: Select all

913124661212
exten => _XXXXXXXXXX.,

While it appears as though it *should* match, it's not for some reason. So:
* Verify that the extensions-vicidial.conf actually reloads the new values when you make a change in a dialplan extension.
* Make sure NONE of your dialplan extensions have a context in them (nothing with brackets [ ]) which would remove everything after that entry from the [default] context where they all must reside to work properly.
* Do NOT leave the dial prefix blank. Use 9 or another single digit number until you have more than 10 carriers OR use X. But don't leave it blank. I strongly suggest you fall in line and use 9.
* Use a matching 10 digit US NANPA dial pattern such as the one suggested by thephaseusa (_91NXXNXXXXXX is *the* standard for north america with dial prefix 9). This allows multiple simultaneous live carriers without interruption or interference with each other.

[escondido]

Code: Select all

Cloud based

This has no meaning. There is no cloud. Is this on a Amazon EC2 server? Or at a colo? Best to name the colo and server type.

Code: Select all

[Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known

Where do you have "vicibox81" in your system? Wherever it is, the system can't resolve that name to an IP. Since this also appears to be the host name of your server, you may need to verify that this entry is in /etc/hosts or change the entry (wherever it is) to an IP or other valid domain or even localhost.

Code: Select all

[Nov 17 19:35:18] NOTICE[2083]: core_local.c:756 local_call: No such extension/context 913124661212@default while calling Local channel

And there is your final "can't dial out" problem.

Code: Select all

913124661212
exten => _XXXXXXXXXX.,

While it appears as though it *should* match, it's not for some reason. So:
* Verify that the extensions-vicidial.conf actually reloads the new values when you make a change in a dialplan extension.
* Make sure NONE of your dialplan extensions have a context in them (nothing with brackets [ ]) which would remove everything after that entry from the [default] context where they all must reside to work properly.
* Do NOT leave the dial prefix blank. Use 9 or another single digit number until you have more than 10 carriers OR use X. But don't leave it blank. I strongly suggest you fall in line and use 9.
* Use a matching 10 digit US NANPA dial pattern such as the one suggested by thephaseusa (_91NXXNXXXXXX is *the* standard for north america with dial prefix 9). This allows multiple simultaneous live carriers without interruption or interference with each other.

Sorry for the late reply, it's been a busy week. JustGoVoip hasn't replied to me in about 1.5 weeks, so forget them. I was to able to get it working for some testing with Didlogic. My only issue with them is allowing CLI passthrough. They seem to be quite picky about that process. Caller ID always showed up for the DID regardless of changing it in the campaign settings. I've reached out them for feedback since I have a lot of numbers with a different provider and I'm eager to test out the geo-targeting feature of ViciDial.

For anybody else looking at this post going forward the following settings works great.

register => user:password@sip.nyc.didlogic.net:5060

[didlogic]
disallow=all
allow=ulaw
type=friend
username=user
secret=password
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=port,invite
nat=force_rport,comedia
host=sip.nyc.didlogic.net

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(SIP/${EXTEN:2}@didlogic,,tTo)
exten => _91XXXXXXXXXX,3,Hangup

Make sure the 9 is there in campaign settings and you'll be good to go.

vicibox81 is what my hostname was changed to after I installed the iso. It's a remote VPS with vultr. My bad.

I did look at the file you recommended and it appears the iso installation doesn't modify the current hostname after installing or I screwed up somewhere.

Current host file dated 5-9-2017 shows the following

Code: Select all

#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#   
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1   localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts

I'm not exactly sure how to fix that part since I've been trying to figure out how to add another 3-4 providers to see how ViciDial works.

I appreciate you guys taking the time to help me out.

[williamconley]

I'm not exactly sure how to fix that part since I've been trying to figure out how to add another 3-4 providers to see how ViciDial works.

Should not be related to individual providers. Try adding one. The only configuration option specific to a provider related to dns is the "host=" entry in the sip configuration/context. As long as your DNSresolver can convert that to an ip (or you just provide an IP so no resolution is needed), then DNS should not fail for an individual provider.

[carpenox]

stupid question, but do you have any channels available on your carrier? a SIP Trunk and a SIP Trunk WITH channels paid for and running are two different things....

[mbaret]

Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known


in relation to this problem, which I only noticed in asterisk

And I did not want to see that warning, I wanted to solve it, so I came to this post.

I solved it by putting in the / etc / hosts file
I added a line
127.0.0.1 vicibox81
This indicates that when that dns is called it will reach the local host, I see that the warning is gone.

Actually I don't know what is trying to do asterisk calling vicibox81, but the warning is not there, if anyone has knowledge about this, could you tell me.

note: I have no inbound, nothing !!, I say this because I saw many posts about inbound and this case


VERSION: 2.14-752a
BUILD: 200508-1024
© 2020 ViciDial Group

VPCS vultr.... 2 core y funciona good 8 agents FYI

[carpenox]

Correct you have to do that with your FQDN too

point your public IP to your FQDN

-Nox

[virtualsky]

Can we configure webphone in Vicidial instead of Vicibox...is it right?

[carpenox]

vicibox is just vicidial, asterisk, apache and mysql all in one which you did via scratch install so YES

[williamconley]

vicibox is just vicidial, asterisk, apache and mysql all in one which you did via scratch install so YES

ViciBOX is the installation disk for ViciDIAL. Vicibox provides the linux environment in which Vicidial can run. This could be done other ways, but Vicibox makes installation much simpler than trying to provide and configure an OS and all necessary packages for Vicidial to run.