Jump to content

Recommended Posts

Posted
Many of our clients use our routers.  Our routers do have DHCP Options.  
The polycom ZTP and Yealink RDS have sometimes failed me when I am doing a roll out.
I would like the onsite router to tell the phone where to go.
I have never been able to get this to work with http://p3.zswitch.net/  
I know that 2600hz uses http instead of ftp.  I am lost.

We use Polycom and Yealink.
twith http://p3.zswitch.net/  
Posted
"Yealink RDS have sometimes failed me when I am doing a roll out"

In my experience, if you are using the RDS service, the phone will get redirected correctly during initial provisioning, however, the 2600hz provisioning server does not configure the "provisioning server" field when it sends the configuration to the phone the first time.  When the phone reboots it will not get a new or updated configuration.

Perhaps, we should open a JIRA ticket on this.  I suspect we want this field set during initial provisioning.  I can't think of a reason why leaving this out is intentional.
Posted
Hey Logicwrath, try it again. A couple months ago they changed the way the provisioner works on a base level. I've been successfully using RPS ever since. If it still doesn't work go into ADV Provisioner, hit the gear and then hit "unlock". 
  • Administrators
Posted
Hi there,
     I wanted to follow up on this. The new provisioner server will block your IP address for 15 minutes if you attempt to provision a bunch of phones that aren't in the database yet. It's a necessary security feature unfortunately.

      If you set Option 66 it may actually be "working" but if you plug the phones in BEFORE you have configured them in the GUI, they will all try to phone home to p3.zswitch.net at the same time. If the config files aren't there and it 404s, the security system will count the failures. If the failures exceed a certain amount, it will block your IP. This is done to prevent MAC address brute force scanning.

      I am wondering if the actual issue here is that you're setting option 66, then plugging in a bunch of phones, then trying to configure them one by one after they're already plugged in. If you are, I would bet this is the issue.
  • Administrators
Posted
Hi there,
     I wanted to follow up on this. The new provisioner server will block your IP address for 15 minutes if you attempt to provision a bunch of phones that aren't in the database yet. It's a necessary security feature unfortunately.

      If you set Option 66 it may actually be "working" but if you plug the phones in BEFORE you have configured them in the GUI, they will all try to phone home to p3.zswitch.net at the same time. If the config files aren't there and it 404s, the security system will count the failures. If the failures exceed a certain amount, it will block your IP. This is done to prevent MAC address brute force scanning.

      I am wondering if the actual issue here is that you're setting option 66, then plugging in a bunch of phones, then trying to configure them one by one after they're already plugged in. If you are, I would bet this is the issue.
  • 3 weeks later...
Guest CBV David
Posted
Thanks for this info!  Definitely helpful to be aware of this sort of thing. :-) 
Guest CBV David
Posted
Thanks for this info!  Definitely helpful to be aware of this sort of thing. :-)

... whoa.  Just had the strangest sense of déjà vu. ;-)
×
×
  • Create New...