OBi200 keeps rebooting after upgraded to 8680EX

<< < (4/4)

jeffreydarnold:
I was able to verify my OBI200 did update to the latest firmware by logging into it directly, so it seems highly likely this isn't us, it's them.   Hopefully, their servers will come back online.   As many others have stated, I've never had an outage last as long as this before either and I've been using OBI for many years.

drgeoff:
The issue that prompted the creation of this topic has nothing to do with GV.

azrobert:
Quote from: glasgow on August 25, 2021, 08:24:31 am

If I understand correctly, the OutboundCallRoute changes is to route sp2 to tg1, so is the DigitMap.


I don’t understand what you’re saying.

Before my fix you had:
PrimaryLine set to TG1 and {(Mpli):pli}
Mpli points to the primary line DigitMap, ((Msp2)|(Msp1))
pli points to the primary line, TG1
If the dialed number matches a rule in sp2 or sp1 digitmap, the call is routed to tg1.

The bug appears when the primary line is set to TG1.

The circumvention is to set the primary line to sp2.
And to route the call to the trunk group: {(Msp2):tg1}
If the dialed number matches a rule in the sp2 digitmap, the call is routed to tg1.

The TG1 Digitmap is no longer used.

Taoman:
Quote from: azrobert on August 26, 2021, 09:28:59 am


The bug appears when the primary line is set to TG1.



Thanks for your help with this, azrobert. Worked as expected when Google Voice went down a couple days ago. Also nice to get a SIT tone when primary is down which I only knew about because of a post you made in the past.

But for whatever reason I can't get VGs to work in a TG. VGs work fine when using ** codes and worked fine with the old firmware. Any ideas?

azrobert:
Failover to a VG works for me. I defined tollfree.alcazarnetworks.com on a VG. I disabled my GV trunk and called 1-800-234-3993 and it connected using the VG. I had to use alcazarnetworks because the only SIP provider I have requires registration.

Does the call history show the call routed to the provider defined on the VG?

Sometimes the OBi config gets corrupted. Try using a different VG number.

Navigation

[0] Message Index

[*] Previous page