Now I have to agree with DrGeoff, that you really do not understand Google Voice, and it's design, at all.
(My response to your comments will be in bold text.)
Thank you for that.
As long as it works the way I want it to I'm satisfied. If I wanted to understand it's internal electrical design I would have bought two of them and reversed engineered one of them.
For the umpteenth time, it is not a bare bones ITSP. It is not a basic SIP VoIP trunk provider. It is a complete telephone call management, voicemail, and text messaging service. It is intended that you use its voicemail, not your answering machine.
Steve, it is very difficult for the manufacture of various products to force people to use their product exactly the way the CEO, Engineering & Sales Departments thinks they should.
i.e. Again, I don't need all that stuff. I just need a phone that will receive and make calls. And I clearly stated that in the beginning of this thread.
Since I don't use a cell phone or tablet etc either; when I want to check if I had any calls I don't have to turn my computer on to see if sales people left me a "click" or a sales pitch. I just look at the number of messages on the answering machine (zero in most cases) and if necessary, push one button and I hear the message. For the way I use a phone that simplifies things greatly.
If this is more complex than you wish, and you wish it would work like your PAP2T did a decade ago, then get service from a bare-bones SIP ITSP. Heck, Circlenet Sam would love to have your business at an extremely low cost.
Yes it IS more complex than I wish. And my phone system using OBiTalk, the OBi202 and my answering machine *IS* working like it did with the PAP2T.
Steve: don't take it so personally. It's not a failure of OBiTalk to allow me to use it the way I want to.
And, comparing an OBi 20x to an ancient PAP2T in terms of sound quality or performance is ridiculous.
Does finding out that the sound quality of both units is the same really cause that much grief on this forum? And it's not ridiculous if it -is- true in my case.
It would be like comparing a 1957 Chevy Impala to a 2018 Chevy Volt. The PAP2T was a very basic device with a low-performance, simple microcontroller.
My first car was a Model T Ford. The car and I were both young at the time. ;-)
As basic as the '57 Cheby, T and the PAP2T seem now, they all served their intended purposes. And still can.
On the other hand, many people drive cars all their lives and don't have any idea how they work. Not everyone has to fully understand how electronics or mechanical things work to get them to do what they need them to do.
The OBi products are Linux computers, running on an ARM SOC. All you were asking the PAP2T to do was the bare-bones registration and SIP VoIP stuff. And of course the OBi is going to run cooler because again, the guts are about 15 years older in the PAP2T, compared to modern, low-power electronics.
Please, I started designing electrical circuits most likely before you were born. It was just a casual observation and not meant to cause umbrage concerning the wonderfully modern (cooler running but with a short power cable) OBi202.
I'll let someone else give you a tutorial on digit maps, which are roughly comparable in purpose, but not in syntax, to PAP dial plans
And I can return the favor if you need to know more about the internal workings of a Model T Ford. Or my present 13 yr old Honda that can get almost twice the driving range of the Chevy Volt at 64 mph. Even my 30 year old Honda CRX-HF got more mpg than the Volt.
And now, getting back to the OBi202:
I found a 3 year old forum post how the poster changed the ring delay of incoming calls, I'll try that.
Come on Steve, lighten up.