| Not getting ANI from incoming toll-free redirected calls Well, VT seems to be getting worse and worse for me. I have several different toll-free #s which I point at my VT#. I do this, in part, to get the ANI from the calling party even if they have "caller-id" turned off.
See ANI: »en.wikipedia.org/wiki/Automatic_···fication
Now incoming calls from my toll-free#s are being handled *and* reported as "anonymous" - which is wrong! Some go to VM, some get other strange results - none ring thru. So, I've now redirected those calls to my backup VOIP service instead. I may be close to done with VT.
Why can't VT get any of this technical stuff right anymore?
- Don |
|
 RockyBBPremium
join:2005-01-31
Steamboat Springs, CO
1 edit | said by deliberate: Why can't VT get any of this technical stuff right anymore? Technically, VT is right. When a call goes out from the originating party, several data fields identify the origination number, including billing telephone number, caller ID number, and ANI. When a subscriber asks to block outgoing caller ID for their own security purposes, they expect that the caller ID number will not display in caller ID units of people that they call. By not showing you the caller ID info, VT is getting it right ... in the past by showing you the ANI info they would have been getting it wrong. What you expect they should not have been doing ... you've had a free ride on that one. Likely, whatever providers are now passing the ANI info as caller ID will one day stop after someone expecting anonymity complains to regulators. |
|
robket
join:2007-12-29
Waunakee, WI | reply to deliberate
Typically in my call logs I will see the phone number of an anonymous party, but I noticed today that new anonymous calls show "restricted" for the phone number. This is one thing that I really liked about Viatalk was that I could check and see the phone number of a private call. |
|
Reviews:
 ·RoadRunner Cable
 ·ViaTalk
| reply to deliberate
I liked being able to see who called also when the blocked it. 
Could this be a side effect of the new setup. Calls now get handed off instead of passing thru VT servers. To bad if so fixed a bug I liked. |
|
| reply to RockyBB
I thought if you had a toll-free number, you were allowed to see the caller info even if they blocked it? |
|
RockyBBPremium
join:2005-01-31
Steamboat Springs, CO | said by druber:I thought if you had a toll-free number, you were allowed to see the caller info even if they blocked it? No, that's what "blocked" means. |
|
 burrisPremium
join:2000-08-22
Miami, FL
·VOIPo
| said by RockyBB:said by druber:I thought if you had a toll-free number, you were allowed to see the caller info even if they blocked it? No, that's what "blocked" means. From my day, all calls to 800 type numbers had to pass CID...
Has this changed??
»www.ucalgary.ca/it/telephone/callerid/faq
If I activate Selective Call ID Blocking and call an 800, 888, or 877 toll-free number, will my number be blocked?
No, it's a requirement that your telephone number cannot be blocked when calling toll-free numbers. |
|
| reply to RockyBB
said by RockyBB:said by druber:I thought if you had a toll-free number, you were allowed to see the caller info even if they blocked it? No, that's what "blocked" means. Rocky, you're totally and completely wrong.
1) Calls to toll-free #s do not block the ANI. This is because the called party is paying for the call, this is the way it has always worked. If you think that your caller-id selection turns off your# when you call a toll-free number you are seriously mistaken; and,
2) It has, in fact, worked properly thru VT, up until just recently.
Nice obfuscation attempt though,
Cheers,
- Don |
|
RockyBBPremium
join:2005-01-31
Steamboat Springs, CO
1 edit | oops. I am wrong. that doesn't happen every day! see page 2 of »www.qwest.com/residential/pdf/us···king.pdf |
|
| So that puts this back on VT then? Or... |
|
3 edits | reply to deliberate
I'm curious as to how VT is supposed to handle that type of call though, as you are forwarding calls made to your toll-free number to your non-toll-free VT number? |
|
| my take: since the number being called is toll-free, the CID block should be ignored, regardless of how many numbers the call ends up being forwarded thru... |
|
| reply to deliberate
"Nice obfuscation attempt though,"
now, why was *that* necessary? you can't just give him the benefit of the doubt that he made a mistake? |
|
 ptrowskiGot Helix?Premium
join:2005-03-14
Putnam, CT
kudos:4 | reply to burris
Welcome back Burris! You love us too much to stay away, huh?  |
|
RockyBBPremium
join:2005-01-31
Steamboat Springs, CO | reply to druber
said by druber:"Nice obfuscation attempt though," now, why was *that* necessary? you can't just give him the benefit of the doubt that he made a mistake? In his defense, he said that prior to me discovering my error. Thanks for sticking up for me, though. As a practicing husband, I come face to face with my list of faults everyday. |
|
 VTBrendanViatalkPremium,VIP
join:2005-06-27
Clifton Park, NY
kudos:1 | Hi,
The number you are calling (forwarding a call to one of our numbers is no different than calling it) is not toll free, correct?
-Brendan |
|
1 edit | said by VTBrendan:The number you are calling (forwarding a call to one of our numbers is no different than calling it) is not toll free, correct? Brendan: Thanks for noticing the post. I don't understand your question, so I'll attempt to restate the problem:
In almost all cases, I instruct people (friends/family/clients/others) to call one of my several toll-free#s, I do not ever use/publish/giveaway/register my underlying VT DID# (or other VOIP/etc #s that I also use) for "call me at ... " #s.
For example, I have an 866-xxx-xxxx toll-free # (this one is with Kall8) that I map to my VT # 702-xxx-xxxx.
Kall8 delivers the ANI as it should, as it has alway done so, to BroadVoice, SunRocket and now VT (etc). VT used to (properly) report that ANI as the caller-id and all was as it should be (as I pay for that incoming call).
Unfortunately, way back when, BroadVoice ran into a situation where some of their underlying services would not properly handle that hand-off at the DID level, and after getting to know and work with the BV CTO it turned out that BV just couldn't control those incoming telco services which it relied upon to handle my incoming BV#. That was a major part of my leaving BV (and that my friend the CTO got fired). Now VT seemingly having the same problem.
Worked fine using SR, but of course SR failed on other issues thru time and I bailed out from them after my prepaid two years and signed up for two years with VT.
Recently (I'm in my second year with VT), incoming calls to my 866-xxx-xxxx# (as above) have now been showing up as anonymous and getting delivered directly to VT voicemail as "restricted". It used to work correctly, now it doesn't. This is not acceptable. I have not changed anything at my end.
One reason I continue to be extremely happy with my toll-free#s is that I can easily/quickly move the mapped# to/from different underlying services (such as VT) and therefore have some modicum of control. I don't have to worry about moving my Voip/cellphone/landline DID#S, just remap. I currently remapped all my toll-free#s away from VT, at least for the moment. That means all my incoming are now coming in (properly) on my backup VOIP provider ...
I am no longer happy with VT. Please do what you can to change that.
Thanks,
- Don |
|
| reply to deliberate
I just signed up for kall8, and will soon be testing the crappy looking tollfreefreedom.com as well.
As for my primary tests, it seems to go well. *67 transfers go fine for me. I'm near the Sacramento area. Have you called Kall8? I've had experiences in the past where a provider changed a switch/routing server and completely broke ANI.
Wish the best for you. |
|
WA 425
join:2006-08-19
Lynnwood, WA | reply to deliberate
If it makes you feel better, I'm not getting ANI either. |
|
