Optimize dialing, call next number faster

[omarrodriguezt]

Thank you!

[DomeDan]

Oh and by the way.
this has been added to the Vicidial trunk as "Enhanced Disconnect logging" (disabled by default)

[omarrodriguezt]

Great news!
I just downloaded the latest version of vicibox
VERSION: 2.6-385a
BUILD: 121124-1957
Can you please let me know where is located this option?

[DomeDan]

it was added in build 121129-2319 so you need to upgrade using svn

[omarrodriguezt]

I have VERSION: 2.6-385a
BUILD: 121124-1957
© 2012 ViciDial Group

Any idea where can I found that great new option?

[DomeDan]

your version is made 2012-11-24 (24 November 2012)
the new feature was added 2012-11-29 (29 November 2012) that's 5 days after after the version you got.
so when doing a vicibox-install you need to choose the option to "update to latest trunk using svn" or what its called during the installation

[omarrodriguezt]

I have another server, installed just 5 days ago:
VERSION: 2.6-391a
BUILD: 121222-2146

Can you please tell me where is the option?
By the way , what is the name of the text file that explain all the changes that have the newest version?
Thank you in advance!

[DomeDan]

Then it should be under system settings I guess, I haven't upgraded jet
you can view the changes in the svn changelog, talked about here http://vicidial.org/VICIDIALforum/viewt ... =4&t=25129

[omarrodriguezt]

Ok. Thank you very much!

[DarknessBBB]

Thank you very much guys for this useful patch! I was stuck with my provider because we continued to call the same disconnected numbers because they was always archived as NA. After this patch they're correctly archived with DC status. Just one question: where in the world they change automagically status from ADC to DC in vicidial_list?. This seems to be the same behaviour of Domedan's NA.

PS: I cannot update the server until August

VERSION: 2.4-347a
BUILD: 111106-1116
8x Core
16GB RAM
HP Proliant DL 380G5
One server with SIP and PRI Trunks

[Kamui]

Sorry for digging up this topic but I have the same behaviour in Goautodial3.0 - vicidial 2.7 The problem also is that I'm getting too much Hangup cause : 0 and dialstatus sometimes Cancel and sometimes nothing at all (still hangup cause is 0).

"agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------" or "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------"

Does Enhanched DC logging takes care of cause code 0? I have many calls waiting in "ringing" before next call start.

[geoff3dmg]

Cancel with a cause code 0 is usually ViciDIAL hanging up due to dial timeout.

[Kamui]

Really? I thought cause code 0 does not exist in SIP. I get this code usually from my ISDN Patton gateway and I though its a translation - mapping problem between ISDN and SIP.

I'm not getting this from my Sip-trunk line though

[geoff3dmg]

Well it's an asterisk mapping of SIP to ISDN cause codes. But yes. You can check anyway, run a carrier log report.

[Kamui]

Carrier log report....can you help me with that?

I checked many numbers that show up with hangup cause 0. Some of them are active phone numbers and many of them are disconnected numbers.

[geoff3dmg]

Vicidial Admin -> Reports -> Admin Utilities (tiny link at the bottom) -> Carrier Log Report

[Kamui]

And here is the results! Can you suggest anything?

Code: Select all

--- DIAL STATUS BREAKDOWN FOR 2014-07-04, 00:00:00 TO 23:59:59 - server(s) 192.168.1.4
+--------------+-------------+---------+
| HANGUP CAUSE | DIAL STATUS |  COUNT  |
+--------------+-------------+---------+
| 0            | CANCEL      | 4088    |
| 1            | CANCEL      | 1605    |
| 1            | CHANUNAVAIL | 223     |
| 16           | ANSWER      | 2923    |
| 16           | NOANSWER    | 18      |
| 17           | BUSY        | 217     |
| 19           | CONGESTION  | 224     |
| 21           | CANCEL      | 3       |
| 22           | CONGESTION  | 3       |
| 27           | CONGESTION  | 27      |
| 34           | CONGESTION  | 4523    |
| 38           | CONGESTION  | 802     |
+--------------+-------------+---------+
|                      TOTAL | 14656   |
+--------------+-------------+---------+


--- SIP ERROR REASON BREAKDOWN FOR 2014-07-04, 00:00:00 TO 23:59:59 - server(s) 192.168.1.4
+----------+--------------------------------+---------+
| SIP CODE | SIP HANGUP REASON              |  COUNT  |
+----------+--------------------------------+---------+
|        0 |                                | 7240    |
|      403 | Forbidden                      | 5       |
|      404 | Not Foun                       | 1       |
|      404 | Not found                      | 1807    |
|      410 | Gone                           | 3       |
|      480 | Temporarily unavailable        | 206     |
|      484 | Address incomplete             | 11      |
|      486 | Busy Here                      | 201     |
|      487 | Request Terminated             | 8       |
|      500 | Internal Server Error          | 4       |
|      500 | Server internal error          | 761     |
|      502 | Bad Gateway                    | 25      |
|      503 | Service Unavailable            | 4384    |
+----------+--------------------------------+---------+
|                                     TOTAL | 14656   |
+-------------------------------------------+---------+


I'm getting most of the 0 from the ISDN Patton gateway (4 X 2 channel ISDN). From logs these 0s comes almost instantly on many calls. I suspect something is not working right with that piece of hardware. Need to find a manual

And please can you explain me this line

305847 | 16 | ANSWER | Local/9302721084338@default-00007d2f;... | 18 | 0 | 0 | |

ISDN sip code is 16 answer but on SIP comes as 0. Does it mean that the customer answered but no agent served, so the call timed out? (or in simple words DROP)