Removing a phone from an extension system thinks it is still attached to extension

Discussion in '3CX Phone System - General' started by deka, Aug 31, 2016.

Thread Status:
Not open for further replies.
  1. deka

    Joined:
    May 10, 2016
    Messages:
    7
    Likes Received:
    0
    Removing a phone from a user, returning phone to factory default. Phone can can not be re-provisioned to existing user or provisioned to a new user. We receive an error: This MAC belongs to another phone on this extension

    This error occurs even if we try to provision the phone to another extension. 9Other than the one we removed it from originally.)
     
  2. schut

    Joined:
    Jul 30, 2012
    Messages:
    20
    Likes Received:
    0
    Just remove it from the extension you previously assigned it to will fix this. You can do this by editing that extension under Phone Provisioning. Remove MAC-address and set phone-type to None.
     
  3. deka

    Joined:
    May 10, 2016
    Messages:
    7
    Likes Received:
    0
    We have removed it from the extension. However, the system continues to think it is assigned to the user. (Even though it does not show up as assigned to the user.) When we try to re provision it, we receive the error stating it belongs to another extension.)

    To add additional information. This seems to occur when trying to use a custom template to provision the phone. If, we accept the default template from 3CX we do not receive the error and the phone provisions.

    Update: using the default template does allow the phone to be re-provisioned. However, if you remove the phone from the extension. It still shows on the phone tab allocated to the users extension. (In addition it shows as New in the phone tab.) There is no way to manage the phone after you have removed it from an extension except to use the phones Gui interface and reset it to factory default. (The crux of the matter is; the system is still not allowing custom templates to be used effectively.)

    It almost seems like there is an issue with the underlying database and changes/updates.
     
Thread Status:
Not open for further replies.