Questions - Google Voice on Obi, New to Obi202, not new to GoogleVoice or VoIP.
SteveInWA:
The only reason you've been able to make simultaneous calls is in support of call-waiting and three-way calling on inbound calls. It's not to support anyone making multiple calls at once from multiple devices.
You'll note that there is also no documentation anywhere that explains, supports or encourages multi-call scenarios.
There is no specific documentation on this. The consumer version of Google Voice has never been intended for any sort of business use, and Google can and does use a variety of triggers to enforce this policy. The business-class version of Google Voice for G Suite customers is the offering for other use cases.
PDX_Mark:
Quote
Google Voice is not a plain vanilla SIP trunk service. It is not intended for use with Asterisk, and it is only capable of making two simultaneous outbound calls. Attempting to use Google Voice as a SIP trunk provider for multiple calling violates Google's terms of use, and may result in your Google Voice service being suspended.
@SteveInWA , WOW! thats a lot of info about things I never asked about!
To reiterate, I asked in first question ONLY about the changing password. Absolutely nothing about the rest of it
In question 2 my question had NOTHING to do with the wiring of the obi jacks or pin-outs thereof.
I did type an error in question 3 but it should read "If I do not want to use the Obi202 phone port for Calls....." This has nothing to do with your "legal OPINION" of the Google TOS as nowhere does it say you are an attorney nor even an ermployee of Google. As someone else pointed out Google already allows several methods of simultaneous calls.
I appreciate your replies, but you may want to consider that your future replies need not be filled with irrelevant information.
SteveInWA:
Quote from: PDX_Mark on September 03, 2020, 05:11:05 pm
Quote
Google Voice is not a plain vanilla SIP trunk service. It is not intended for use with Asterisk, and it is only capable of making two simultaneous outbound calls. Attempting to use Google Voice as a SIP trunk provider for multiple calling violates Google's terms of use, and may result in your Google Voice service being suspended.
@SteveInWA , WOW! thats a lot of info about things I never asked about!
To reiterate, I asked in first question ONLY about the changing password. Absolutely nothing about the rest of it
In question 2 my question had NOTHING to do with the wiring of the obi jacks or pin-outs thereof.
I did type an error in question 3 but it should read "If I do not want to use the Obi202 phone port for Calls....." This has nothing to do with your "legal OPINION" of the Google TOS as nowhere does it say you are an attorney nor even an ermployee of Google. As someone else pointed out Google already allows several methods of simultaneous calls.
I appreciate your replies, but you may want to consider that your future replies need not be filled with irrelevant information.
I don't see any problem whatsoever with my replies. I answered what you originally asked; how can I possibly read your mind?
You asked about the password change scenario. I explained WHY it doesn't matter. Some people want to know why, not just a one word answer.
The reason I described the pin wiring of the OBi 202 jacks is that countless people over the years have misunderstood it, causing failures. Other posters and I have then had to explain it; I simply provided that information so you'd not fall into that trap.
As for the multiple call issue: I'm designated by Google at the highest-level of product experts on the Google Voice help community. I've been supporting the service for over a decade, and I have direct contacts at Google. I know exactly how the service works behind the scenes, and I am pointing out that a) it's Google's service, you have no legal contract nor entitlement to use it however you wish, and b) Google can and does kick people off of the service when, at its sole discretion, they don't use it as Google intends. It happens every week; just look through the official forum.
I'll make a note not to waste time replying to your posts going forward.
PDX_Mark:
@SteveInWA,
Man you are so full of yourself while tooting your own horn.
Google does not pay you, and more than probably the "experts" that designate you are also not Google employees. You may even be a self professed "expert" as I see no "Google Certification" nor the like cited. If you were in fact some SIP "expert" you would not be working for Google for free.
You seem to impy that my intention somehow is to abuse Google's service when in fact you have no idea what my usage is and in fact my usage is nothing more than residential , using the Obi202, an officially supported Google Voice device. I just need to know what happens if someone else goes to place a GV call when one is already in progress.
If Google has a problem with that they should take it up with Polycom that makes the officially endorsed Google Voice Obi products with the inteface to asterisk and other SIP devices possible.
I would actually appreciate it if you would refain from repying to me in the future, I have no need for your opinions and even question the accuracy of any relevant portons of your reply. So do not make that a threat, make it a promise please.
SteveInWA:
What a piece of work you are. First me, then attacking Taoman.
The actual title of your thread said "New to Obi202, not new to GoogleVoice or VoIP." It was a reasonable assumption that you here to augment your existing knowledge by learning about how OBiTALK devices work with Google Voice. I replied in the spirit of helping you with that.
For the record, your reply "I did type an error in question 3 but it should read "If I do not want to use the Obi202 phone port for Calls.." is an outright lie, since you followed up with a post about using Asterisk.
And by the way, you are very late to the party of outraged whiners regarding second-guessing the ToS and Asterisk. There was a 44 page (!!!) DSLReports forum discussion on this, which was finally put to rest by Alex Wiesen, head of Engineering for Google Voice, who clearly stated that it was a violation of the ToS. Nobody is interested in re-hashing that ugly shit-flinging mess:
https://www.dslreports.com/forum/r32016984-Asterisk-Google-Voice-SIP-testing-and-technical-discussion~start=1170
So: learn to have a civil, respectful discussion, or GTFO.
Navigation
[0] Message Index
[#] Next page
[*] Previous page