Once seen never forgotten!

Discussion in '3CX Phone System - General' started by ccomley, Feb 7, 2016.

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

    Joined:
    Apr 6, 2011
    Messages:
    92
    Likes Received:
    4
    I often plug customer's phones in in the office before shipping them, e.g. to make sure they're on the latest firmware, install EHS modules etc.

    Of course, as soon as they boot they shout out their existance and 3CX promptly adds them to the "Phones you can configure" list.

    So far as I can see - am I missing a trick? - there's no way to either remove a specific unallocated phone from that list or to remove *all* unallocated phones from the list.

    Anyone know better??

    I have phones "waiting to be allocated" which have been shipped to customer sites *years* ago!!
     
  2. aberry

    aberry New Member

    Joined:
    Jan 13, 2015
    Messages:
    118
    Likes Received:
    7
    You should be able to use the 'Reject' key to remove them from the list. If rebooted, they will appear on the list again.
     
  3. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    "Reject" works fine. I made the experience, that you have to edit your security settings afterwards and remove the rule, which blocks the IP.
     
  4. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,283
    Likes Received:
    68
    The 'reject' button doesn't add anything to the IP Blacklist.
     
  5. JonnyM

    Joined:
    May 17, 2010
    Messages:
    79
    Likes Received:
    5
    Create a subnet separate from the one 3CX runs on with access out to the internet and in from the subnet your PC is on, and use that to test phones.
     
  6. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    @Nick: Thanks you for correcting me. We had an issue with one phone and I rejected it and deleted a blocking rule. But this rule got created because of a login attempt with a wrong password. So I mixed things up.
     
Thread Status:
Not open for further replies.