3CX v15.5 Update 2 Brings QR Codes, Hotdesking, CRM Integration and More

[nb]

Key goal is making PBX & client installation faster and easier - both on-premise and in the cloud - realized. With the latest update for v15.5 3CX have made deploying and managing the PBX even easier. Key improvements focused around minimizing administration as well as making the clients easier to deploy and use.

Provision Smartphones vi...​

Continue reading the Original Blog Post.​

 

[AramS_3CX]

Thanks Aram, If our client is happy with a quick reboot in the short term, is there a way to make them work?

No, I can't suggest you to do something that is not supported.
You can contact to Fanvil (for example, write a post on their forum) and ask them to implement it faster.
We already sent them an email to do that.

 

[StefanW]

I might also suggest that there be a new email variable to customize the FromName for email.

The name is generated from your activation company name and is handled on servicer side to keep the service healthy in terms of delivery scoring.

 

[jem1]

Fanvil informed us that the X6 models with the old HW version 1.1 need to be replaced. You can contact them for the replacement.
We are not planning to support the HW version that is old and need to be replaced.

I'm having Fanvil look into this but their initial response is that they are still supporting the 1.1 hardware devices and with 3CX as well.

 

[daneke]

No beta for my customer. When is the release?

 

[mtech1]

No, I can't suggest you to do something that is not supported.
You can contact to Fanvil (for example, write a post on their forum) and ask them to implement it faster.
We already sent them an email to do that.

Do you have a ETA for this? We are using Fanvil as they are on your supported list of phones?
I understand its a Fanvil issue, but even so, you must have let them know of this requirement when you 1st started testing? Are they usually quick to develop these features and release firmware? I have a client of whom this is now holding up an installation.

Many Thanks

 

[Phone systems NZ]

Hotdesking is not supported on Fanvil phones because they can't re-provision without the reboot.
Fanvil guys are working on this.
As soon as the "re-provision without the reboot" functionality will be implemented on Fanvil phones we will add them in Hotdesking too.

Has Fanvil given any time frames of when they will have there firmware updated to support this? Thanks.

 

[mtech1]

I'm having Fanvil look into this but their initial response is that they are still supporting the 1.1 hardware devices and with 3CX as well.

I have emailed Fanvil too. I will let you know the outcome, I will also be touching base with Voipon in the morning and sending them a link to this thread.

 

[AramS_3CX]

Do you have a ETA for this? We are using Fanvil as they are on your supported list of phones?
I understand its a Fanvil issue, but even so, you must have let them know of this requirement when you 1st started testing? Are they usually quick to develop these features and release firmware? I have a client of whom this is now holding up an installation.

Many Thanks

Its ok - hold the installation a lil' bit longer. This feature has been in the works for a very long time. It's ok if your client waits another 1 or 2 months.

Also leave the communication of how we inform Phone manufacturers up to us. When developers are given a task it is very common that it's not the only task you have at the moment. So you make roadmaps and put stuff into a queue... And then you move the task forward or backward depending on the priority, importance etc etc.

 

[AramS_3CX]

Has Fanvil given any time frames of when they will have there firmware updated to support this? Thanks.

Contact Fanvil for their ETA's.

 

[mtech1]

Fanvil were informed about this new functionality more than 1 month ago. And they were informed that the Hotdesking will be disabled for Fanvil phones in case they will not implement this new functionality on time.
We can't know why it's took so long to implement it. Usually they are fast to implement a new features, but this feature took more time than usual.
We don't have ETA from them, but we are forcing them to implement it as soon as possible.

Thank you, I look forward to their update.

 

[Sopock]

Thanks for this update, that worked.

I also think that updates for installed prompts should appear on main update page.

I want to thank anyone who resolved issue with public IP in this special update.
One small thing in next 1.0.1 web terminal could be to
add custom right click (context) menu for selection terminal background color like darkblue, mediumblue, midnightblue.
Someone could be confused by different outputs of Linux vs Windows traceroute. Or in other words - traceroute doesn't find all hops - tracert does.

Next one will not be so trivial.

Spoiler: Optional attachments?

Mac client should be prepared to find config which will be inside zip.

//Install into /Applications
NSArray * ConfigsToInstallPaths = [self findConfigToInstallInPath: [currentPath stringByDeletingLastPathComponent]];

This way, at least Mac users could completely avoid Welcome attachment. Hence no Security risk?!

 

[Rod Bacon]

I'm looking at the hot desking with Yealink T46S handsets. We run a custom phone template at the moment, as I needed to make the handsets look similar to the Cisco system that we just replaced. My question is, can I safely edit the default phone template (and not create a custom one) in order to ensure that my regular handsets and hotdesking-enabled handsets end up looking the same? I found 3 copies of yealinkt4.ph.xml nested below the %ProgramData% folder all with the same modified date/time (the one in the "updates" folder seemed to be used?) but when I edited them, I lost access to these devices altogether.

 

[datamerge]

The v1.0.0 firmware for Fanvil X6 seems to be faulty. I have tried both through 3CX management console and also downloaded the firmware to install directly on the phone. It fails with message "invalid file". I tested with another firmware I have which works to make sure it wasn't a handset issue.

 

[AramS_3CX]

The v1.0.0 firmware for Fanvil X6 seems to be faulty. I have tried both through 3CX management console and also downloaded the firmware to install directly on the phone. It fails with message "invalid file". I tested with another firmware I have which works to make sure it wasn't a handset issue.

This means that you have the old HW version (1.1) of the Fanvil X6 phones.
Our supported 1.0.0 FW version works only on the Fanvil X6 models with the new HW version (1.2).
Please contact to Fanvil for the replacement.

 

[datamerge]

LLDP on Fanvil handsets (talking about X4 here as that is what I am using) is able to be selected in the phone provisioning. However, it is only setting one of 2 entries in the template file necessary to make LLDP function.
The setting <LLDPTransmit> is linked to the feature, but by itself the phone will not do LLDP properly.
The setting <LLDP_Learn_Policy> needs to be 1 when LLDPTransmit is 1 for LLDP to work.

 

[datamerge]

Nick, do you want feedback through this thread?

 

[datamerge]

This means that you have the old HW version (1.1) of the Fanvil X6 phones.
Our supported 1.0.0 FW version works only on the Fanvil X6 models with the new HW version (1.2).
Please contact to Fanvil for the replacement.

Thanks Aram.

I see there are other Fanvil issues. We will just have to nag Fanvil.

 

[nb]

LLDP on Fanvil handsets (talking about X4 here as that is what I am using) is able to be selected in the phone provisioning. However, it is only setting one of 2 entries in the template file necessary to make LLDP function.
The setting <LLDPTransmit> is linked to the feature, but by itself the phone will not do LLDP properly.
The setting <LLDP_Learn_Policy> needs to be 1 when LLDPTransmit is 1 for LLDP to work.

Agreed thanks for reporting. We will update it in the next template update

 

[nb]

Nick, do you want feedback through this thread?

Yes sure - definitely - this is why there is a thread specifically for the release.
If they are new feature requests or new ideas and proposals proceed to put them in ideas section of the forum.

 

[NickD_3CX]

Yes, the SMTP offer was genius. I like that the instance company name shows up as the "from" name. But, we did notice that invites for conferencing did not include the friendly name "3CX Phone System CompanyName <[email protected]>", it only shows "[email protected]". If the tenant or instance name can be included in all emails generated it would be helpful.

This actually works, but it depends on your mail client. Example, GMail, even when it receives an email with an ICS, it still displays the From SMTP Display Name. Outlook Live on the other hand when it receives ICS mail displays what is found in the ORGANIZER CN parameter which is "[email protected]" which cannot be changed (you can check the message source to see this).

Anyhow, you should be able to use in the "WebMeeting Profile" options the "WebMeeting" option instead of the "Webinar" one. This will launch your own mail client in a new pop-up to send it which should remedy this as you would then be sending natively from your own account.