**5 setup failing (no call route)
SteveInWA:
Thanks for the updates. Yes, that's why I asked about whether or not it was a 302 vs. 202, and where you obtained it. The 302s are meant to be used by managed service providers, and so your unit was probably configured to use that other service provider. I don't know if Obihai will be able to remove that or not. Good luck.
darthMuzo:
Final status:
Obihai support resolved the final issue, and I am now able to administer the 302 via the webpage. Today, I got it going with the two VSPs I wanted, and this guide was pure gold for short-cutting me on the setup and dial-plans:
http://www.obihai.com/docs/OBi-VoIP-Device-Australian-Localisation-Workbook-v1-1.pdf
I do like the level of indirection with the dial-plans (naming short pieces of digit maps and then being able to refer to the names in higher-level config strings). It's a bit less oblique than the SPA3102 this replaced.
SteveInWA:
Good news! Thanks for closing the loop with this on your successful outcome.
NoelB:
Quote from: darthMuzo on February 06, 2016, 01:41:43 am
Thanks for the reply, Steve.
Purchased new from http://www.warcom.com.au/
As far as I can tell, it's a real 302. On the sticker on the bottom; on the admin status page - identifies as an OBi302, h/w version 1.4.
This is strange because I just rang warcom and they only stock the 110 and the 202 and I have never seen a 302 listed on their website. Distributors of billion and fritzbox have changed recently but not obi. It sounds like it may be returned stock from a voice service provider previously provisioned so I would ask warcom where it came from and about warranty. It may be worth requesting replacement with a 202.
Konos:
darthMuzo. Could you please elaborate on this?
How was resolution achieved?
Quote
Obihai support resolved the final issue, and I am now able to administer the 302 via the webpage.
cheers
Navigation
[0] Message Index
[*] Previous page