Update 7 - DECT, VoIP Providers, RPS Mass provisioning

[techcare]

Sorry if this has been discussed before... but how come we can only add one phone to an extension in the webclient admin?

Happily admit it's not very common for us to do so, but the use case I had today was swapping from a normal phone to SBC phone. I would prefer to pre-configure my SBC phone and then remove the original phone after install. Not a big deal, just wondering if I'm missing something.

Same issue. Need to add an SBC phone AFTER existing phone provisioned and it is only possible to do it via new interface.

Only work around at this stage is to remove the current phone (downtime for user). Add SBC phone. Then using old admin interface add new non SBC phone.

Can we get add another phone to the Web client admin @Nick Galea ?

 

[CentrexJ]

Same issue. Need to add an SBC phone AFTER existing phone provisioned and it is only possible to do it via new interface.

Only work around at this stage is to remove the current phone (downtime for user). Add SBC phone. Then using old admin interface add new non SBC phone.

Can we get add another phone to the Web client admin @Nick Galea ?

I'm not against the ability to do multiple phones in web client. But just a clarification to your message, there is no downtime involved in the current process. The only downtime is the very short inability to provision the non-router phone until you add it back to the management console after adding the router phone. The non-router phone doesn't drop its connection just because you delete it from provisioning.

 

[techcare]

I'm not against the ability to do multiple phones in web client. But just a clarification to your message, there is no downtime involved in the current process. The only downtime is the very short inability to provision the non-router phone until you add it back to the management console after adding the router phone. The non-router phone doesn't drop its connection just because you delete it from provisioning.

So if I remove a phone from user, it won't deny connection? Even though extra security is turned on?


I will test and report back.

Still doesn't remove the need for having "ADD PHONE" to the webclient portal. Work arounds are fine temporarily.

 

[SweetAction]

So if I remove a phone from user, it won't deny connection? Even though extra security is turned on?

View attachment 34555
I will test and report back.

Still doesn't remove the need for having "ADD PHONE" to the webclient portal. Work arounds are fine temporarily.

No, the only thing that will deny an already provisioned, working phone from continuing to work is a change in the SIP auth credentials.

It won't get new updates / changes (like some names, new/removed BLFs, etc) if it can't talk to provisioning server, but it will continue to make and receive calls without any issues.

 

[sam.phillips]

I'm not against the ability to do multiple phones in web client. But just a clarification to your message, there is no downtime involved in the current process. The only downtime is the very short inability to provision the non-router phone until you add it back to the management console after adding the router phone. The non-router phone doesn't drop its connection just because you delete it from provisioning.

Yes correct! Hence my comment of 'no big deal', just a nice to have so we can retain remote provisioning of handsets before they get swapped out - like sending a phone to customer for self-install, but still needing to manage the old phone in the mean time.Niche use case for sure.

 

[CentrexJ]

We use yealink and last week we had our supplier update the phones firmware before shipping so the router phone feature was truly plug and play. We didn’t have to manually update the phone once connected at customer or ship to our office to update ahead of time. Hopefully their next inventory shipment from China has the newer firmware already in the box.

 

[renroh20]

Hello 3CX, any news on when Update 7 will move to Beta, or even the Final release please?! Very keen to get the Jabra headset issues fixed for customers. Many thanks in advance

 

[YiannisH_3CX]

Hello 3CX, any news on when Update 7 will move to Beta, or even the Final release please?! Very keen to get the Jabra headset issues fixed for customers. Many thanks in advance

You mean this? https://www.3cx.com/community/threads/update-7-beta-new-deployment-server.119564/

 

[SteveITS]

Very keen to get the Jabra headset issues fixed for customers.

Alternatively see thread https://www.3cx.com/community/threads/webhid-headset-integration-how-it-works.119133/#post-554874 for some beta app links.

 

[renroh20]

@YiannisH_3CX - sorry not quite, on existing systems I only see the Alpha release, is there any ETAs for the Beta or full Release for existing systems please?

@SteveITS - thanks for that, very helpful, I'd missed that.

 

[YiannisH_3CX]

sorry not quite, on existing systems I only see the Alpha release, is there any ETAs for the Beta or full Release for existing systems please?

To get to the Beta you need to install the Alpha first. But I would recommend waiting for the final release. I do not have an ETA for you but we are close.

 

[jed]

Hi Team 3CX. We are pleased to see the re-adding of the "Starting range 00X only via Management Console"
Would it in any way be possible to also add this possibility to the o365 creation of users, please?
Thanks a million.

 

[timmbo]

Hi.

It seems that from the M.C. to go to the Phones-Webinterface (Phone-UI) wont be able to do this on new Snom Webinterface(D865) anymore.
The old Webinterface is now on Port 3112.

Bye
Timm

 

[JohnS_3CX]

Hi.

It seems that from the M.C. to go to the Phones-Webinterface (Phone-UI) wont be able to do this on new Snom Webinterface(D865) anymore.
The old Webinterface is now on Port 3112.

Bye
Timm

Correct, we don't know if Snom will change it in the future but for now it is not possible to auto-login. It will just take you to the phone page and you must login manually.

 

[timmbo]

OK. But maybe on the old Webinterface on Port 3112 will work.

Bye
Timm

 

[JohnS_3CX]

OK. But maybe on the old Webinterface on Port 3112 will work.

Bye
Timm

Hi Timm,

Unfortunately not doable for now because we use a single unified link for all the Snoms and if we change it to point to 3112 then the others that use 80 like D1xx, D3xx, D7xx will stop working.

The D8xx is the exception to the rule because it runs two different web interfaces (for now at least).

And additionally we do not know if Snom plans to keep the classic interface on those or will remove it entirely at a later stage. We will have to see what they decide doing in the end after the firmware is a bit further developed, and act accordingly.

 

[timmbo]

OK, i understand it.

I will talk with Snom on this.

Bye
Timm

 

[timmbo]

Hello Tim,


It is work as design, the fill-in credential is no longer supported due to security issue.





Best regards,
Samuel