Template for extensions

[David_K]

Hello

Not sure I'm missing something but is there a way to create templates used when creating an extension?

For that customer when I create an extension I change many things manually : disable voicemail, change the phone langage and LED settings, recording settings, setup default BLF keys (everyone has the same) and so on... so many things I'll forget most next time I'll create an extension.
I did not find a way so that when I create a new extension manually (or created automatically when in sync with M365) all our default settings are automatically configured.

Is it possible?

 

[Saqqara]

There is not default settings for extensions that will be applied to new extensions.

What you can do, is select multiple extensions and click on edit where you block change settings for all the selected estemsions

 

[SweetAction]

I typically setup 1 ext the way I want it, then use the copy button or export/import button depending on number of new exts needed.

 

[VoIPTools]

Our 3CX Active Directory Sync tool uses a "template" user when creating extensions. Further, we use the "Department" field to optionally create groups and assign extensions to the group. So, it could be done if needed.

 

[Saqqara]

I typically setup 1 ext the way I want it, then use the copy button or export/import button depending on number of new exts needed.

I doubt this will work, as the user is using sync with m365, so the extension is automatically created - not the same as copy an extension to a new extension

 

[VoIPTools]

Agreed @Saqqara. My only point is there are ways to programmatically create extensions using a "template" extension. It was a general statement if another approach is needed.

 

[NickD_3CX]

@Saqqara is right, but you could use what @SweetAction said a different way when you want to create a new user:

1. Use the "Copy Extension" feature to create your new extension
2. In the new extension, manually enter the email address that this user has on MS365.
3. Enable MS365 sync for this user.

What will happen is that the MS365 sync will see that there is already an extension wit this email and sync the user data from MS365 onto the already created extension.

 

[David_K]

Thanks @SweetAction that could be a solution

But extensions are created automatically by the M365 sync.

It does not seem to be any kind of template to be used automatically in that case.
Maybe a valid feature request?

 

[accentlogic]

@David_K I was able to find an existing Idea for this. Please vote it up.

https://www.3cx.com/community/threa...tes-for-reducing-extension-programming.59395/

The request does mention that Copy would be acceptable, but with the growing use of auto-created extensions the need for a default Extension Template is increased.

 

[SweetAction]

Thanks @SweetAction that could be a solution

But extensions are created automatically by the M365 sync.

It does not seem to be any kind of template to be used automatically in that case.
Maybe a valid feature request?

In this case, Nick has the answer - basically create via import and it will match up after you enable sync. Don't enable sync until after the user is created. It's not a solution, just a work around that does make some manual work.

@Saqqara is right, but you could use what @SweetAction said a different way when you want to create a new user:

1. Use the "Copy Extension" feature to create your new extension
2. In the new extension, manually enter the email address that this user has on MS365.
3. Enable MS365 sync for this user.

What will happen is that the MS365 sync will see that there is already an extension wit this email and sync the user data from MS365 onto the already created extension.

 

[David_K]

@David_K I was able to find an existing Idea for this. Please vote it up.

https://www.3cx.com/community/threa...tes-for-reducing-extension-programming.59395/

The request does mention that Copy would be acceptable, but with the growing use of auto-created extensions the need for a default Extension Template is increased.

Thanks @accentlogic but I can't vote on the idea, I get this message :

 

[David_K]

In this case, Nick has the answer - basically create via import and it will match up after you enable sync. Don't enable sync until after the user is created. It's not a solution, just a work around that does make some manual work.

Thanks @SweetAction
But the objective of M365 sync is to have something automated
Here each time we add a new M365 user, it's create automatically a 3CX extension for it, and then I'll have to manually do things on the 3CX side to configure the extension.
So M365 user sync to 3CX looses a lot of value since there are no templates to be used automatically.

 

[Evolute IT]

Thanks @accentlogic but I can't vote on the idea, I get this message :

View attachment 26073

The voting is the small green button with a number in it, above that. Usually below the OP.