3CX Update 6 Alpha: Improved Call Data Records & Reports

[rayt]

Lots of great stuff in this update . I haven't tried it all yet.

One report that I would love to see is: number of SCs per trunk & system.

This would be invaluable for planning when to upgrade a 3CX licence and/or SIP trunk.

 

[Alphabetic]

Just got back from a week away, im looking forward to testing this update!

 

[tronic]

Lots of great stuff in this update . I haven't tried it all yet.

One report that I would love to see is: number of SCs per trunk & system.

This would be invaluable for planning when to upgrade a 3CX licence and/or SIP trunk.

We have all been dreaming of this for years. LOL

 

[N_G]

@tronic we will make it

 

[tronic]

@tronic we will make it

I think I just heard angels singing. Is this what happiness feels like?


As always, I'm super grateful.

 

[N_G]

@tronic thank you for your nice words

 

[Sajjad.Khurshid]

After Update 5, we are unable to upload IVRs with more than 10,000 entries.


Is this a known issue that others are experiencing as well? If so, is there any information on when it will be resolved? Also, is there any workaround available to use such large IVRs in the meantime?

 

[N_G]

The IVRs are not designed for 10,000 entries. Then you better create a callflow script that can make a lookup in some database or something. Depending on of course what exactly the IVR does..... But I assume some kind of customer lookup

 

[dleduc]

Anybody else on U6 Alpha can't see their recordings anymore in the WebClient? I see the files on the server, but they are no longer available on the user and/or admin interface.

 

[edossantos_sipcaller]

The IVRs are not designed for 10,000 entries. Then you better create a callflow script that can make a lookup in some database or something. Depending on of course what exactly the IVR does..... But I assume some kind of customer lookup

Nick, I think he's referring to a big CFD app. He's using many custom components, and the resulting C# script is too big, and 3CX rejects it when uploading it. This seems to be a limitation recently added, as the same CFD app was uploaded in previous versions without problems.

 

[Sajjad.Khurshid]

Nick, I think he's referring to a big CFD app. He's using many custom components, and the resulting C# script is too big, and 3CX rejects it when uploading it. This seems to be a limitation recently added, as the same CFD app was uploaded in previous versions without problems.

Yes, exactly — we have a large CFD app with many custom components and the resulting C# scripts, which 3CX now rejects. it was working fine in the previous version without any issues.

 

[fxbastler]

aha, changed colors

v20u5


v20u6alpha


The problem could be: it's difficult to explain custom status to customers, especially since you've always been able to change the name.

Since the names of the other three status have also changed in recent years, understanding of them is limited and there are also different ways to describe the same thing in different languages (in the last few years: Nicht stören, Bitte nicht stören, DND, Out of Office, OoO ... - among others, plus the many different ways to express business and non-business hours and their automatic status changes).
We often describe things to customers using colors or create color coded instructions as the only constant over the last 10 years.
They're not stupid. We and our customers can read and understand simple text instructions; we're in Europe. But the changes of the last few years force us to do so.
On top of that, a significant proportion are men. How are we supposed to explain the colors to them? Until now it was easy: green, orange, red, light green and pink. Now instead we're seeing something like turquoise / cyan-blue (2FBBB3) and something like darker cyan-blue (1D8FD2) ...
Some of these people aren't exactly young anymore, either - included me.
This makes the difference even more difficult to explain.

These / our instructions therefore are all obsolete. We have to create all these instructions again: descriptions, screenshots, colors. Not nice.

And actually, I'm not talking about changes in the last 10 years but the last two – where the names often went back and forth. Now the colors, too

 

[tronic]

aha, changed colors

v20u5
View attachment 47459

v20u6alpha
View attachment 47460

The problem could be: it's difficult to explain custom status to customers, especially since you've always been able to change the name.

Since the names of the other three status have also changed in recent years, understanding of them is limited and there are also different ways to describe the same thing in different languages (in the last few years: Nicht stören, Bitte nicht stören, DND, Out of Office, OoO ... - among others, plus the many different ways to express business and non-business hours and their automatic status changes).
We often describe things to customers using colors or create color coded instructions as the only constant over the last 10 years.
They're not stupid. We and our customers can read and understand simple text instructions; we're in Europe. But the changes of the last few years force us to do so.
On top of that, a significant proportion are men. How are we supposed to explain the colors to them? Until now it was easy: green, orange, red, light green and pink. Now instead we're seeing something like turquoise / cyan-blue (2FBBB3) and something like darker cyan-blue (1D8FD2) ...
Some of these people aren't exactly young anymore, either - included me.
This makes the difference even more difficult to explain.

These / our instructions therefore are all obsolete. We have to create all these instructions again: descriptions, screenshots, colors. Not nice.

And actually, I'm not talking about changes in the last 10 years but the last two – where the names often went back and forth. Now the colors, too

As long as the mobile app matches the colors i can see it being a big problem

 

[N_G]

We saw the difference in colors too little and I believe we copied the teams colors so they would recognize them. But it's open to debate of course

 

[KoesioOccitanieTech]

We saw the difference in colors too little and I believe we copied the teams colors so they would recognize them. But it's open to debate of course

I think it's a really good thing for colorblind people !

 

[Grace Liu]

Yes, exactly — we have a large CFD app with many custom components and the resulting C# scripts, which 3CX now rejects. it was working fine in the previous version without any issues.

If you can successfully upload CFD to 3CX server after you randomly delete some components, you can try to add one parameter(SCRIPT_CODE_MAX_LENGTH) and put a value of 500000, and check if it is OK.

We've had similar problems before.

 

[pmterp]

RE: Change to colors
The change would require re-learning and modifying of help materials on our end.
When we have clients that use a combination of desk phones and mobile apps (which is quite common), we'll by default disable PUSH for the "Available" status. We'll change custom status 1 to "Mobile" and enable PUSH on that one. Then we instruct the users, "Dark green will just ring to your desk phone. Light green will ring to your desk phone and your mobile app."
So "green" (either one) means calls will come through, just with a variation.
For that reason, I like the multiple shades of green although I can see where a more distinct color could be appropriate in some cases.

 

[KoesioOccitanieTech]

RE: Change to colors
The change would require re-learning and modifying of help materials on our end.
When we have clients that use a combination of desk phones and mobile apps (which is quite common), we'll by default disable PUSH for the "Available" status. We'll change custom status 1 to "Mobile" and enable PUSH on that one. Then we instruct the users, "Dark green will just ring to your desk phone. Light green will ring to your desk phone and your mobile app."
So "green" (either one) means calls will come through, just with a variation.
For that reason, I like the multiple shades of green although I can see where a more distinct color could be appropriate in some cases.

I don't think "color" of the status in the big deal here, the name of the status matter imo. Even if the color is changing the name will stick and in your example it's really clear by the name.

I understand your point with "help materials" but it is what it is, we did one with the V18 webclient and 6 months later the V20 was annonced with all the changement of it

 

[Sajjad.Khurshid]

If you can successfully upload CFD to 3CX server after you randomly delete some components, you can try to add one parameter(SCRIPT_CODE_MAX_LENGTH) and put a value of 500000, and check if it is OK.

We've had similar problems before.

Thank you for your response and guidance.
Should I add this in the CFD or in the 3CX Parameters Settings?

 

[Grace Liu]

Thank you for your response and guidance.
Should I add this in the CFD or in the 3CX Parameters Settings?

Add the parameter(SCRIPT_CODE_MAX_LENGTH) in 3CX parameters settings