OBI110 and Simonics GV trouble - Unauthorized
SteveInWA:
It is impossible for Google Voice to send a different phone number than the one from which you are calling.
If you have a Google Voice inbound telephone number, then Google Voice will use that number as your caller ID.
If you have no Google Voice inbound telephone number, then Google Voice will not send any caller ID number at all. The caller will see "UNKNOWN CALLER" or "PRIVATE CALLER" or a similar message instead.
The only way that a WA number could be sent as the caller ID, AND you are using Simonics GVGW, is if you entered the wrong number on the GVGW web site.
billsimon:
Quote from: SteveInWA on November 13, 2017, 04:10:45 pm
It is impossible for Google Voice to send a different phone number than the one from which you are calling.
...
The only way that a WA number could be sent as the caller ID, AND you are using Simonics GVGW, is if you entered the wrong number on the GVGW web site.
Actually the part that matters is the Google account used to sign up. Tim, if you're getting different behavior now than when you were using the Obi, it is probably because you signed up for the GVGW using a different account than you had applied on your Obi.
SteveInWA:
Quote from: billsimon on November 13, 2017, 04:38:24 pm
Quote from: SteveInWA on November 13, 2017, 04:10:45 pm
It is impossible for Google Voice to send a different phone number than the one from which you are calling.
...
The only way that a WA number could be sent as the caller ID, AND you are using Simonics GVGW, is if you entered the wrong number on the GVGW web site.
Actually the part that matters is the Google account used to sign up. Tim, if you're getting different behavior now than when you were using the Obi, it is probably because you signed up for the GVGW using a different account than you had applied on your Obi.
Thanks, Bill. I should have also mentioned that. This is turning into a fuster cluck. I spend too much time on the Google Voice help forum explaining to people why they can't find their number, and it's always because they are looking at the wrong account. If only people would read what's on the screen.
azrobert:
Quote from: TimAtHome on November 13, 2017, 04:01:20 pm
What are the rules (Mipd) and [^*#]@@. for, anyway? They were part of the default after I reset the machine.
(Mipd) points to User Defined Digit Map1
ipd:
Code:
(xx.<*:@>xx?x?<*:.>xx?x?<*:.>xx?x?<*:.>xx?x?|xx.<*:@>xx?x?<*:.>xx?x?<*:.>xx?x?<*:.>xx?x?<*::>xx?x?x?x?)
This digit map will convert character string "0*192*168*1*100*5060" to "0@192.168.1.100:5060".
I think rule "[^*#]@@." is meant to match a URi like "tim@company.com".
azrobert:
Quote from: azrobert on November 13, 2017, 06:16:10 pm
I think rule "[^*#]@@." is meant to match a URi like "tim@company.com".
I think I'm wrong about rule "[^*#]@@.". This rule will match any character string that doesn't begin with "*" or "#" and will match an IP address after conversion by (Mipd). The [^*#] will prevent the rule from matching a Star Code or "##". "##" is used to get dial tone on a PSTN line.
Navigation
[0] Message Index
[#] Next page
[*] Previous page