All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by Vince-0 » Fri Apr 21, 2017 9:17 am
Hi!
I have an issue with a list where I find leads with status NEW but call count of 3:
CALLED COUNTS WITHIN THIS LIST:
STATUS STATUS NAME 1 2 3 4 5 6 7 SUBTOTAL
NEW New Lead 95
If I check any of these 95 leads they show no call log but there are recording logs with 0 duration.
I'm sure these numbers don't connect but surely the status should change away from NEW.
My problem is it looks like we have used these leads from the call count when in fact they are still in status NEW.
Please advise on any way to figure out how these got like this?
--
Vicibox 7.0.4 ISO + SVN upgrade
VERSION: 2.14-610a
BUILD: 170416-1548
-
Vince-0
-
- Posts: 272
- Joined: Fri Mar 02, 2012 4:27 pm
- Location: South Africa
by Vince-0 » Fri May 19, 2017 6:30 am
I've investigated these further and have found similar symptoms on my servers on different carriers.
The carrier says Asterisk is hanging up the call but their CDR shows a couple of seconds set up time and zero duration.
I have run these new leads with called count 1 through the campaign on auto-dial without AMD and have found that a lot of them do connect.
I am investigating further.
-
Vince-0
-
- Posts: 272
- Joined: Fri Mar 02, 2012 4:27 pm
- Location: South Africa
by Vince-0 » Fri May 19, 2017 7:52 am
Here's an example from the console where the lead was NEW, I put it back in a second time without AMD after list reset and it stays NEW a second time. This happened for 1778 out of 9879 leads. This happened using multi-alt settings but I see it happening without multi-alt.
Why is it staying in NEW when it looks like its a NA from the CANCEL line?
XX used for censoring.
- Code: Select all
tail -f -n 100000 /var/log/asterisk/messages | grep 72XXXXXXX
[May 19 14:16:06] VERBOSE[11695][C-00004538] pbx.c: [May 19 14:16:06] -- Executing [999072XXXXXXX@default:1] AGI("Local/999072XXXXXXX@default-0000438f;2", "agi://127.0.0.1:4577/call_log") in new stack
[May 19 14:16:06] VERBOSE[11695][C-00004538] res_agi.c: [May 19 14:16:06] -- <Local/999072XXXXXXX@default-0000438f;2>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[May 19 14:16:06] VERBOSE[11695][C-00004538] pbx.c: [May 19 14:16:06] -- Executing [999072XXXXXXX@default:2] Dial("Local/999072XXXXXXX@default-0000438f;2", "SIP/bizvoip1/072XXXXXXX,,To") in new stack
[May 19 14:16:06] VERBOSE[11695][C-00004538] app_dial.c: [May 19 14:16:06] -- Called SIP/bizvoip1/072XXXXXXX
[May 19 14:16:06] VERBOSE[11695][C-00004538] app_dial.c: [May 19 14:16:06] -- SIP/bizvoip1-0000380b is making progress passing it to Local/999072XXXXXXX@default-0000438f;2
[May 19 14:16:22] VERBOSE[11695][C-00004538] app_dial.c: [May 19 14:16:22] -- SIP/bizvoip1-0000380b requested media update control 26, passing it to Local/999072XXXXXXX@default-0000438f;2
[May 19 14:16:22] VERBOSE[11695][C-00004538] app_dial.c: [May 19 14:16:22] -- SIP/bizvoip1-0000380b is making progress passing it to Local/999072XXXXXXX@default-0000438f;2
[May 19 14:16:28] VERBOSE[11695][C-00004538] pbx.c: [May 19 14:16:28] == Spawn extension (default, 999072XXXXXXX, 2) exited non-zero on 'Local/999072XXXXXXX@default-0000438f;2'
[May 19 14:16:28] VERBOSE[11695][C-00004538] pbx.c: [May 19 14:16:28] -- Executing [h@default:1] AGI("Local/999072XXXXXXX@default-0000438f;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------") in new stack
[May 19 14:16:29] VERBOSE[11695][C-00004538] res_agi.c: [May 19 14:16:29] -- <Local/999072XXXXXXX@default-0000438f;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL---------- completed, returning 0
-
Vince-0
-
- Posts: 272
- Joined: Fri Mar 02, 2012 4:27 pm
- Location: South Africa
Return to Support
Who is online
Users browsing this forum: Google [Bot] and 28 guests