U7 Adds Contact Center with Facebook, SMS & Live Chat

The new version of CFD for U7 will be release shortly after the U7 release. So, it should come soon.

Always use the CFD version in parallel to the Update level. Or you will get those type of issues.
So U7Final it’s not U7Release? When expected the Release version?
 
So U7Final it’s not U7Release? When expected the Release version?
YES IT IS. But wait for the CFD U7.

Release = Final = Official.
 
  • Like
Reactions: N_G and spf
So U7Final it’s not U7Release? When expected the Release version?

Essentally, the 3cx PBX update has been released, however, the CFD software for V17 hasn't been released yet. V17 should be stable from the 3cx side, but the CFD software will be updated separately in the near future to match the backend changes from the PBX side.

Hope this helps explain :).
 
  • Like
Reactions: Evolute IT and spf
YES IT IS. But wait for the CFD U7.

Release = Final = Official.
Essentally, the 3cx PBX update has been released, however, the CFD software for V17 hasn't been released yet. V17 should be stable from the 3cx side, but the CFD software will be updated separately in the near future to match the backend changes from the PBX side.

Hope this helps explain :).
Updated within 1 min :) Brilliant work!
 
>>> Hide CRM Contacts from 3CX Apps Company Phonebook

It’s just ... WOW feature! finally
 
  • Like
Reactions: N_G and Evolute IT
The new version of CFD for U7 will be release shortly after the U7 release. So, it should come soon.

Always use the CFD version in parallel to the Update level. Or you will get those type of issues.

I do not understand that logic then. While I get what you are saying, then why push a non-Beta, released update U7 when it is known fact that some of us use the current version of CFD, which apparently is not compatible?

Not that it matters, but I see nothing in the release notes about it. I say not that it matters as the client did the update on his own, but without a release note or other to indicate the incompatibility, how would one know...such as you, for instance?
 
MMS supported or just SMS?
 
I do not understand that logic then. While I get what you are saying, then why push a non-Beta, released update U7 when it is known fact that some of us use the current version of CFD, which apparently is not compatible?

Not that it matters, but I see nothing in the release notes about it. I say not that it matters as the client did the update on his own, but without a release note or other to indicate the incompatibility, how would one know...such as you, for instance?
As a silver partner, you should already know why and hold off on updates for systems using CFD.

MMS supported or just SMS?
SMS only for now. MMS is coming later (don't ask for a timeline, we don't know.)

My guess is they will work on getting more providers before enabling MMS for them all.
 
I updated from stable 16.6 to 16.7 with root SSH commands ;
thx

This is a completely unsupported method of updating 3CX and will undoubtedly lead to issues and invalidate your support.
 
  • Like
Reactions: Evolute IT
I can't use the admin console, we manage over 200 PBXs.
We have a script that connects in SSH in each of our PBXs to perform the update via SSH command line.

You can update 200 instances via our instance manager easily and in a supported manner.
 
Last edited:
What completely rubbish. You can update 200 instances via our instance manager easily and in a supported manner.
Exactly what I thought lol
 
  • Like
Reactions: N_G
Regarding the CFD, you do t need to wait for a new CFD release. However, if you build our apps using quite old versions then you will see this. We talk about a version from 2019...
 
Last edited by a moderator:
  • Like
Reactions: FridayIT
Safari is a not supported browser we don’t check during QA.
 
If I have an active enterprise licence, why don't I see the option for update 7 in the management console? Current install is 16.0.5.619.

There is an update 5 hotfix 2 (16.0.5.622) that has been stuck there forever unable to upgrade due to an error. Does this need to be updated first before update 7 is available?
 
you are quite back, you need to go through the updates 1:1 to reach U7.
What is the error you get when installing U5H2?
 
  • Like
Reactions: Evolute IT
Thank you for your reply. Here is the message.

---

A problem occurred and 3CX Phone System was not updated successfully.

Your installation at {}.3cx.us encountered a problem and the update was not successful. The system was rolled back to the previous version.


Attached is the update log files which contain information about why the update failed.

Try and perform the update one more time. Chances are that the update will succeed. If not, contact support and send the log files.

---

How would I contact support to help with this?
 

Attachments

Can 3CX put together a tutorial on how the "Outbound caller ID in Outbound Rule and per Route" feature works w/ examples for common uses?

Does this work for any SIP trunk provider? Which outbound parameters for the SIP trunk does this modify?

"From : Display Name"
"From : User Part"
"Remote Party ID - Calling Party : User Part"

Thank you!

The outbound caller ID in the outbound rules works like the outbound caller ID in the extension settings. It overrides the same options in the outbound parameters.
The only difference is that it has the highest priority. So if you have an outbound caller ID set in your outbound rule and an outbound caller ID in your extension settings the one in the outbound rule will win.
More details will be available soon.
 
So does the new method of setting up Live Chat (https://www.3cx.com/docs/manual/live-chat/) replace the existing ones I already had setup ("Click2Talk" attached to a Queue)?

Should I delete those settings and set them up again in the "Messaging" menu? Or just leave the existing. Is there some benefit to setting up in the Messaging menu over what I already had set up or is it just moving the existing setting into a central location (if the latter it might have been nice if my existing already showed up there).

Thanks.
 
@Nick Galea It's all well and good to put a SP7 without doing functional resetting on CFDs as usual. Once again we have the right to a functional regression in having been warned of a pre-requisite or other.
For them and those who would not be all CFDs compiled before version 16.6.53 become inoperative on the SP7 !!!

So watch out integrator friends make a pass on your CFDs before the updates!
 
  • Like
Reactions: N_G
Hello @ENCOM-GEFFRAY thank you for your feedback.

The problem occurs on Call Flow Apps that are build on specific version of Call Flow Designer (16.3.19) and never rebuild (with newer CFD versions) and uploaded on management console.

Until those projects are build with the latest version of the Call Flow Designer(16.6.53), they will not be functional

It's kind of impossible to do verifications with whatever build we released up to now, to verify that it will compile successfully with the latest version of the PBX.

Definitely this is something that we keep a note internally and we will safeguard that his will not repeat in the future.
 
Last edited by a moderator:

Latest Posts

Forum statistics

Threads
111,990
Messages
590,161
Members
164,925
Latest member
batarong