Page 1 of 1

manual dial handling DC's

PostPosted: Fri Apr 21, 2023 8:47 am
by dreedy
Hello,

I am curious if it is possible to have a function with the Settings container to do a sip action on a disconnected number. When i look up the logs on the hangup cause report. I see that a disconnected is treated as a

Hangup cause 1
Dial Time 0
Answered Time 0
and
Sip Response 404

is it possible to use this as a vector to auto dispo all calls like this ? say a sip_event of 404 was seen in the lookup. would that be enough to auto dispo this call?

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 9:31 am
by jamiemurray
SIP 404 dispos as ADC (Disconnected Number Auto) anyway by default. What are you trying to achieve?

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 10:11 am
by dreedy
The ADC doesn't capture all the DC's. we manual dial and on DC's the call will ring for a sec and then upwards of 20 seconds later the call will bring up a small green screen with cause 1 sip 404 and the user has to click to close box and dispo the lead. I am trying to find a way to automate that so the user doesn't have to interact with that number. or take time to wait for the call to identify as a disconnected.

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 10:49 am
by jamiemurray
Ah I got ya, actually the lead will likely be dispo'd ADC by FASTagi upon receipt of the 404, but since the agent has the lead on their screen, their chosen disposition when they hangup will override it for that call.

AFAIK there's no way currently to handle these automaically unless you're on a non manual dial method.

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 10:54 am
by dreedy
even if i could get the time down to a second or two that would be great. that is why i am looking at the container setting to see if i can get the notification to go faster.

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 11:09 am
by martinch
Hey dreedy,

Not aware of such functionality in ViCiDial but sounds like a good feature. Makes manual dialling a bit more productive I guess. I would call such a feature a "hardcore" dialler feature though as it circumvents the will of the agent! lol I can take a look at proposing this feature request to the team for this if you like? It would be somewhat simple to implement.

Something like the below;

  • Campaign Option - Auto Dispo Dead Calls (Y/N)
  • Campaign Option - Auto Dispo Dispo Code (Status Code for Campaign)
  • Dialler code to perform the automatic dispositions (via JavaScript)
  • Potentially a timer (just to let the agent know what is about to happen).

Hope this helps.

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 11:30 am
by jamiemurray
An even simpler implementation could be to introduce a new system setting to enable or disable automatic handling of these system wide.

Around line 1357 of FastAGI_log.pl is where disconnected numbers are handled.
A check could be made to see if the feature is active and if so look to see if the call being processed was the result of a manual campaign dialed call. If this is true, set the hangup and dispo on the live agents table for that user and perhaps display some notification on their screen that it was a disconnected number.

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 1:17 pm
by dreedy
martinch.

would a disconnected number be counted as a DEAD CALL?

Would it be better to go off SIP 404 message ?

I do like having the option of disposition type and the java script taking care of the call.

As for feedback for the rep making the call instead of taking time to notify them that an action is going to take place. Maybe have a small audio sounds that indicates this was a disconnected number.

you could actually do this with busy signals also as the SIP 486 would be issues. and you could play an audio file for that action.

after the audio file plays then next lead populates.


jammiemurray.

Does the FastAGI_log.pl work also in a manual dial scenario?

Re: SIP EVENT ACTIONS

PostPosted: Fri Apr 21, 2023 2:04 pm
by jamiemurray
FastAGI is called on every call hangup regardless if it's manual, auto or inbound, it's what takes care of closing out the logs out etc.