You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In EPM Extension Mapping, adding a new extension without the MAC address defaults that extension to be configured by Phone.
I would think that later adding the MAC address would update the extension to be configured by Server. However, that does not happen. Save/Apply does not change the configured by option, and onboarding a phone, inputting the global config password, selecting an extension, and bringing up the phone does not update the setting either. The only way to change this that I've found is to export the CSV file in Bulk Handler and change the column field(s) there and then import that.
P.S. - Removing the MAC address later automatically changes the configured by setting from Server to Phone; however, again, adding the MAC address later does not automatically change the configured by setting from Phone to Server, either on applying changes to the PBX interface or onboarding a phone.
FreePBX Version
FreePBX 17
Issue Description
In EPM Extension Mapping, adding a new extension without the MAC address defaults that extension to be configured by Phone.
I would think that later adding the MAC address would update the extension to be configured by Server. However, that does not happen. Save/Apply does not change the configured by option, and onboarding a phone, inputting the global config password, selecting an extension, and bringing up the phone does not update the setting either. The only way to change this that I've found is to export the CSV file in Bulk Handler and change the column field(s) there and then import that.
P.S. - Removing the MAC address later automatically changes the configured by setting from Server to Phone; however, again, adding the MAC address later does not automatically change the configured by setting from Phone to Server, either on applying changes to the PBX interface or onboarding a phone.
Operating Environment
Relevant log output
No response
The text was updated successfully, but these errors were encountered: