Page 1 of 1

Custom Caller Id in security_phrase

PostPosted: Thu Nov 04, 2010 11:19 am
by spinto
I can’t seem to get this working. I have the Custom Callerid field in the campaigns settings to “Y”.

I have a phone number in the security_phrase for that lead, but for some reason it’s always using the campaign caller id.

I tried several different numbers for the caller id in the campaign settings (to make sure the carrier allows custom caller id) and it always uses those numbers instead of the security_phrase. Is there additional setting I should be looking at?

PostPosted: Thu Nov 04, 2010 1:48 pm
by williamconley
when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

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.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

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)
______________

Especially your vicidial version and build have a huge impact on this issue. never post without it.

PostPosted: Fri Nov 05, 2010 9:42 am
by spinto
Version: 2.4b0.5
Asterisk: Asterisk 1.4.21.2
Single Server
No Digium/Sangoma Hardware
No extra software

PostPosted: Fri Nov 05, 2010 9:51 am
by williamconley
williamconley wrote:when you post, please post ... and vicidial version with build.

PostPosted: Fri Nov 05, 2010 11:05 am
by spinto
VERSION: 2.4-285
BUILD: 101022-1427

RE: security_phrase

PostPosted: Mon Nov 08, 2010 1:53 am
by hackerx
spinto wrote:VERSION: 2.4-285
BUILD: 101022-1427


The following is my server config:

Software:
OpenSuSE v.11.3 32-bit w/ PAE
Linux Kernel v.2.6.34.7
Asterisk v.1.4.27.1-vici
Dahdi v.2.3.0.1
ViciDial v.2.2.1 and SVN v.2.4-285 Build 101022-1427

Hardware:
Quad-Core CPU
160GB Hard Drive
4-GB RAM

I am facing the same issue. I first downloaded the one of the sample lists and then modified it to use only the fields I was interested in. Namely the "phone_number" and "security_phrase" fields.

I put numbers in the phone_number column and CIDs in the security_phrase field for each number. The Custom CallerID option is set to "Y" and the Campaign CallerID field is empty.

I have tried this with .csv formatted files and .xls formatted files. I have tried this with "anonymous", and "unknown", and "0000000000" in the Campaign CallerID field with the Customer CallerID option set to "Y".

I have confirmed that the provider can accept custom CallerID. I have even tried to send the calls to another voip server that I control so that I can see if the caller ID is being sent there. I know that this other server accepts callerID.

I don't know where else to look or what else to try that makes sense. Any suggestions?

PostPosted: Mon Nov 08, 2010 4:41 am
by mflorell
We have several clients using this and I just tested it on our dev server and it is working properly on the latest 2.4

PostPosted: Mon Nov 08, 2010 4:54 am
by hackerx
mflorell wrote:We have several clients using this and I just tested it on our dev server and it is working properly on the latest 2.4


Mike,

Then is there any reason you can think of that it wouldn't be working based on what I have told you about my setup and how I am attempting to use it?

It seems pretty straightforward to me which is why I am amazed that it's not working.

One more thing I would like to add is that my installation is a Vicibox Server install with no modifications or additional software. It's as plain-jane as it can be.

TIA

PostPosted: Mon Nov 08, 2010 9:05 am
by mflorell
It should be rather straightforward, I would suggest checking the vicidial_manager records to see what those say the CID is being sent as.

PostPosted: Mon Nov 08, 2010 12:15 pm
by hackerx
mflorell wrote:It should be rather straightforward, I would suggest checking the vicidial_manager records to see what those say the CID is being sent as.


Well I checked the records and indeed the CID was being sent as expected. However what was showing on the intermediate voip server was still the "anonymous".

So I started thinking about where in the configuration was "anonymous" still present. As it turns out I was using SIP registration from the VICI server to the voip server. The username was "anonymous".

Once I removed the SIP registration string in the Carrier record and basically changed to insecure and peer for Carrier record, the CID started passing as expected.

Since my intermediate server is desired anyway this method works fine for me. I am not sure why the registration username would override any CID which is being sent on a per call basis but perhaps this a design of Asterisk which I am not aware of currently. I am for all intents and purposes an Asterisk newbie so if anyone else cares to elaborate on this please do so.


UPDATE: actually I believe I have figured out what the issue was. I was also using the "fromuser" option in the sip-vicidial.conf. This was also set to "anonymous". A subsequent check on the internet shows that this option will in fact override the CID being sent with itself.

I am going to validate this by returning to the scenario where my VICI server registers to my intermediate voip server but without the "fromuser" option. I will update with my results.

TIA

PostPosted: Mon Nov 08, 2010 12:45 pm
by williamconley
nice postback. :D

PostPosted: Mon Nov 08, 2010 1:42 pm
by hackerx
williamconley wrote:nice postback. :D


Thanks William.

Indeed. I have confirmed that the root cause of my issue was having the "fromuser" option defined in the Carrier record for my target carrier.

What I am using now is in the following format:
[VOIPCARRIER]
disallow=all
allow=g729
type=peer
username=xxxxxxxxxx
secret=xxxxxxxxxx
insecure=port,invite
host=10.10.10.10
fromdomain=10.10.10.10
dtmfmode=rfc2833
context=trunkinbound

Also here is the definition for the "fromuser" option as listed on www.voip-info.org/wiki/view/Asterisk+config+sip.conf

fromuser = <from_ID> : Specify user to put in "from" instead of $CALLERID(number) (overrides the callerid) when placing calls _to_ peer (another SIP proxy). Valid only for type=peer.

I hope this helps someone.

TIA

PostPosted: Mon Nov 08, 2010 1:50 pm
by covarrubiasgg
hackerx wrote:
fromuser = <from_ID> : Specify user to put in "from" instead of $CALLERID(number) (overrides the callerid) when placing calls _to_ peer (another SIP proxy). Valid only for type=peer.


This explains a lot of caller id issues i had before, thank you very much for your feedback.

PostPosted: Mon Nov 08, 2010 2:44 pm
by gardo
This is very helpful indeed. Thanks guys for posting your solutions. 8)