Page 1 of 1

Unique ID and Channel are not being updated

PostPosted: Tue Feb 11, 2014 1:45 pm
by viciboy
Hi guys,

I was customizing vicidial for predicitive campaigns but when I transfer the call to any number it adds record in vicidial manager but it doesn't update unique_id, channel and status fileds, that's why It does't hangup the call because it needs this info(channel) for hanging up the call.



| Debian OS Kernel/V2.6.18-5-686|
|(DB-MySQL v5.0.3.2)|
|(Dialer-Vicidial:Asterisk 1.4.21.2-vici)|
|(Web-ApacheV2.2.3)|
|Perl:v5.8.8|PHP:v5.2.0-8+etch7|
|AstGuiClient V2.4-308a Bld:110428-1108|

Re: Unique ID and Channel are not being updated

PostPosted: Tue Feb 11, 2014 1:56 pm
by viciboy
look at vicidial manager table

Code: Select all
+----------+----------------+-------------------+
| man_id   | uniqueid       | channel           |
+----------+----------------+-------------------+
| 17640032 |                 |                          |
| 17640031 | 1392091264.533 | SIP/XXXXXXXXXX-000000ba |

Re: Unique ID and Channel are not being updated

PostPosted: Wed Feb 12, 2014 12:05 am
by williamconley
You should describe the method of "transfer" in detail. I mean button for button (change the last four digits to "9999" if there's a private phone number involved). Also post your carrier settings for all legs of the call (inbound, outbound, transfer, anything).

Not a bad idea to post CLI sample from an occurrence. Just for fun. 8-)

Note also that if you have modified "extensions.conf", you likely introduced a bug by doing so. The same applies to "custom dialplan entries" anywhere in the Vicidial Interface. Any context in extensions.conf (anywhere, even included files) must have the pre-requisite ,h, extension that harvests this data at the termination of the call and performs necessary actions (like updating dates and times, and possibly even terminating the call). Also, carrier entries must have all three required lines as an absolute minimum (the agi line, the dial line, and the hangup line).

If indeed you have a bug, an upgrade may be in order ... but I suspect it's something more like a configuration error. Just a guess though. Let us know. :)