How to show my Google Voice number as caller ID when forwarding only to the OBi
Taoman:
Don't know what to tell you. Works fine for me on multiple numbers and OBi ATAs. The fact your OBi won't even ring indicates invalid syntax but I can't see the problem. Only thing I can think of is I'm running older firmware (3.2.2 (Build: 5859EX)) but it seems unlikely that would be the problem.
Maybe azrobert might have an idea why it isn't working for you or have a better idea how to do what you want?
Taoman:
Quote from: LTN1 on April 01, 2020, 09:13:56 pm
I have daughters that share the same handset connected to the OBi and want to differentiate the incoming call.
As far as this issue goes, have you tried using distinctive ring patterns for the different numbers?
LTN1:
Quote from: Taoman on April 02, 2020, 08:59:30 am
Quote from: LTN1 on April 01, 2020, 09:13:56 pm
I have daughters that share the same handset connected to the OBi and want to differentiate the incoming call.
As far as this issue goes, have you tried using distinctive ring patterns for the different numbers?
That's a good suggestion but many young people these days are more visual and I suspect that it may be a challenge for them to remember how to differentiate the different ring patterns. But it is worth a try, however, a future caller ID solution would be preferable.
SteveInWA:
Out of curiosity, I tried it, and it doesn't work with my OBi 202. I substituted *GVNUMBER* with either 12061234567 or 2061234567. The phone didn't ring, although my GV VoIP clients did.
Maybe it's a firmware thing. I am running the current firmware 5921EX.
azrobert:
You have a couple things wrong with the rule you're using. First GV send an 11 digit callerid with a "+" prefix, so you won't get a match (xx. will not match a "+"). Second you are prefixing the callerid with 10 digits plus 2 stars, so you will end up with a 24 character callerid. Try the following rule:
{(<+1xxxxxxxxxx:9163595555>):ph}
Navigation
[0] Message Index
[#] Next page
[*] Previous page