this post was submitted on 28 Nov 2023
1 points (100.0% liked)

VoIP

1 readers
1 users here now

Rules

founded 11 months ago
MODERATORS
 

Hello,

I have a client that is interested in leaving Ooma, and would like to keep using their Ooma Branded (and firmware'd) phones with other providers. The bottom of the device shows that it's a Grandstream device, and that Ooma is the 'importer'.

I've been able to gain access to the administrative WebGUI for one of them, and I can even get it to download configuration from my switch! The phone will not register however. It seems that it's running a custom firmware that Ooma puts on this device and some of that isn't/can't be programmed by my switch. I suspect I might be able to manually provision each phone (and each button on each phone), but that sounds not-great at best.

When I try to upload the current Grandstream firmware via the web interface to this phone, I get a Firmware Provision Failed message on the phone.

Entering in the firmware.grandstream.com address (and HTTP) also doesn't seem to affect it. Has anyone been able to flash standard GS firmware on these phones? I called Ooma, and their overseas support said that "these phones should only be used with Ooma service".

Has anyone accomplished a firmware reflash with the stock firmware?

you are viewing a single comment's thread
view the rest of the comments
[–] johnvoipcom@alien.top 1 points 9 months ago (1 children)

I dont believe it's possible, not only will you have custom firmware you also have what is called GAPS which is the grandstream provisioning server the phones automatically reach out to each time it's rebooted.

Best bet would be to tell them get new phones

[–] packetdoge@alien.top 1 points 9 months ago

Thanks for that. I'm not sure if Ooma's custom firmware uses GAPS. That was one of the things I wanted to test. I can enter the MAC there, and if it's on GS firmware I think it will pull our provisioning configuration URL. Either way, if I'm on the GS firmware I can program this phone, it just looks like there's challenges with the programming/config not being 1 to 1 on this firmware.