Page 1 of 1

status "NEW" and called_since_last_reset ="Y" ???

PostPosted: Tue May 06, 2014 8:37 am
by binis
Hello
I'm new to the forum, I'd like to know what it means that a lead is "NEW" as status and called_since_last_reset = "Y".

if Is the system tried to call the lead and the call was not successful in this case why it is always "NEW", and if the system does not try to call the lead why it changes called_since_last_reset from "N" to "Y".

Re: status "NEW" and called_since_last_reset ="Y" ???

PostPosted: Wed May 07, 2014 6:07 pm
by Staydog
It should not, unless someone added a dupe lead that is new or manually changed the disposition. All leads are NEW one time: when they are first entered and have not been called. Where are you seeing this statement?

Re: status "NEW" and called_since_last_reset ="Y" ???

PostPosted: Thu May 08, 2014 3:56 am
by geoff3dmg
On older ViciDIAL installs this can happen due to local channel resolution errors or some carrier issues. On newer ViciDIAL installs the former is dis-positioned as LRERR and the latter is handled if you have 'enhanced disconnect logging' enabled whereby you get dispositions of ADC/ADCT.

Re: status "NEW" and called_since_last_reset ="Y" ???

PostPosted: Mon Jul 07, 2014 12:23 am
by williamconley
binis wrote:Hello
I'm new to the forum, I'd like to know what it means that a lead is "NEW" as status and called_since_last_reset = "Y".

if Is the system tried to call the lead and the call was not successful in this case why it is always "NEW", and if the system does not try to call the lead why it changes called_since_last_reset from "N" to "Y".

1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) As Geoff3DMG says, older systems can have this happen ... but even newer ones can have this happen in case of serious configuration issues. If your carrier is not set up properly, or if the entire Vicidial install is "bad" just about anything can happen (including a call being made and then ... lost ... because the agi script in the first priority of the carrier is never initiated). So ... post your specs (and perhaps your carrier dialplan entry under Admin->Carriers->"Dialplan Entry") and we'll begin to work this through for you.

Happy Hunting! 8-)