Firmware update for 20x series
ma678:
My three GV accounts show "Connecting to 64.9.240.172" every few minutes. May I change setting anywhere to keep alive interval longer?
Thanks.
SteveInWA:
Quote from: ma678 on May 12, 2018, 10:43:53 pm
My three GV accounts show "Connecting to 64.9.240.172" every few minutes. May I change setting anywhere to keep alive interval longer?
Thanks.
NO. Do NOT change the keep-alive interval. Google Voice will specifically block connections if the endpoint is sending rapid keep-alives. Leave it at the default. In fact, the error you describe can be caused by changing the keep-alive settings.
If you can't get your device to connect and stay connected, then delete it off of the OBiTALK portal, restore it to factory defaults, re-add it to the portal, and re-configure Google Voice. Do not make any "expert mode" changes to the Google Voice SPx settings.
RFC3261:
Quote from: SteveInWA on May 13, 2018, 12:06:26 am
Google Voice will specifically block connections if the endpoint is sending rapid keep-alives.
My recollection is that if one makes rapid changes via the portal (or power cycle the device repeatedly) one can also run into one/more rate limits (if not with GV, with some other providers), so one should have some patience after making the changes to let those limits expire and for the connections to complete. Rate limiting is considered a best practice, and some may need to learn the valuable new skill of patience.
chilirock:
Quote from: SteveInWA on May 12, 2018, 10:03:18 pm
Regarding Callcentric, check the DTMF method setting. It should be set to "Auto", which is the default setting when using the OBiTALK portal with its Callcentric configuration template.
But, that setting usually comes into play AFTER you connect to the called party, and you are saying that the friend can't even key in *123 to reach CC VM? That's sounds like a digit map problem. Can it call ANY number?
Hi Steve, Regarding "DTMF method", yes, it's set to "Auto". I know for sure that is not something I would have changed.
Regarding "Can it call ANY number?", yes, dialing other numbers and connecting to calls are working as normal, fine.
Regarding, "Sounds like digit map problem", that's what I suspected as well. It seems like the Obi is just not registering the number string that I dialed. It must not be matched to one of the dialing strings so it waits and eventually gives me a fast busy tone.
I am by no means a digit map guru, not even a digit map neophyte. I wouldn't know what to check or where. I know I didn't change the digit map. If you or someone else has a suggestion for what to check it would be appreciated.
ma678:
Does anyone know how GV's call forwarding works? I enabled unconditional forwarding on three GV accounts to sp1(my cellphone #). Sometime I can get calls forwarded, and sometimes not. Doesn't new GV sip support call forwarding?
Thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page