OBi200 keeps rebooting after upgraded to 8680EX
azrobert:
SP1 DigitMap: (1xxxxxxxxxx)
SP2 DigitMap: (1xxxxxxxxxx|<0:1>xxxxxxxxxx)
SP3 DigitMap: (1800xxxxxxxxxx)
Phone DigitMap: (0xxxxxxxxxx)
Trunk list: (sp3,sp1,sp2)
A number will only be routed to a trunk when it matches its DigitMap.
14805551212 will not be routed to SP3 because it doesn’t match its DigitMap. It will be routed to SP1. Upon failure it will be routed to SP2.
04805551212 will be routed to SP2 after leading 0 is replaced by 1. I call this “normal routing”, it’s not used for failover.
18005551212 will be routed to SP3. Again “normal routing”.
Edit: This is bad example of “normal routing” because the call will be routed to SP1 upon failure.
I have an OBi110 connected to a landline. I also have an OBi200 defined with a VG pointing to the OBi110. I route calls with a “9” prefix to the OBi110 and then to the landline. The VG is defined in my OBi200 trunk group.
glasgow:
It works for me without changing the DigitMap. I tested by making sp2 disabled, all calls were re-routed to sp1.
If I understand correctly, the OutboundCallRoute changes is to route sp2 to tg1, so is the DigitMap. I have sp2,sp1 in the tg1 trunk list and ((Msp2)|(Msp1)) in DigitMap, so when sp2 is down (I manually disabled it) it will route to sp1 that's the next one in TG, and both Msp2 and Msp1 will be used as the DigitMap so I don't have to change the DigitMap for Phone1 Port. Is this correct?
Quote from: azrobert on August 24, 2021, 07:53:13 pm
You can get Trunk Group1 working by using OBi Expert to make the following changes.
Physical Interfaces -> Phone1 Port -> PrimaryLine: SP2 Service
Physical Interfaces -> Phone1 Port -> OutboundCallRoute
The last rule is {(Mpli):pli}
Change it to {(Msp2):tg1}
If the above doesn’t work, add this change.
Physical Interfaces -> Phone1 Port -> DigitMap
The last rule is (Mpli)
Change it to (Msp2)
Please post back if these changes work or not.
frankpc:
Are you suggesting that the outage we are now experiencing with our oBi devices is due to the FW update and that we have to make the changes in setup described above to restore service?
glasgow:
Quote from: frankpc on August 25, 2021, 12:43:00 pm
Are you suggesting that the outage we are now experiencing with our oBi devices is due to the FW update and that we have to make the changes in setup described above to restore service?
I don't think so. I am having the same error message "Connect Failed" at this moment like many others.
frankpc:
Quote from: glasgow on August 25, 2021, 01:02:43 pm
I don't think so. I am having the same error message "Connect Failed" at this moment like many others.
I agree. thank you. I don't recall an outage lasting this long for the past 4 years since my Obi's went online.
Navigation
[0] Message Index
[#] Next page
[*] Previous page