OBI110 and Simonics GV trouble - Unauthorized
SteveInWA:
Quote
It's what my called parties see, and there is a change. Instead of my name and number, it has a number from Washington state.
Google Voice has never sent CNAM. Your called parties will either see the generic city name, or they will see whatever they have in their own phone's address book/contacts list, via that phone matching the number with their own list.
In some rare cases, and only for numbers that have been ported in from a landline telco, if that telco had submitted your name into the LIDB, it could have been left there for some period of time, and eventually purged.
If you absolutely require that your name be sent, then consider not using Google Voice. Some SIP service providers do feed their customers' names to the LIDB, with the customer's permission. Callcentric is one example.
Just keep in mind: CNAM is becoming less and less useful in general, as more people abandon their land lines, or use VoIP ITSPs that don't support CNAM.
TimAtHome:
Quote from: azrobert on November 13, 2017, 02:49:53 pm
Quote
(1xxxxxxxxxx|<1312>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
You are adding 1312 to a 10 digit number, not 7.
The last 2 rules are not needed.
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1312>[2-9]xxxxxx|011xx.|xx.)
Thanks so much, azrobert!
You know what's strange? <1312>[2-9]xxxxxx still does not work. But if I use <1312>xxxxxxx instead, that works.
What are the rules (Mipd) and [^*#]@@. for, anyway? They were part of the default after I reset the machine.
mo832:
Quote from: SteveInWA on November 13, 2017, 02:57:45 pm
Quote
It's what my called parties see, and there is a change. Instead of my name and number, it has a number from Washington state.
Google Voice has never sent CNAM. Your called parties will either see the generic city name, or they will see whatever they have in their own phone's address book/contacts list, via that phone matching the number with their own list.
I thought I might chime in here, because the way I read TimAtHome's post, it looks like Steve mistook what Tim is describing. I read it as Tim is **NOT** in Washington State, and the CID NUMBER (not name) displays some random number that does not belong to Tim and decodes to WA, where Tim is not located. He seems to be asking why the GVGW is assigning to Tim the wrong phone number that makes his called parties not recognize it.
I don't know if GVGW is the cause of this erroneous number display, but I'll step back and let you guys comment on this issue, and just read the discussion.
And if I'm wrong about what Tim meant, I'm sure he will correct that as well ;)
TimAtHome:
Quote from: SteveInWA on November 13, 2017, 02:57:45 pm
Quote
It's what my called parties see, and there is a change. Instead of my name and number, it has a number from Washington state.
Google Voice has never sent CNAM. Your called parties will either see the generic city name, or they will see whatever they have in their own phone's address book/contacts list, via that phone matching the number with their own list.
In some rare cases, and only for numbers that have been ported in from a landline telco, if that telco had submitted your name into the LIDB, it could have been left there for some period of time, and eventually purged.
If you absolutely require that your name be sent, then consider not using Google Voice. Some SIP service providers do feed their customers' names to the LIDB, with the customer's permission. Callcentric is one example.
Just keep in mind: CNAM is becoming less and less useful in general, as more people abandon their land lines, or use VoIP ITSPs that don't support CNAM.
CNAM wasn't my big concern, I was just wondering why a completely different number showed up. I tested it with someone who had my number in her contacts, and when I called it didn't display my number and the name she had in her contacts; instead, it had a number we'd never seen before from WA. Giving a different, new number for my calls is pretty much a deal killer. But ... I tried to think what you would advise and the thought occurred to power down, reboot everything, and try again. It's working as normal now. I don't know what that other number was all about, but if it's fixed I'm ready to move on...
TimAtHome:
Quote from: mo832 on November 13, 2017, 04:02:51 pm
Quote from: SteveInWA on November 13, 2017, 02:57:45 pm
Quote
It's what my called parties see, and there is a change. Instead of my name and number, it has a number from Washington state.
Google Voice has never sent CNAM. Your called parties will either see the generic city name, or they will see whatever they have in their own phone's address book/contacts list, via that phone matching the number with their own list.
I thought I might chime in here, because the way I read TimAtHome's post, it looks like Steve mistook what Tim is describing. I read it as Tim is **NOT** in Washington State, and the CID NUMBER (not name) displays some random number that does not belong to Tim and decodes to WA, where Tim is not located. He seems to be asking why the GVGW is assigning to Tim the wrong phone number that makes his called parties not recognize it.
I don't know if GVGW is the cause of this erroneous number display, but I'll step back and let you guys comment on this issue, and just read the discussion.
And if I'm wrong about what Tim meant, I'm sure he will correct that as well ;)
mo, you're absolutely right. That's what happened. It was strange and disturbing and definitely a deal-killer.
Fortunately after a reboot it's working as it used to, so the deal is on!
Navigation
[0] Message Index
[#] Next page
[*] Previous page