Backing off...............again
Lavarock7:
Quote from: Judgeless on November 04, 2017, 03:34:22 pm
I did get it working used the DNS address 8.26.56.26
I know this is a short term fix. I am sure it directs to an old google server.
It sounds like the issue is an updated certificate. It is BS that ObiTalk will not upgrade the firmware to fix this with the new certificate. It is not like they have to change code.
This seems like a bad business model forcing people to buy new hardware every few years.
I'm not sure why you think this is Obi's fault. They had nothing to do with it and their decision to stop updating 100's was made quite a while back.
You can call it a bad decision, but then have to go back to companies like Microsoft who have end-of-life products. Plead with MS to patch Win95 and see what happens.
Yes, you can say they Obi SHOULD fix it, but perhaps they have dumped the code, since they no longer support it. Ford stops making parts, Chevy stops making parts, companies stop updating software. HP stopped supporting MPE (their proprietary mainframe software) and there in nobody left to make changes.
When I worked in the industry, we used the term NOT SUPPORTED to mean, it may still work, but we cannot/willnot spend any time fixing it.
Obi110s are not supported by Obi anymore. There has been a workaround here I think involving using a 3rd party connection.
SteveInWA:
Quote from: Lavarock7 on November 04, 2017, 03:55:12 pm
Quote from: Judgeless on November 04, 2017, 03:34:22 pm
I did get it working used the DNS address 8.26.56.26
I know this is a short term fix. I am sure it directs to an old google server.
It sounds like the issue is an updated certificate. It is BS that ObiTalk will not upgrade the firmware to fix this with the new certificate. It is not like they have to change code.
This seems like a bad business model forcing people to buy new hardware every few years.
I'm not sure why you think this is Obi's fault. They had nothing to do with it and their decision to stop updating 100's was made quite a while back.
You can call it a bad decision, but then have to go back to companies like Microsoft who have end-of-life products. Plead with MS to patch Winm95 and see what happens.
Yes, you can say they Obi SHOULD fix it, but perhaps they have dumped the code, since they no longer support it. Ford stops making parts, Chevy stops making parts, companies stop updating software. HP stopped supporting MPE (their proprietary mainframe software) and there in nobody left to make changes.
When I worked in the industry, we used the term NOT SUPPORTED to mean, it may still work, but we cannot/willnot spend any time fixing it.
Obi110s are not supported by Obi anymore. There has been a workaround here I think involving using a 3rd party connection.
+1, and it's pretty amusing for someone who's forum nickname is "Judgeless" to be judging Obihai on this.
spencer:
Quote from: Taoman on November 04, 2017, 01:43:55 pm
Quote from: Judgeless on November 04, 2017, 01:28:50 pm
I own 5 Obi110's.
Bummer. For $30 you can get all 5 back up and running with Google Voice. Plus you get incoming CNAM (Caller ID name).
https://simonics.com/services/
I signed up yesterday and everything seems to be working good. Since they don't give you step by step instructions, it did take me a little while to find old posts on how to configure the obi. So I'm hopeful this $6 will fix the problem, otherwise I'll have to get the 200 model for $50.
The 40 dollar 100 model worked great for the past 5 years with only a few outages.
drgeoff:
Simonics does not give you step by step instructions for configuring an OBi because their gateway can be used with any SIP ATA. The signup process gives you the 3 necessary bits of info - SIP login, SIP password and server. You then use those with the Generic Service Provider template on the Dashboard. (Or pop them into the appropriate places if you configure your device via the local web interface.)
bsdaiwa:
I setup Simonics on my 200, maybe this will help others...
Quote from: bsdaiwa on October 30, 2017, 01:16:17 pm
First thanks azrober, I will keep your suggestion in mind if Simonics doesn't work out.
Here is what I setup, if someone sees I need to do something different please let me know.
OBi 200 SP3: Generic Service Provider
Service Provider Proxy Server: gvgw.simonics.com
Service Provider Proxy Server Port: 5060
Outbound Proxy Server: gvgw.simonics.com
Outbound Proxy Server Port: 5060
Username: GVxxxxxxxxxxx
Password: (generated by Simonics)
URI: (left blank)
In addition I followed these instructions:
This post describes how to set up your Obi to take advantage of GVGW server redundancy.Thanks to user CarlM for this write-up!
The starting point for these instructions is GVGW already configured under Service Providers->ITSP Profile X and working.
Obihai Config Instructions
Under Service Providers->ITSP Profile X->SIP:
1. Set all four of the following parameters to gvgw.simonics.com :
ProxyServer (this should have been set already)
RegistrarServer
UserAgentDomain
OutboundProxy
2. Enable X_ProxyServerRedundancy
3. Enable X_DnsSrvAutoPrefix
4. Submit the changes
5. Reboot your Obi
That's it!
Note:
It is neither necessary nor desirable to enable X_SecondaryRegistration. In the case of GVGW, registering with one server registers you with all servers.
Just so it's clear I have an OBiLine attached to the OBi200 that handles the local PSTN line and that is the default line when the receiver is lifted. SP1 has the CallCentric account, SP2 has my wifes GV account and SP3 has my GV account. As of now I have just setup SP3 using Simonics to see how that works, if it does I will setup my wifes account on Simonics.
Anyone see any problems?
Navigation
[0] Message Index
[#] Next page
[*] Previous page