Problem with VoIP Configuration on SMB

[Soroosh]

Hi Mates,

 Recently, I tried to configure VoIP on an SMB 1535 with firmware R81.10.17, but it could not save the configuration and displayed the following error: "Cannot edit VoIP network object group." I rebooted and reset the firewall to its factory settings, but that didn't help.
We already have this configuration on another SMB 1775 with firmware R81.10.10, and it works without any problems.
Can anyone help me solve this issue? Is this a firmware bug?

Thanks in andvance 🙂

[Soroosh]

Update:
I downgraded the firmware to R81.10.10, the latest recommended version, but the problem still exists!

So it is not a firmware bug! 

[G_W_Albrecht]

Strange . i would try USB re-imaging first before we ask CP TAC.

[Soroosh]

Hi,
I've already reimaged it via USB. The first time the unconfigured gateway from R81.10.10 (the factory default) to R81.10.17. The second time, I downgraded from R81.10.17 to R81.10.10 (the latest recommended version). Lastly, I brought the gateway back to R81.10.17 via the GUI.
The problem occurred in every state.

[G_W_Albrecht]

Did you use a backup or set up each version completely from scratch ?

[Soroosh]

I've sat up each version from scratch. The only exception is the last one. That one is back from R81.10.10 to R81.10.17.

[G_W_Albrecht]

Looks like a hardware issue to me. Strange to show with VoIP. Would suggest to ask CP TAC...

[Soroosh · Accepted solution]

I've tried to figure out what exactly caused the problem, and I found that the VoIP configuration cannot be saved when the Service Provider Name is changed from "SIP-Provider" to anything else. The firewall cannot rename the group name "SIP-Provider". Without this, I could save the configuration.

[G_W_Albrecht]

Yes, sip-provider, ip-phones, pbx-server - things used by VoIP wizard should not be touched...

[Soroosh]

The web interface gives the option to rename this object (SIP Service Provider Name in VoIP Page). However, the underlying system is preventing the modification of this default, system-generated group. This conflict between the UI's front-end action and the back-end restriction is what triggers the "Cannot edit VoIP network object group" error. 😞

[ronk]

>> the VoIP configuration cannot be saved when the Service Provider Name is changed from "SIP-Provider" to anything else

Thanks for the feedback. We're opening an internal bug for this issue.
It's likely to be fixed by the next version — either by making those fields read-only or by allowing the names of these network group objects (both "SIP-Provider" and "IP-Phones") to be changed.

[ohadp]

Hi @Soroosh,

We have a fix available for your issue.

If it’s urgent, feel free to email me directly at [email protected], and I’ll provide you with the JHF image.

Otherwise, the fix is expected to be publicly available around mid-July.

@G_W_Albrecht - FYI.

Thanks,
Ohad

[Soroosh]

Hi Ohad,
Thank you for your prompt response. It's not urgent since I was able to configure VoIP. It works properly with the default names.
I can wait for the official public release.

Yours
Soroosh