<aside> 💡 NOTE: This documentation refers to the Monster UI implementation

</aside>

Overview: About Phone "Locking"

Attacks on VoIP phone networks have steadily increased in recent years.  Hacking efforts such as scanning, brute-force hacking, or attempts to steal SIP credentials or make fraudulent calls can be disruptive at a minimum  and/or -- worse -- breach your company's private data.

To ensure a phone with a 2600Hz provided phone number is initially secure when first provisioned and remains secure while it is part of your account,  our Provisioner application monitors IP activity to/from the phone and sets protection mechanisms to keep them safe.  If Provisioner encounters one of triggers outlined below,  it will automatically "lock" the phone -- meaning it will block the phone from provisioning and it will no longer be connected.

Events that can trigger a phone to lock

Provisioner will automatically lock a phone if it encounters any of the behavior outlined below:

When first provisioning phones

• When you successfully provision a phone for the first time (from a factory reset state) and you move it to a different network where its IP address will change.
• If you have created a device in KAZOO (either in SmartPBX or Callflows) more than 1 week before you provision it, the phone will be locked out. This means if you have a phone you want to send to your customer and create it as a device in KAZOO before you ship it, you will need to follow the unlock procedures when they receive it.

Once your phone is provisioned, if

• You move a phone from your office desk to your home environment, or anywhere that the WAN IP address is not the same as your existing location.
• Within your account, a phone has been blocked by 2600Hz security system due to suspicious activity.
• Your phone is not a new phone but was registered in your account.