Callerid vs calleridname

[Keyfin]

I'm using Voxox as one of our carriers, and the problem with some calls is with the caller id.

Code: Select all

2017-07-10 12:00:38|agi-VDAD_inbound_calltime_check.agi| -- callerid = 803XXXXXXX
2017-07-10 12:00:38|agi-VDAD_inbound_calltime_check.agi| -- calleridname = Y7101154350002145012

Code: Select all

2017-06-27 10:06:36|VDfastAGI|begin| -- callerid = 704XXXXXXX
2017-06-27 10:06:36|VDfastAGI|begin| -- calleridname = Y6271005490002127922

on these calls the scripting puts the calleridname into vici for the customer's phone number. How do I get it to ignore the calleridname and just use the callerid?

[mflorell]

We've noticed some carriers now passing the CIDname on with some calls in the US, although it seems to be somewhat random depending on what their routing equipment supports and where you are calling.

This is one of the reasons we started building VICInoc(http://www.vicinoc.com), so that you could have an OpenSIPs setup that would filter out the CIDname on outgoing calls.

The other option is to send calls through a loopback IAX trunk and clear out the CIDname at that point, but that will raise the load on your dialers.

[Keyfin]

any way to get something like this to work?
exten => _61NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _61NXXNXXXXXX,n,Set(CALLERID(name)=${CALLERID(num)})
exten => _61NXXNXXXXXX,n,Dial(${DIAL6TRUNK}/+1${EXTEN:2})
exten => _61NXXNXXXXXX,n,Dial(${DIAL8TRUNK}/+1${EXTEN:2})
exten => _61NXXNXXXXXX,n,Hangup

exten => _6NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _6NXXNXXXXXX,n,Dial(${DIAL6TRUNK}/+1${EXTEN:1})
exten => _6NXXNXXXXXX,n,Hangup

[mflorell]

You have to send the calls through the IAX loopback trunk, and make sure you don't log them at that point.

Take a look at the [loopback-no-log] context in the default extensions.conf

[Keyfin]

i'm attempting this...
excerpt from extensions.conf

Code: Select all

#include extensions-vicidial.conf

[trunkinbound]
; DID call routing process
; exten => _XXXXXXXXXX,1,AGI(agi-DID_route.agi)  ; use this one instead of the one below if you are having delay issues, and match to number of received digits
exten => _X.,1,Set(CALLERID(num)=${CALLERID(num)})
exten => _X.,2,Set(CALLERID(name)=${CALLERID(num)})
exten => _X.,3,AGI(agi-DID_route.agi)
exten => _X.,n,Hangup()
; If you have DIDs that arrive with a plus sign at the beginning then uncomment
exten => _+X.,1,AGI(agi-DID_route.agi)
exten => _+X.,n,Hangup()
; If you have DIDs that arrive with a plus and 1 at the beginning that you want to filter out, then uncomment
exten => _+1X.,1,Goto(trunkinbound,${EXTEN:2},1)


it did not stop the inbound calls, now let's see if it will stop the Y##### caller ids in vici

[Keyfin]

I think this actually worked. It seems to be putting the CID(num) into the CID(name) in the VDAD report! I'll post again, if I get another Y################### as the caller id on the agent screen.

[Keyfin]

hmm, this is from the agiout log.... does this seem correct with what I did?

Code: Select all

2017-07-25 12:19:23|12:19:23|agi-VDAD_ALL_inbound.agi|callerID changed: "Y7251219230002168024 <614XXXXXXX>"

the number for this call did show up correct in the agent screen

[Keyfin]

ok, i think i got it now

Code: Select all

[Jul 25 14:07:54]   == Using SIP RTP CoS mark 5
[Jul 25 14:07:54]     -- Executing [18XXXXXXXX@trunkinbound:1] Set("SIP/Voxox-00002cdf", "CALLERID(num)=646XXXXXXX") in new stack
[Jul 25 14:07:54]     -- Executing [18XXXXXXXX@trunkinbound:2] Set("SIP/Voxox-00002cdf", "CALLERID(name)=646XXXXXXX") in new stack
[Jul 25 14:07:54]     -- Executing [18XXXXXXXX@trunkinbound:3] AGI("SIP/Voxox-00002cdf", "agi-DID_route.agi") in new stack


updated earlier post with the correct DID inbound settings in the extension.conf file

[mflorell]

Thanks for the post-back with your solution!

[Keyfin]

of course, thanks for putting together a magnificent PBX!

[uselessinfoguru]

after a couple of weeks, the Y numbers are still coming. The previous post did work, the asterisk cli output shows every inbound call setting the calleridnum and calleridname, but this doesn't affect what shows up in the agent screen, and thus how the lead is put into the system and all the reports and the recording file for those leads.