obi302 can't provision with obitalk. Install is tomorrow!
SteveInWA:
Right: use official firmware. OBiTALK registers the device via its OBi number and MAC address.
Here's how it works:
If you can register the device with OBiTALK, then the device was not previously registered to some other user, who didn't delete it off of their OBiTALK portal, OR it was not previously registered to a carrier and locked to that carrier.
If you get the error message shown in red in your earlier post, then it can't be registered by you to the OBiTALK portal, for the reasons I posed above. It doesn't matter what you do to reset the device.
If you don't need to use the OBiTALK portal, then you may be able to configure it locally, via the device's built in web server, at its assigned IP address.
Betta:
This is important; there seems to be misunderstanding that Service Provider devices are somehow "crippled/locked" and are "bricks". That is not true. They are exact same devices that are refused registration on ObiTalk based on MAC or S/N. If you copy config from a working device, they might even do google talk as google doesn't care for MAC or S/N (i.e. to exclude from service).
Quote from: SteveInWA on April 22, 2018, 09:48:48 pm
If you don't need to use the OBiTALK portal, then you may be able to configure it locally, via the device's built in web server, at its assigned IP address.
Mango:
If yours does happen to be locked, the third-party firmware from http://www.obifirmware.com/ has an unlocking tool. You need to SSH into the device and run clear_zt_params.
Navigation
[0] Message Index
[*] Previous page