problem in getting calls in Inbound campaign

[joviton]

Added by joviton dcosta 4 minutes ago

Hi i have goautodial 2.1 setup ,

i have created inbound campaign , in-group , Added DID, and DID setting in carrier .

when i do test call from my phone to the inbound DID , it just plays the IVR message and gets hunup

i can see the Asterisk log when the incoming calls come in . Please help

Tried diverting the call to Local phone ,etc but no luck

Carrier config.

Code: Select all

register string .=> XXXXXX xxxxxxxxx xxxxxxxxxxxxxxxx

Code: Select all

[xxxxxxxxx]
disallow=all
allow=ulaw,alaw
type=friend
username=
secret=
host=
fromdomain=
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=port,invite
nat=yes

Below is the Asterisk log

Code: Select all

[[Apr 19 00:55:17] -- Executing [0207872005@trunkinbound:1] AGI in new stack
[Apr 19 00:55:17] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Apr 19 00:55:17] ERROR14073: utils.c:967 ast_carefulwrite: write() returned error: Broken pipe
[Apr 19 00:55:17] -- AGI Script agi-DID_route.agi completed, returning 0
[Apr 19 00:55:17] -- Executing [9998811112@default:1] Wait("SIP/XXXXXXXXXX-00000004", "2") in new stack
[Apr 19 00:55:19] -- Executing [9998811112@default:2] Answer("SIP/XXXXXXXXXX-00000004", "") in new stack
[Apr 19 00:55:19] -- Executing [9998811112@default:3] Playback("SIP/XXXXXXXXXX-00000004", "ss-noservice") in new stack
[Apr 19 00:55:19] -- <SIP/XXXXXXXXXX-00000004> Playing 'ss-noservice' (language 'en')
[Apr 19 00:55:24] -- Executing [9998811112@default:4] Playback("SIP/XXXXXXXXXX-00000004", "vm-goodbye") in new stack
[Apr 19 00:55:24] -- <SIP/XXXXXXXXXX-00000004> Playing 'vm-goodbye' (language 'en')
[Apr 19 00:55:25] -- Executing [9998811112@default:5] Hangup("SIP/XXXXXXXXXX-00000004", "") in new stack
[Apr 19 00:55:25] == Spawn extension (default, 9998811112, 5) exited non-zero on 'SIP/XXXXXXXXXX-00000004'
[Apr 19 00:55:25] -- Executing [h@default:1] DeadAGI("SIP/XXXXXXXXXX-00000004", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Apr 19 00:55:25] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0

Even edited the extension.confg

Code: Select all

exten => 8002277655,1,Ringing ; call ringing
exten => 8002277655,2,Wait(1) ; Wait 1 second for CID delivery from PRI
exten => 8002277655,3,Answer ; Answer the line
exten => 8002277655,4,AGI
exten => 8002277655,5,Hangup

[edited for legibility: williamconley]

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) You should be using the Vicidial Manager's Manual to configure inbound, not just guessing. Do not edit the extensions.conf file.

4) Create a DID for "0207872005" and point it to an Ingroup or phone from Admin->Phones for testing. To point to an Ingroup, you must choose both the route type (Ingroup) and the actual Ingroup from the dropdown of available ingroups. But mostly: Use the Manual!