QueueMetrics forum

WombatDialer => Running WombatDialer => Topic started by: pguima on September 24, 2014, 18:50:00

Title: Appt confirmation - solved
Post by: pguima on September 24, 2014, 18:50:00
I am testing wombat with the appointment confirmation and everything is working so far the only issue is that the confirmation status does not work all the time.

Where can i set debug or detail logging to figure out the situation.

Thank you.

pguima
Title: Re: Appt confirmation
Post by: QueueMetrics on September 25, 2014, 09:26:53
Can you explain what is not working? make sure your Asterisk systems does emit events before the call is hung up.
As a part of our quality process for releasing WD, we do a test of direct dialing with generated response events and we get 100% of events on about one million calls at 100 parallel calls per servers on two parallel servers, so we are pretty much sure it works.
Title: Re: Appt confirmation
Post by: pguima on September 25, 2014, 15:31:54
I understand the system works, I am trying to figure out why it is not working 100% on my system. The extended status with the callee's response does not show up everytime. I am attaching an image of the report.(http://s7.postimg.org/t5zhfvk3f/Capture.png)
Title: Re: Appt confirmation
Post by: QueueMetrics on September 25, 2014, 17:16:58
I would add a wait time after sending the event (if you do this before you hang up) to make sure Wombat received the events in order.
Title: Re: Appt confirmation
Post by: pguima on September 25, 2014, 18:40:16
I added a 2 second wait on the dialplan but it did not work. Can I add a pause between 2 calls in wombat?

Title: Re: Appt confirmation
Post by: pguima on September 25, 2014, 21:16:21
I noticed on the reports when a call has w/pre greater than 1 my wombat is able to grab the response but when the w/pre is equal wombat does not record the answer.

I am not sure where I can force wombat to add a wait time before placing other calls.

This is what my dialplan looks like:

Code: [Select]
[drstrangelove]
exten => s,1,Answer
exten => s,n,Set(TIMEOUT(response)=5)
exten => s,n,UserEvent(CALLSTATUS,Uniqueid:${UNIQUEID},V:0)
exten => s,n(start),agi(googletts.agi,"Your appointment with doctor Frankstein is for tomorrow at ${HH} ${MM}")
exten => s,n(confirm),agi(googletts.agi,"Press 1 to confirm the appointment")
exten => s,n,agi(googletts.agi,"or 2 to cancel it.")
exten => s,n,Read(conf,,1)
exten => s,n,GotoIf($["${conf}" = "1"]?ok)
exten => s,n,GotoIf($["${conf}" = "2"]?ko)
exten => s,n,Goto(confirm)
exten => s,n(ok),UserEvent(CALLSTATUS,Uniqueid:${UNIQUEID},V:1)
exten => s,n,wait(5)
exten => s,n,agi(googletts.agi,"The appointment was confirmed. See you tomorrow.")
exten => s,n,Hangup
exten => s,n(ko),UserEvent(CALLSTATUS,Uniqueid:${UNIQUEID},V:2)
exten => s,n,wait(5)
exten => s,n,agi(googletts.agi,"Boo the appointment was cancelled.")
exten => s,n,Hangup

Thank you in advance for any input.
Title: Re: Appt confirmation
Post by: pguima on September 26, 2014, 17:37:37
We can call it solved. Since I am running this test server on a VM, all I had to do is lower the number of messages on the AMI settings and now wombat catches all the responses.

pguima
Title: Re: Appt confirmation - solved
Post by: QueueMetrics on January 18, 2015, 12:26:53
 ;D