vicidial.org

Hi ,
Our configuration is GoAutodial 3.3 from iso. , Single Server | Sangoma PRI Card A101e (Single Port) | No Extra Software After Installation | Core i3 Processor | 4GiB RAM

We are successfully using GoAutodial / vicidial for incoming calls. We use a PRI line from Airtel in India. On our outbound campaigns, our server is successfully dialing out, the call is also ringing, however when the lead picks up the phone, he hears silence for 10 seconds and the call disconnects. Meanwhile on the agent end, even after pickup the call is not transferred to the agent screen. THe lead is then marked as 'NA' status .

The CLI output is below

Code: Select all


[Mar 18 11:56:25]     -- DAHDI/i1/9836068426-490 answered Local/919836068426@default-000003c6;2
[Mar 18 11:56:25]        > Channel Local/919836068426@default-000003c6;1 was answered.
[Mar 18 11:56:25]     -- Executing [8368@default:1] Playback("Local/919836068426@default-000003c6;1", "sip-silence") in new stack
[Mar 18 11:56:25]     -- <Local/919836068426@default-000003c6;1> Playing 'sip-silence.gsm' (language 'en')
[Mar 18 11:56:25]     -- Executing [h@default:1] AGI("Local/919836068426@default-000003c6;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----11-----0") in new stack
[Mar 18 11:56:26]     -- Executing [8368@default:2] AGI("DAHDI/i1/9836068426-490", "agi://127.0.0.1:4577/call_log") in new stack
[Mar 18 11:56:26]     -- <DAHDI/i1/9836068426-490>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Mar 18 11:56:26]     -- Executing [8368@default:3] AGI("DAHDI/i1/9836068426-490", "agi-VDAD_ALL_outbound.agi,NORMAL-----LB") in new stack
[Mar 18 11:56:26]     -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_outbound.agi
[Mar 18 11:56:26]     -- <Local/919836068426@default-000003c6;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----11-----0 completed, returning 0
[Mar 18 11:56:26]   == Spawn extension (default, 919836068426, 2) exited non-zero on 'Local/919836068426@default-000003c6;2'
[Mar 18 11:56:28]   == Manager 'sendcron' logged on from 127.0.0.1

[Mar 18 11:56:35]     -- <DAHDI/i1/9836068426-490>AGI Script agi-VDAD_ALL_outbound.agi completed, returning 4
[Mar 18 11:56:35]   == Spawn extension (default, 8368, 3) exited non-zero on 'DAHDI/i1/9836068426-490'
[Mar 18 11:56:35]     -- Executing [h@default:1] AGI("DAHDI/i1/9836068426-490", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Mar 18 11:56:35]     -- <DAHDI/i1/9836068426-490>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------- completed, returning 0
[Mar 18 11:56:35]     -- Hungup 'DAHDI/i1/9836068426-490'


Our Dialplan is below :

Code: Select all

exten => _91.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91.,2,Dial(DAHDI/g0/${EXTEN:2},,tTor)
exten => _91.,3,Hangup


Any help would be HIGHLY appreciated.

My vicidial version is VERSION: 2.9-441a
BUILD: 140612-1628

Our carrier settings are :

[siptrunk]
type=friend
username=testcarrier
secret=test
host=myip:5060
dtmfmode=rfc2833
context=inbound
canreinvite=no
disallow=all
allow=g729

slunia wrote:My vicidial version is VERSION: 2.9-441a
BUILD: 140612-1628

Our carrier settings are :

[siptrunk]
type=friend
username=testcarrier
secret=test
host=myip:5060
dtmfmode=rfc2833
context=inbound
canreinvite=no
disallow=all
allow=g729

Good job posting your system specs. Do note that posting on your own topic can make the system believe someone answered you ... better to edit the original post if there are not yet any responses. Then you still appear in the "unanswered posts" list and are more likely to get a response.

You posted the sip context ... for a DAHDI carrier. You'll need to do a bit of research for how to make a DAHDI/ZAP/PRI call work properly which is in NO way related to "SIP" which is a VOIP call.

Have a look here on the forum and in the extensions.conf file which has some notes for PRI configuration.

Also worthy of note: If your inbound calls are working, posting an example of one of those "functional" inbound calls as compared to a a "failing" outbound call would be quite useful.

Many rooms will put the PRI card in a separate "Asterisk Only" server and treat that server as a carrier. Thus the asterisk/PRI interface is all that matters and Vicidial can run "standard" with no special hardware. And the seller of the PRI card can always walk you through asterisk configuration ... solving the vicidial interface problem succinctly.

If you require direct intervention, both The Vicidial Group and Gardo at Goautodial have extensive experience at integrating these PRI cards with Vicidial. Probably handle it in just a few minutes. They are often quite busy, but this is March so you may get lucky. Of course we also handle them, just not as often.

Thanks William, our working inbound example is below :

Code: Select all

   == Manager 'sendcron' logged off from 127.0.0.1
[Mar 19 10:54:01]   == Manager 'sendcron' logged on from 127.0.0.1
[Mar 19 10:54:01]     -- Executing [83047777777777@vicidial-auto:3] Hangup("Local/192*168*001*227*78600053@default-00000010;1", "") in new stack
[Mar 19 10:54:01]   == Spawn extension (vicidial-auto, 83047777777777, 3) exited non-zero on 'Local/192*168*001*227*78600053@default-00000010;1'
[Mar 19 10:54:01]     -- Executing [h@vicidial-auto:1] AGI("Local/192*168*001*227*78600053@default-00000010;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Mar 19 10:54:01]     -- <Local/192*168*001*227*78600053@default-00000010;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
[Mar 19 10:54:01]   == Spawn extension (default, 78600053, 1) exited non-zero on 'Local/192*168*001*227*78600053@default-00000010;2'
[Mar 19 10:54:01]     -- Executing [h@default:1] AGI("Local/192*168*001*227*78600053@default-00000010;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Mar 19 10:54:01]     -- <Local/192*168*001*227*78600053@default-00000010;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------- completed, returning 0
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]   == Manager 'sendcron' logged off from 127.0.0.1
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]     -- Playing 'sip-silence' (escape_digits=) (sample_offset 0)
[Mar 19 10:54:02]     -- <DAHDI/i1/9836068426-b>AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Mar 19 10:54:02]     -- Executing [192*168*001*227*8600053@default:1] Goto("DAHDI/i1/9836068426-b", "default,8600053,1") in new stack
[Mar 19 10:54:02]     -- Goto (default,8600053,1)
[Mar 19 10:54:02]     -- Executing [8600053@default:1] MeetMe("DAHDI/i1/9836068426-b", "8600053,F") in new stack
[Mar 19 10:54:06]   == Manager 'sendcron' logged on from 127.0.0.1
[Mar 19 10:54:06]   == Manager 'sendcron' logged off from 127.0.0.1
[Mar 19 10:54:14]     -- Span 1: Channel 0/2 got hangup request, cause 16
[Mar 19 10:54:14]   == Spawn extension (default, 8600053, 1) exited non-zero on 'DAHDI/i1/9836068426-b'
[Mar 19 10:54:14]     -- Executing [h@default:1] AGI("DAHDI/i1/9836068426-b", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Mar 19 10:54:14]     -- <DAHDI/i1/9836068426-b>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
[Mar 19 10:54:14]     -- Hungup 'DAHDI/i1/9836068426-b'
[Mar 19 10:54:14]   == Manager 'sendcron' logged on from 127.0.0.1
[Mar 19 10:54:14]     -- Executing [8600056@default:1] MeetMe("Local/8600056@default-00000011;2", "8600056,F") in new stack
[Mar 19 10:54:14]        > Channel Local/8600056@default-00000011;1 was answered.
[Mar 19 10:54:14]     -- Executing [9109969711566@default:1] AGI("Local/8600056@default-00000011;1", "agi://127.0.0.1:4577/call_log") in new stack
[Mar 19 10:54:14]   == Manager 'sendcron' logged off from 127.0.0.1
[Mar 19 10:54:14]     -- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=1000))
[Mar 19 10:54:14]     -- <Local/8600056@default-00000011;1>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Mar 19 10:54:14]     -- Executing [9109969711566@default:2] Dial("Local/8600056@default-00000011;1", "DAHDI/g0/09969711566,,tTor") in new stack
[Mar 19 10:54:14]     -- Requested transfer capability: 0x00 - SPEECH
[Mar 19 10:54:14]     -- Called DAHDI/g0/09969711566
[Mar 19 10:54:14]     -- DAHDI/i1/09969711566-c is proceeding passing it to Local/8600056@default-00000011;1
go*CLI>
Disconnected from Asterisk server
[root@go ~]#


The inbound call is being received and connected to the agent successfully. Whereas our outbound call is not being connected to agent after ringing and pickup.

Can you please direct us to where we can resolve this.

Hello,

We are facing same issue.
Is there any solution till today?

pratik wrote:Hello,

We are facing same issue.
Is there any solution till today?

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 and vicidial version with 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 "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. 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) Please provide asterisk CLI output from a single incident (not 3000 lines of text, just one test call that provides an example).

Dear William,

Logs for the auto dialing not working on vicidial 2.12 with Asterisk 1.8.23.0 -vici and Sangoma card - Scratch installation

Code: Select all

[Aug 31 19:37:08] VERBOSE[16194] pbx.c:     -- Executing [22229461054990@default:1] AGI("Console/dsp", "agi://127.0.0.1:4577/call_log") in new stack
[Aug 31 19:37:08] VERBOSE[16194] res_agi.c:     -- <Console/dsp>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Aug 31 19:37:08] VERBOSE[16194] pbx.c:     -- Executing [22229461054990@default:2] Dial("Console/dsp", "DAHDI/g1/09461054990,55,tTo") in new stack
[Aug 31 19:37:08] DEBUG[16194] sig_pri.c: sig_pri_request 32
[Aug 31 19:37:08] DEBUG[16194] sig_pri.c: CALLER NAME:  NUM:
[Aug 31 19:37:08] VERBOSE[16194] sig_pri.c:     -- Requested transfer capability: 0x00 - SPEECH
[Aug 31 19:37:08] VERBOSE[16194] app_dial.c:     -- Called DAHDI/g1/09461054990
[Aug 31 19:37:08] VERBOSE[16194] app_dial.c:     -- DAHDI/i2/09461054990-1 is proceeding passing it to Console/dsp
[Aug 31 19:37:09] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:10] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:11] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:12] VERBOSE[16194] app_dial.c:     -- DAHDI/i2/09461054990-1 is ringing
[Aug 31 19:37:12] VERBOSE[16194] app_dial.c:     -- DAHDI/i2/09461054990-1 is making progress passing it to Console/dsp
[Aug 31 19:37:12] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:13] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:14] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:15] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:16] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory
[Aug 31 19:37:17] WARNING[16194] chan_oss.c: Unable to re-open DSP device /dev/dsp: No such file or directory

If you could help to come across this issue, It would be great,

Configurations for your information

1. dahdi 2.10.1 Version
2. libpri 1.14.15.0 Version
3. Asterisk 1.8.23.0-vici version
4. Vicidial - VERSION: 2.12-505a
5. OS- CentOS 6.5
6. PRI Card - Sangoma A102D
7. Scratch Installation

Server - IBM X3650 M4, Xeon quad core, 32 GB RAM