provided by Star2Billing S.L.

Customer is connecting via SIP phone.
I have managed to pass callerID out via editing the CALLERID field with the SIP settings.
What I want to do however now is to disable the callerID and make his outgoing calls to appear anonymous.
Leaving the CALLERID empty or putting any of the following does not work: anonymous, 'hidden', "hidden".
While having any of those the result is that the ACCOUNTCODE (or USERNAME) is passed down to the trunk as the CALLERID. This of course sends an invalid callerid.

How do I make it anonymous

Thank you,

N

There are two ways to block outbound Caller ID. The first method is the best and "real" way and it sends up a Privacy flag to the remote provider. The second way simply sets the caller ID to something like 0000000000 and people will think this is a commercial telemarketing caller that blocked their number.

The first method will only work if your sip carrier can read sip headers. You will need to test call your mobile or another phone to see whether or not this is the case. REMEMBER- if you are using LCR you need to make sure this works on ALL carriers. Not all my carriers "accept" the sip headers I send for method one so I have a special setup to send the private calls to specific carriers only. I can post instructions here upon request. The second method will work out of the box with all carriers. Note that for the first method, a2billing out of the box does not read the sip headers received by another PBX, so this caller ID blocking script must be configured on your a2billing server right under the [a2billing-whatever] line.

First method


Method 2 (can be programmed on the remote PBX side instead of a2billing side)

First, Make sure you have done the settings as described here http://www.voip-info.org/wiki/view/Asterisk+sip+sendrpid

Secondly, just by buying a SIP account from your VoIP provider you cannot take control of the Caller ID you are sending to the last mile. It all depends on how each carriers on the path process your Caller ID. If your Caller ID is a E.164 format then you can be sure that it is delivered properly else its hopeless.

Vinod

I know that, but in my case I want to NOT send anything (including the account number that goes out now). I want to be sent as anonymous.

Hi there and thank you for the answer.

Assuming I want to go with option 1, where do I put that?
A bit lost here!
Any help is much appreciated.

In extensions.conf you should see some a2billing contexts there. When other users interconnect with your a2billing system, you are using one of those contexts for routing. For me it is a2billing-sip. You can check it out under customers-voip settings and you will see the context there. Depending on what you are using your a2billing for, it may very well be the default [a2billing]. You want to put the script right under the context name, before all the other stuff.

Hi I'm having this exact same problem. Our customer's asterisk server is connected with our A2Billing server. I can see in the CLI that we are receiving calls from the customer with the following flags privacy=full and screen=yes. After a lot of tweaking and before I found this post I set trustrpid=yes and sendrpid=yes in sip_custom.conf. Which got me part way there, but A2Billing is still passing calls on to the carriers with privacy=full and screen=no. Any help with this would be much appreciated.

Hi All,

I'm also having the same issue.

I created a context called 'a2billing-private' and put in the following code...

[a2billing-private]
exten => _X.,1,SIPAddHeader(P-Preferred-Identity: <sip:${CALLERID(num)};user=phone>)
exten => _X.,n,SIPAddHeader(Privacy: id)
exten => _X.,n,Goto(a2billing,${EXTEN},1)
exten => _X.,n,Hangup()

I was talking to our carrier and they captured a few snapshots of what I’m sending them and why Hidden CallerID isn’t working.

Eg. 1. Via A2Billing using extension 45000 using ‘a2billing-private’ Context

Remote-Party-ID: "hidden" <sip:Unknown@myserverip>;privacy=off;screen=no'

Where it should be something like this ...

Remote-Party-ID: "hidden" <sip:217654321@myserverip>;privacy=full;screen=no'



Eg. 2. Via FreePBX using ext 10001 with CallerID set to ‘”hidden”<217654321>’

Remote-Party-ID: "hidden" <sip:217654321@myserverip>; privacy=full;screen=yes'

THIS WORKS PERFECTLY

## Note that even though we want the CallerID to be hidden, we still need to pass the number through to our Carrier.
## It’s the ‘privacy=full’ bit that hides the CallerID to the rest of the world.

The problem is, I can't seem to get extensions behind A2Billing to set the privacy=full bit.

Any Ideas out there???

Max

Found a solution!!!

Add this code to the bottom of your a2billing_extensions.conf file via the 'Config Editor' under the 'System Setting' menu...

[a2billing-private]
exten => _.,1,SetCallerPres(prohib_not_screened)
exten => _.,n,Goto(a2billing,${EXTEN},1)
exten => _.,n,Hangup()

Then just change the context used by the extension from the default 'a2billing' to 'a2billing-private', in the A2Billing - 'VoIP Settings' Menu.

#################################################################

For anybody interested, here's how I found it....

I was looking through fourms and came across this thread...

http://forums.digium.com/viewtopic.php?p=7164

And in it there was this post...



So I added the following to a2billing_extensions.conf...

exten => _X,1,SetCallerPres(prohib_not_screened)

But this didn’t work initially.


My a2billing-private context was now...

[a2billing-private]
exten => _X,1,SetCallerPres(prohib_not_screened)
exten => _X.,1,SIPAddHeader(P-Preferred-Identity: <sip:${CALLERID(num)};user=phone>)
exten => _X.,n,SIPAddHeader(Privacy: id)
exten => _X.,n,Goto(a2billing,${EXTEN},1)
exten => _X.,n,Hangup()


I was looking at a capture I did with ‘sip set debug peer 45000’ in the Asterisk CLI, and I noticed this line...

Looking for 0867926342 in a2billing-private (domain 88.151.26.100)
list_route: hop: <sip:[email protected]:55136>

It occurred to me that that perhaps the number I’m dialling isn’t getting pattern matched to the context.

So I changed the context to...

[a2billing-private]
exten => _0867926342.,1,SetCallerPres(prohib_not_screened)
exten => _0867926342.,1,SIPAddHeader(P-Preferred-Identity: <sip:${CALLERID(num)};user=phone>)
exten => _0867926342.,n,SIPAddHeader(Privacy: id)
exten => _0867926342.,n,Goto(a2billing,${EXTEN},1)
exten => _0867926342.,n,Hangup()

This Worked!!!!

I then ‘;’ or commented out each of the top three lines one at a time, to find out which one was actually doing the job, and then changed the pattern match from ‘_X.’ to just ‘_.’, and I was left with the context...

[a2billing-private]
exten => _.,1,SetCallerPres(prohib_not_screened)
exten => _.,n,Goto(a2billing,${EXTEN},1)
exten => _.,n,Hangup()

I’ll be doing more testing this morning, but this looks like it’s the job.

I have to put out a big 'Thank You!' to Joe Roper who was able to point me in the right direction to finding a solution.

Regards,

Max

Better to use my script so that calls to 911 and toll free numbers will display caller ID
In the US and Canada, many toll-free carriers block anonymous caller IDs