3CX V18: Connecting Teams & Customers - Faster, Better, More Efficiently

[jaywagener]

I strangely hat this one morning after it had worked well for weeks. Once I started the desktop app, the issue stopped however when I only used the mobile app, all calls failed. MS Support to clear some cache in the app which did not resolve my issue while not using the desktop app in tandem. I removed on my iOS device the app and reinstalled it and 10m later all was back to normal. Would this fit your situation? Do you still have any other SBC configuration in your teams tenant?

Ok, we have tested in a completely new Microsoft tenant and are receiving the same behavior on a manual rejection (pressing the big red button) on inbound calls to Teams. Once the button is pressed, the 603 Decline message is sent to the PBX and the call is dropped.

We have tested with 3 different inbound carriers, just to rule out the carrier and now with a different Microsoft tenant. If this is normal behavior on the 3CX, I can accept that, but is a fairly large issue for our clients as most users are accustomed to pressing the red button if they don't want to talk with the person. Let me know if I'm missing something on the setup or on the 3CX. I feel that there is something simple that we missed or misconfigured.

 

[N_G]

We will follow this up and revert...

 

[bravad]

Ahhhhhhhhhhh !!!!! Coooomone ! Seriously? ​

We use this field for the CNAME !
The CallerID is provided by the extension !


We want to avoid changes being made in the Outbound Parameters Tab !! ..
It attracts the curious and customers break the other headers... If I ask to modify to a Custom field ...

Stop controlling the fields so severely! Why ? How does it negatively affect 3CX to let the right to be able to put spaces or a hyphen in a field!


>>>
Please remove limitations in fields in the next update ...
Outbound Caller ID in extensions settings and in Outbound Caller ID in SIP TRUNKs settings !
thx / <<<

Please Offer a holiday to the one who had the idea of "limiting" his fields! ​

Friendly​

 

[NickD_3CX]

Ahhhhhhhhhhh !!!!! Coooomone ! Seriously? ​

View attachment 23767


We use this field for the CNAME !
The CallerID is provided by the extension !


We want to avoid changes being made in the Outbound Parameters Tab !! ..
It attracts the curious and customers break the other headers... If I ask to modify to a Custom field ...

Stop controlling the fields so severely! Why ? How does it negatively affect 3CX to let the right to be able to put spaces or a hyphen in a field!


>>>
Please remove limitations in fields in the next update ...
Outbound Caller ID in extensions settings and in Outbound Caller ID in SIP TRUNKs settings !
thx / <<<

Please Offer a holiday to the one who had the idea of "limiting" his fields! ​

Friendly​

Hi!

I understand what you are using it for, however, most other users don't use it the same way and end up breaking their SIP Trunk when they enter a number with spaces, hyphens, etc, as these characters are translated to ASCII when put in the User Part of a SIP message.

If you really need to hard-code the CNAME, it seems you already know what you need to do in the Outbound Parameters, and quite frankly this is the way you should have done it in the first place.
You were misusing the field by using it for the CNAM while it was intended for the CID.

 

[NickD_3CX]

Hello
is there already an approximate release date for the ios app v18?

Regards
fabs

The App the you can currently find on the App Store is fully compatible with 3CX V18.

 

[bravad]

Hi!

I understand what you are using it for, however, most other users don't use it the same way and end up breaking their SIP Trunk when they enter a number with spaces, hyphens, etc, as these characters are translated to ASCII when put in the User Part of a SIP message.

If you really need to hard-code the CNAME, it seems you already know what you need to do in the Outbound Parameters, and quite frankly this is the way you should have done it in the first place.
You were misusing the field by using it for the CNAM while it was intended for the CID.

So in 2021 .. you have to "hard-code" a CNAME ... Let's see, in Canada & USA .. it's standard a ... CNAME ...
We shouldn't have to "hard-code" that in Header Outbound Parameters .. .
Please .. Provide at least one CNAME field in this case ... Above the Outbound CallerID field .. that would make a lot of sense ..

The amount of 3CX North American customers ... Please consider ..

 

[NickD_3CX]

So in 2021 .. you have to "hard-code" a CNAME ... Let's see, in Canada & USA .. it's standard a ... CNAME ...
We shouldn't have to "hard-code" that in Header Outbound Parameters .. .
Please .. Provide at least one CNAME field in this case ... Above the Outbound CallerID field .. that would make a lot of sense ..

The amount of 3CX North American customers ... Please consider ..

Now that is a valid argument.
As this is not currently planned, I would suggest you create a thread in the 'Ideas' section.

 

[Evolute IT]

So in 2021 .. you have to "hard-code" a CNAME ... Let's see, in Canada & USA .. it's standard a ... CNAME ...
We shouldn't have to "hard-code" that in Header Outbound Parameters .. .
Please .. Provide at least one CNAME field in this case ... Above the Outbound CallerID field .. that would make a lot of sense ..

The amount of 3CX North American customers ... Please consider ..

It's only for Canada... They won't do it. We asked for years and got the Outbound Caller ID field in Outbound Rules.

They are right by the way, you should use the provider or the Custom Field in headers to set a CNAME, specially since it's fixed on the trunk anyway.

The Caller ID field is for DIDs. Not text.

 

[FridayIT]

Now that is a valid argument.
As this is not currently planned, I would suggest you create a thread in the 'Ideas' section.

I cant post in the ideas section post, but another benefit of this, is it would allow much more easier changing of CNAME (Display Name) and and DID (User Part) "from" fields. Right now you can only do phone number or name easily in the custom field, if we had one more field we could do both Cname and number display.

In our case, I as an example have my name directly appear, however, HR wants to show as HR rather than their names. I can work around this by using trunk/outbound rules. but it would be much easier to have 2 fields per extension.

 

[gbourgeois]

C'est seulement pour le Canada... Ils ne le feront pas. Nous avons demandé pendant des années et obtenu le champ Outbound Caller ID dans Outbound Rules.

Ils ont raison, vous devez utiliser le fournisseur ou le champ personnalisé dans les en-têtes pour définir un CNAME, d'autant plus qu'il est de toute façon fixé sur le tronc.

Le champ ID de l'appelant est destiné aux SDA. Pas de texte.

En effet @Frederick,
Les fournisseurs SIP aux États-Unis supportent de plus en plus la transmission du champs CNAME ex. Vitelity (mais ne le supporte pas en entrée pour l'instant, sauf quelques exceptions).
Donc les appelants aux États-Unis qui appellent vers le Canada ( Nous avons des clients comme ça ).

Ceci dit, il est évident que de créer un "POST" dans les idées pour ajouter ce champs est peine perdue ..
Une de mes suggestions ( Audit logs ) a nécessité 4ans pour voir le jour ... ( Enfin dispo sur V18 ! )

Même si je crois que ce serait simple pour 3CX ajouter ce champs ... c'est évident qu'ils ne le feront pas.

Comme le disent souvent les clients " Même les vieux systèmes téléphonique numérique offre cette solution depuis les années 1880 c'est possible ... Je ne peux pas croire en 2021 ça ne se fait pas ! " (Joke)

Ça reste un choix incompréhensible .. Restreindre l'utilisation d'un champ pour les quelques clients qui ne savent pas l'utiliser. Depuis aussi longtemps que je me souviens ( V12.5 / sauf erreur ) , il a toujours été un champ "ouvert" ...
Il y a sans doute moins de 1% plainte pour décider ajouter une validation ...
Mais nécessite beaucoup votes pour attirer l'attention des concepteurs (Sauf exception)..

Aujourd'hui, avec les Bridges, il n'est pas rare ... et serait pratique de transmettre CID avec ;ext=0000 .. V18 empêche ça maintenant !


C'est un choix dans le même sens que les boutons dans le WebClient ... Choix illogique / incompréhensible ...
Il a de la place en dessous ! Pourquoi créer un menu qui ajoute des cliques !!!





C'est dommage que, à chaque mise à jour de 3CX PBX majeur, 3CX réussi toujours à "supprimer" des fonctions ou des solutions ... qui marche déjà. Mais ... lorsque nous sollicitons des ajouts ... c'est un processus très long et très complexe.

Bref, c'est à ne rien comprendre ..

 

[gbourgeois]

I cant post in the ideas section post, but another benefit of this, is it would allow much more easier changing of CNAME (Display Name) and and DID (User Part) "from" fields. Right now you can only do phone number or name easily in the custom field, if we had one more field we could do both Cname and number display.

In our case, I as an example have my name directly appear, however, HR wants to show as HR rather than their names. I can work around this by using trunk/outbound rules. but it would be much easier to have 2 fields per extension.

My goal is not to denigrate 3CX, but must be realistic .. This tell ... the truths.

I can post the idea but I agree with Frédérick Marcoux , I don't think 3CX will do it ..
My perception is that 3CX "works" on a logic of "If this can help the majority of END USERS, we proceed..."

Better to work with an API from your SIP Trunk distributor.. or look at @VoIPTools (not recommended by 3CX¹ but Voiptools is doing a good job, you will not have problems caused by this tool, We are also a reseller of this product)

Even via the tickets .. it's not going any faster .. I have a ticket opened in December 2019 .. A design error .. The ticket is still in "Being Processed by RandD Department" status with internal ID of the R&D case #16564 (If someone at 3CX isn't convinced it's true)

There is had 4 updates for 3CX phonsystem since .. this has never been fixed ! I relaunched .. I got that as an answer; "In general, there is no guarantee that a concern that is brought to our attention will be corrected or when, it is a decision that belongs to R&D."

All I have to say is that we will no doubt have overcome a global COVID pandemic in less time than it took to process my ticket to support.

I am not angry,
I am disappointed!


- Is the 3CX Support team fantastic and knowledgeable? Hooo Yes!
- Am I convinced this is the best phone system product ? Yes ! (Everyone has their own preferences)
- Do I like the 3CX solution and its different functions? I love !
- Does 3CX listen sufficiently to its Partners in the choice of the design of new functionalities or the withdrawal of functionalities? ... I'll let you guess my answer.


Yet who is best at "update" recommendations ?
The Resellers/Partners who receive customer feedback ?
or
Developers who receive internal Tickets .. IF the agent (Support) has seen fit to report the info to the developers.


Good day


------
¹ 3CX will tell you that the support might be invalidated if VoipTools broke 3CX but .. the VoipTools team is doing a good job, it won't broke your 3CX and its components.

 

[Evolute IT]

FYI: My v18 update (fresh install, then restore from complete 3CX backup) did NOT restore the custom CRM template. Could custom CRM templates be added to the list of things that are backed up?

I can confirm this behaviour. An in-place upgrade does keep them tho.

 

[aschildmeyerSTR]

I see your case as well but I think there is a little missunderstanding here. As you describe your case, I think you mean for example forwarding rules and above all you have enabled all the mailboxes. What I'm talking about is the forwarding when I have someone on my phone. Sorry for my english, maybe it is better called the transfering of a call.
This is what I'm talking about.
View attachment 23693
And in our case, we have disabled all mailboxes in the extensions, and when we transfer the call and I look for a name or the extension of a colleague, there is his extension and the extensions mailbox listed, where I can forward to. Some colleagues have problems with this and they don't see the difference and transfer the call to the mailbox, where it says the caller, that the extensions mailbox is disabled.
So the question is not why the mailbox is listed here generally, the question is, why is it listed for extensions where the mailbox is disabled.

I get your point for sure. But what I mean is exactly that. I have people that tell callers "Oh so and so isn't here right now, do you want voicemail or I can leave a note?" Many callers say give me the voicemail. So the person will click Transfer, type the name an select "User - Voicemail" and push the caller straight to voicemail. This is nice as it doesn't impact the missed calls score to the person who is away from there desk as it's registered as answered by someone else and sent straight to the persons voicemail. Also, in my scenario if I have unknown people calling the receptionist who handles our main cooperate phone number sends them straight to my voicemail rather than to my extension. Then I'll never have my phone ring and I can see a text caption of what usually a sales person is trying to sell me.

But I do get your point of having a flag to turn that functionality on or off globally or maybe per extension. Like executives might have it only where front line workers don't.

 

[RemoMeyer]

Olá,

Atualizamos recentemente para a V18, deparamos que na pagina de contatos mostra a chamada em andamento, mas não marca ela na cor azul igual tinha na V16.
Queria fazer uma sugestão de melhoria para a V18, ter essa característica que facilita bastante em nossa equipe.

V16:
View attachment 23587

V18:View attachment 23588


Aguardo retomo.

Thats really a big problem. The users need a clearer visual Feedback of the call information of other users and the blue background helped.

Anyone else think so?

@Pedro Torre

Eles somente responden posts/comentários em inglês na regra, com raras exceções

 

[RemoMeyer]

I have found another issue:

1 - Queue 800
2 - Users 000 and 100 in Queue 800
3 - User 000 is Queue Manager
4 - User 000 try user 100 Logg Out
5 - User 100 is Logged Out

6 - In Webclient/Teams "Q" is still active:



Is that know ?

 

[ChrisC_3CX]

@RemoMeyer

The Q icon under each extension/user indicates the Global Queue Login status. When a Queue Manager logs an extension/user in our out of a Queue, what they are doing is explicitly logging them in/out and not globally. That said, the icon will remain in the scenario you described because the extensions/users in question are still globally logged into the Queues.

 

[RemoMeyer]

"Global Queue" - There are just one Queue

How can the manager "globally" loggout the user?

 

[ChrisC_3CX]

"Global Queue" - There are just one Queue

It doesn't matter how many Call Queues a user/extension is a member of, global Queue login status is different that explicit queue login status. For more information regarding Queues I recommend going through the guide.

How can the manager "globally" loggout the user?

A Queue manager cannot perform a global login/logout on behalf of an extension from within their own 3CX Client. The extensions would have to log themselves out from the 3CX client:
3CX Webclient/Desktop App:



If the Queue Manager has Management Console access, then they can globally log the extensions out/in from there by going to "Users >> Select user >> Status":



Another alternative is to give the Queue Manager extension "Receptionist" rights and therefore allow the Queue Manager to change an extension's Profile Status to one that has the "Log out from Queues" option enabled:

"Management Console >> Users >> Forwarding Rules >> Select Profile Status >> Options"

 

[inknow]

Webmeeting is getting better and better, but right now i think you should take a look that chat dialog box appears over presentation area, almos transparent, but it blocks some presentation area, it would be great to resize presentación area in case of chat box is in use.

 

[ChrisKoll]

Ahhhhhhhhhhh !!!!! Coooomone ! Seriously? ​

View attachment 23767


We use this field for the CNAME !
The CallerID is provided by the extension !


We want to avoid changes being made in the Outbound Parameters Tab !! ..
It attracts the curious and customers break the other headers... If I ask to modify to a Custom field ...

Stop controlling the fields so severely! Why ? How does it negatively affect 3CX to let the right to be able to put spaces or a hyphen in a field!


>>>
Please remove limitations in fields in the next update ...
Outbound Caller ID in extensions settings and in Outbound Caller ID in SIP TRUNKs settings !
thx / <<<

Please Offer a holiday to the one who had the idea of "limiting" his fields! ​

Friendly​

Try removing the space between Bravad ti and use Bravadti