Jump to content

Recommended Posts

Posted
Note: Kazoo Only. We have not migrated our customers on Monster yet.
Provisioning server: prv.zswitch.net

Here are the steps that we took:

1)  Factory reset the phone 
2)  Set it up to prv.zswitch.net tag SN to UA enabled 
3)  Saved configuration then the phone restarts when it connects it would say "updating initial configuration"
4) Waited a minute or two, phone comes back and it says "could not contact boot server"
5) Then the phone will come back up and its a flashing time and date.
6)When we tried to log in to the web interface it says "sorry connection refused"
7) If you factory default the phone again, you can get back to the web interface 
    and when we manually provisioned it the phones will come back again.

We have tested this on both IP 450's and 550's and at this point we are seeing that Auto Provisioning is failing. 

Anyone here experienced the same issue?
Posted
Joy, The server type is set to http too, right?

Also, from the same public IP as the phones, do the provisioner optios still show on the device (KAzoo ui, device)
If not, your IP may be blocked by 2600hz

MD
Posted
Michael,

We have two internet connection that we tried that on and it failed on both.
But on the third connection we tried to do what you just mentioned and it auto-provisioned.

Thanks for that info we are not aware of the IP being blocked by 2600 at all until now.

And so, how can we prevent our IP's from being blocked by 2600hz?
Posted
From what I understand, if there are too many requests to the provisioning server from non phones/scans, you'll get blocked
I open a case and give them a heads up if I think there is an issue
Posted
Also,
could it simply be that on the other internet connections there was a firewall blocking the provisioner?

"In addition, the client should allow access to our web and API servers on:
80 TCP
443 TCP
8000 TCP
8443 TCP"
×
×
  • Create New...