OBiTALK Community

I have and Obi202 being used with GV

The problem is, it rings the Obi Phone for say, a certain number of rings (the precise number of rings is irrelevant to the question at hand).

The question is NOT about the precise "number" of rings, but rather the key question is "how to increase the delay" TIME (to keep the Obi ringing locally, before GV goes to VM, (whatever that time amount may be but we want to INCREASE it somehow...)

Often, when your Obi phone rings, you can't get to the phone quickly enough, and by the time you get to it, GV has already transferred your incoming call to Voicemail.

I am aware that GV has not provided any way to specify the "NUMBER OF RINGS" before going to voicemail.

GV has also not provided any way to increase the TIME ("number of seconds") before an incoming call will go to Voice Mail.

What is needed is a HACK!

Since GV does not allow us the FLEXIBILITY to delay Voice Mail answering, we must figure out a way to OUTSMART GV, and delay it by some HACK.

Does anyone  know of any "tricks" that can be used to cause GV to be slowed down so that it can't jump to Voice Mail so quickly?

Perhaps if GV is told to ring a "few numbers" (unneeded numbers, as a HACK) instead of just one needed number, perhaps that can "keep em busy" so they can't go to Voice Mail so quickly?

There must be some tricks that can be used to "tie up" GV resources so that it's gets "slowed down" artificially, and thereby will delay .... and keep ringing the Obi phone LONGER, before quitting to Voice Mail.

We are not talking "theory here" but looking for anyone who has successfully experimented with successful results to increase the DELAY of the amount of time before GV goes to Voice Mail.

Anyone?

You haven't said why you can't get to the phone.

This is why people get multiple handset cordless phones: carry one with you.

The Obi will handle a couple of regular wired extensions also.

I don't believe any tried method exists to do what you want.  The platform Google uses it very robust so tying up enough resources just isn't possible.  Your best bet would be using another service altogether.


If you don't want my "theory" don't bother reading any further but I am confident this would work. 
No longer theory as I have tested this. 
If you insist on using Google Voice you could set up your Obi or another service to actually answer the call immediately and then forward the call to your phone.  The call would then need to be manually sent to voicemail or an answering machine could be used.  

I am tinkering with the solution right now.  It must actually answer the call and not just forward it.


Edit:
It seems a little more then I can accomplish with just the Obi unless you want to route the call to the AA and make the caller press 1 to ring your phones.  That will bypass Google Voicemail altogether.  It can be done on other systems that give you more control like a PBX.  I made this work on voxeo for an infinite ring.  All I did was have Voxeo pick the call up place a new call to my OBi and bridge the two calls.  I won't be testing this with anything else right now.

Any hack that extends the rings will also at least partly disable simultaneous ringing. 

I have been trying to avoid replying to this thread since the op said he didn't want theory and only looking for answers from people with successful story....

But since the silence has been broken I figure I'll add to the thread by asking some questions. Hopefully this may lead to some actual success story....

If AA is configured to answer the call, is there a way to bypass the menu and have it ring the phone directly? This would have solved op's issue.

Could service like PBXes be configured to answer the call then ring the callee's phone?

Normally AA only answers if the caller's caller ID is listed as a "trusted caller". So an incoming call from most people would ring the local phone for 25 seconds. I only have my cellphone as a "trusted caller".

What I do is to have my local answer machine pick up a little before the call would have gone to voicemail. If I were a little slower than 25 seconds in  picking up the phone, I would still get the caller because the answer machine has caused the call to be answered.

 This may not be what you want but it fits my needs. I don't have to deal with two voicemails that way. I understand there are downsides.

This might work. Note, I haven't tested this. It will be a revelation if it works! I suspect that GV might think the call is answered.

Using an Obi202
CallForwardOnNoAnswerEnable
CallForwardOnNoAnswerNumber {ph2} (Send it to ph2)
CallForwardOnNoAnswerRingCount = 3 (before GV VM picksup)

Let us know if it works.

I tried this on the OBi directly and it did not work.  VG1 was a gateway I configured and for obi@obi.sip.address I used a sip address I actually configured to ring my OBi.  Google Voice still eventually went to voicemail.  Perhaps it might inspire someone else with a local OBi solution.

{VG1(obi@obi.sip.address)}

If you want to send everything to AA then this should do it.  Callers will need to press 1 to continue the call.  The aa should be secured with a good password.  Even then I wouldn't consider it safe.
{aa}


As I posted earlier I did make infinite rings work by putting Voxeo in the middle of the system.  


The answering machine sounds like the best solution to me.  I guess you could even replace the outgoing message with a recoding of ringing for another 15 seconds so the caller didn't know the machine picked up yet.

A few "Hacks" you can do with the AA, including ringing the phone port.
Re: obi110 auto attendent - default option
https://www.obitalk.com/forum/index.php?topic=3783.msg25164#msg25164

It seems that it works. Have a look at this thread for details of the correct syntax to use.
Re: CallForwardOnBusyEnable Broken Obi202 - Solved (Firmware Bug)
http://www.obitalk.com/forum/index.php?topic=5842.msg37433#msg37433