CID lookup on inbound

[mms1]

We have inbound campaigns setup and working great; however, i do have a question about how the CID lookup works. I know that when a call comes in, the lookup searches the record on the phone number and if found sends that record to a rep logged in to an in-group associated with the dialed phone number.

I was wondering if there was a way to implement some sort of filter to make sure that the looked up record is associated with the campaign that the rep is logged into. (campaign_id or list_id match the campaign that the in-group is associated with).

I am asking this question because occasionally we are getting the wrong record pulled up on the rep's screen. For example, 2 people exist in two different lists we are calling but work at the same company that share outbound phone lines. Person A calls in to our system and the record for Person B gets pulled instead because that is also his work phone number. They are in our system in completely separate lists and campaigns so if there was a filter then this would not occur.

Any help or insight is much appreciated!

Thanks!
Alex

[aouyar]

Hi Alex,

The first argument of agi-VDAD_ALL_inbound.agi in extensions.conf sets the search method. Straight out of extensions.conf:
; - CIDLOOKUP - Lookup CID to find record in whole system
; - CIDLOOKUPRL - Restrict lookup to one list
; - CIDLOOKUPRC - Restrict lookup to one campaign's lists

Bye

[mflorell]

astguiclient version?

[mms1]

Thanks for the info on:
- CIDLOOKUP - Lookup CID to find record in whole system
; - CIDLOOKUPRL - Restrict lookup to one list
; - CIDLOOKUPRC - Restrict lookup to one campaign's lists

Ill def. look into this in the morning. I think currently we only use CIDLOOKUP in our extensions.conf file.

Matt, I'll check the astguiclient version we are using in the morning and then post.

Thanks!

Alex

[mms1]

VERSION: 2.0.5-134 BUILD: 80703-0124

[mflorell]

It sounds like you would want to change to using CIDLOOKUPRC

Since you are using SVN trunk you might want to consider upgrading to the latest revision, we've added a lot of new features like inbound DID configuration from within the admin interface.

[mms1]

Thanks, CIDLOOKUPRC worked great!

[linuxknight]

When using the CIDLOOKUPRC method and multiple leads possibly exist within the campaign lists, what is the order of preference for the lookup result? Do the results prefer entry_date or last_called_date? (maybe something else?)

[mflorell]

order by last_local_call_time desc

[linuxknight]

Thank you Matt