How to send 0000000000 to Privacy Manager?
Submitted by carteepb on Tue, 07/22/2008 - 9:53am.
I've been getting calls from 0000000000 lately instead of unknown. I don't know if it's Vitelity or the end user that's changed the way they handle unknown calls. In any case, it is defeating my Privacy Manager. In searching the site, I see suggestions on setting up an inbound route to terminate calls from this number, but I receive legitimate calls that present like this, and I'd like to send them to Privacy Manager to allow the caller to input an identification rather than terminate the call.
Does anyone know how to send this number to Privacy Manager? What would be nice is an option under the inbound routes section to send any number to Privacy Manager, since I would suspect any number can be spoofed.
Thanks.
 
Me too
Wed, 08/06/2008 - 10:18am
If you figure this out let me know. I have a support call into Vitelity too because this is lousy.
There were buggy issues with Aastra phones and some SIP ATA's that if you sent them no caller id number at all, the device would freak out and not take the call. I wonder if this was Vitelity's short minded fix?
 
Has anyone figured this one
Tue, 10/21/2008 - 12:43pm
Has anyone figured this one out? I just received a call from a company that forces their CID to 9999999999. I'd like to dump them to privacy manager.
 
This is how Vitelity sends
Wed, 10/22/2008 - 8:41pm
This is how Vitelity sends the private calls unfortunately. A quick fix is to create an inbound route with the caller ID of 0000000000 and set the destination to an IVR or an announcement with a recording that says "we're sorry, private calls are not accepted by this number. Please call again without blocking your number"
 
anyone got a resolution for
Sat, 01/31/2009 - 12:24am
anyone got a resolution for this?
 
Not yet
Wed, 02/04/2009 - 5:35pm
I have been looking into this issue as well since we switched over to Vitelity.net this year. Based on what I've been reading in the asterisk.org website, the way the Privacy Manager works is by checking if the callerid is greater than or equal to 10 numbers. Since 0000000000 is 10 numbers it thinks it's a valid caller id and gets passed as a valid call.
I talked to Vitelity's tech support and was told that they can't do anything about that so we're going to have to figure this out on our own. I'm going to spend more time researching this and to find a work around so once I get something figured out I'll post it here.
This is a link to the actual source code to the privacy manager if you want to see what it looks like.
http://www.asterisk.org/doxygen/1.2/app__privacy_8c-source.html
Dean
Anaheim, CA
 
This is very doable.
Please
Thu, 02/05/2009 - 11:01am
This is very doable.
Please read what i wrote here: http://trixbox.org/forums/trixbox-forums/help/how-use-blacklist-f...
 
Problem Solved
Sat, 02/07/2009 - 10:11am
Hey everyone, I'm happy to report that I was able to resolve this problem with Vitelity. After working with their tech support via their Support Ticket system, I was able to convince them to change blocked calls so they say 'Unavailable' instead of '0000000000'. So now all my blocked calls are getting captured by the Privacy Manager.
I'm not sure if their change was system wide or just on my account so test it first. If it does not work then enter in a support ticket with Vitelity and tell them to change the caller id from '0000000000' to 'UNAVAILABLE'. If they give you flack then reference ticket #30682.
Thanks!
Dean
Anaheim, CA
 
Thanks
Tue, 03/17/2009 - 9:34am
Your Vitelity change was not system-wide. I was still getting 0000000000 for unknown numbers. I initiated a support ticket and referenced your ticket number. Initially, they said that they would have to move me to another incoming server. When I asked how we could coordinate this without downtime, they just changed my account on the same server. Now, privacy manager is working GREAT! Thanks for the help.
 
Member Since:
2006-06-01