Provisioning Client Settings for all users

[oJo]

Is there any way to make the client use certain default values? Our customers rely heavily on using a shortcut to dial and NEED + to be converted to 00. We know that there is a convoluted way to change this in the client software, but we need a reliable way to deploy this to all users. I have experimented with manipulating the settings XML, but it's a terrible ordeal.

 

[Vali_3CX]

oJo, this should be done at the PBX level, via outbound rules; the PBX is the one connected to providers, therefore the one knowing if the provider requires + or 00.

 

[oJo]

oJo, this should be done at the PBX level, via outbound rules; the PBX is the one connected to providers, therefore the one knowing if the provider requires + or 00.

But the client strips the + and just dials 43XXX instead of +43XXX. With the setting changed it dials 0043XXX.

 

[Vali_3CX]

That's what I'm talking about: each 3CX client user can customize its own settings, which is highly unreliable for your purposes. So, in the PBX, define such kind of rules:

• for every number starting with +, replace + to 00
• for every number starting with 43 and length of XX, prepend 00

(for every number starting with 00, leave it unchanged)
I'm not a master of PBX configuration, but I guess the two rules above combined will cover your case. Even more, it will cover ALL clients (Windows, Android, iOS, MAC, hard phones). See also the E164 Processing.

 

[oJo]

This doesn't work for us, as numbers starting with 43 can be local numbers as well. There has to be a way to reliably deploy the 3CX client setting to process + to 00 instead of dropping the +. This is one of the most basic features of dialing any phone number IMHO.

 

[Vali_3CX]

E164 doesn't help?

 

[oJo]

We are using E164 Processing, but the 3CX Client strips the Plus sign unless the client-side setting is configured.

 

[Vali_3CX]

I understand. So we go back to the outbound rules I mentioned above, where you missed the most significant element of my description:
number starting with 43 AND LENGTH of XX
so, if the number is local, it would be 43000000 (length 8). If it would be international, stripped of +, would be 4343000000, length 10, agree? In this case, your outbound rule will says
- for any number starting with 43 AND length 10 append 00 (so the number will become 004343000000).
Am I wrong?

 

[oJo]

I don't even think there is a minimum international phone number length, but it still wouldn't solve a local phone number conflict, as those can have virtually any length depending on the internal numbering scheme used by the called company. So if I dialed (+)44 870 990 8881 I'd want to reach the London eye internationally, but (+43 732)448709908881 would technically be a valid local number as well.

 

[oJo]

It also doesn't solve the issue of wanting to centrally manage the client settings, is there no mechanism to manage the 3CX client at all?