Can't call out after new firmware pushed to 2 OBi 200s

<< < (4/6) > >>

RFC3261:
Quote from: restamp on July 03, 2018, 08:30:38 am

If someone else has a 202 loaded with 5897EX, could you check this and report?  I'd like to know whether this problem is particular to my OBi or one that affects all 202s.

My 202 seems to be working fine with the call status page (displays calls in progress, etc.).

One thought is to be sure to clear your browser cache and/or force a refresh without cached content (depending on browser).  Since the web page(s) have changed, the page/scripts may have changed sufficiently to cause issues [I have gotten caught on that for other manufacturers change in web interfaces at firmware update].

lrosenman:
I have 2 GV accounts on my OBI202, one in the WiFi beta (mine), one NOT in the WiFi beta (My Wife).

Mine works fine, my wife's seems to still be talking XMPP based on the OBI202 logs.

Quote

Jul  3 12:13:24 192.168.200.109  XMPP:Updating peer:218ott37o0la51syx8acnad1v8@public.talk.google.com[messaging-lcsw_hangouts_82CB35E0] to online

Ideas?

GV Calls do *NOT* reach the 202, and it does *NOT* show up in the portal, but the Obi says connected.

RFC3261:
Quote from: GPz1100 on July 03, 2018, 07:29:45 am

For those _not_ having issues with the new firmware, are you using only gv or other providers too?

All working for me with 5897EX.  I have tested with GV (the new SIP based variant of course), and a provider that I primarily use for e911 (which is a standard SIP setup).  Tested with both a POTS phone, and a (bridged) IP phone.  I will note none of the calls I tested with were to true landlines (AFAIK).

RFC3261:
Quote from: lrosenman on July 03, 2018, 10:26:17 am

Ideas?

I have to believe mixing and matching SIP based and XMPP GV accounts on the same OBi is not a well tested case.

Completely untested, and as likely as not it won't work, but my ideas would be to delete your Wife's GV account from the portal, wait for the various restarts, and then try to re-add it which *may* force the conversion to SIP on the OBi and GV side.  If that does not work, I would next try signing your Wife's account up for the WiFi Beta (and wait for that to happen) and repeat.  Last idea, delete both GV accounts, and than add your Wife's as the first GV account to get it SIP-ized.  Once there, you should be able to reset/restart and get things back to normal (your account on SP1, your Wife's on SP2).  Let us know if any of that happens to work (we can add it to the knowledge base of works, or does not work).

lrosenman:
Quote from: RFC3261 on July 03, 2018, 12:01:10 pm

Quote from: lrosenman on July 03, 2018, 10:26:17 am

Ideas?

delete your Wife's GV account from the portal, wait for the various restarts, and then try to re-add it which *may* force the conversion to SIP on the OBi and GV side.

That didn't work

I've sent the form for her account on the WiFi beta, but I had to "edit" my response from my account to hers.

We'll see.

I may try the 3rd option here in a bit.

Thanks for the ideas.

What's interesting is outbound calling works, but inbound does NOT.

Navigation

[0] Message Index

[#] Next page

[*] Previous page