Page 1 of 1

inbound Anonymous Calls

PostPosted: Thu Jul 28, 2011 10:47 am
by fibres
Hi

I have just changed my CID lookup so it checks all lists in my system, However this is causing a major issue.

When a caller calls in witholding their number our trunk passes the callerid name as "anonymous" the issue is that vicidial is treating this as a callerid and looking it up in database.

Therefore once a customer first calls in as anonymous it creates a new record and gives it a lead_id. after this point every other person who calls in gets matched to the new record and classed as same caller.

Any ideas on how to resolve this?

We only use CID(number) in the UK there is no CID(name) except for anonymous calls so would putting something in the dial plan to blank the CID(name) solve the problem?

Regards

PostPosted: Thu Jul 28, 2011 11:27 am
by mflorell
Is the CIDnumber coming in as Anonymous?

I have seen this happen, and there really isn't too much you can do about it except for blocking those in the dialplan if you don't want them, or possibly sending them to another in-group through the dialplan.

PostPosted: Thu Jul 28, 2011 12:45 pm
by fibres
Hi
Luckily in my setup it is coming in as CID(name)

I have therefore implemented the following in the dial plan which has fixed the issue


; DID call routing process
exten => _X.,1,Set(CALLERID(num)=${CALLERID(num):1})
exten => _X.,2,Set(CALLERID(name)="")
exten => _X.,3,AGI(agi-DID_route.agi)


Note: The exten => _X.,1,Set(CALLERID(num)=${CALLERID(num):1}) line removes the first digit from the received callerid number as this is needed for lookup to work in the UK with the setup we have.

Regards

Re: inbound Anonymous Calls

PostPosted: Thu May 31, 2012 12:34 am
by mnguyen
fibres I realize this is an old topic but Im having the same issue with anonymous lead_ids,
where exactly did you add this dial plan option?
Under which category?

Any help would be appreciated, Thank You.