Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Provisioning Q and A

8,773 views

Published on

This is the Provisioning Q&A presentation.

Published in: Technology, Business
  • Login to see the comments

Provisioning Q and A

  1. 1. Powerful, Distributed, API CommunicationsCall-in Number: 805-309-5900 Pin 705-705-141Expert Q&A: Provisioning EditionMay 17th, 2013
  2. 2. Welcome
  3. 3. Our PanelistsJoshua GoldbardMarketing Ninja, 2600hz,ModeratorDarren SchreiberFounder, 2600hzFrancis GenetProvisioning Engineer,2600hzAndrew NagyProvisioning Guru,Provisioner.net
  4. 4. Provisioning:Y U NO NAMETHINGSCONSISTENTLY?
  5. 5. Some background…
  6. 6. What is Provisioning?• As old as time.• Telecom Term used to dole out access• We’re focused on Handset provisioning• Goal is to eradicate manual labor• Why is this important?• Cisco devices can take 2.1 hours per device toinstall (according to Cisco)
  7. 7. Provisioning is hard• Handsets change over time• Some support only certain features or methods• Example, TFTP only on Polycom 3.0 Firmware (HTTP isweird on 3.0), HTTP/TFTP on 4.0 and beyond• Secure phones are even harder• Checksum Firmware• Weird authentication patterns (see Ang Cui’s video)• Lots of pings
  8. 8. Note to Karl: THIS SUCKS
  9. 9. Provisioning is Political• Some firmwares are only supported in certain countries• Based on encryption standards / languages / etc.• Some companies hide their older firmwares• Sometimes you need the older firmware!• Some firmware is actually broken!• We have multiple Aastra firmwares that don’t work• Nobody will tell you any of this!• Broken to one person is not broken to another
  10. 10. Provisioning Lifecycle1. Phone arrives brand new from factory2. Phone has Provisioning URL added to the on-Device GUI3. Provisioning server creates a provisioning profile for the handsetcontaining all of the configuration files (MAC Address used foridentification)4. The Phone is attached to the corporate network and attempts toconnect to the provisioning URL in the GUI5. The provisioning server recognizes the MAC ID of the handset and sendsthe corresponding configuration files after authenticating the phone6. The phone receives the firmware and/or Configuration files and if this is asecure environment, performs a checksum on the configuration files tomake sure they match7. If everything is Kosher, the phone will begin the update process. Oncecomplete it will enter service.8. Every few minutes (days) or when the phone powers on, it will repeatthis process starting at step 4.Every Phone will ping every 3-10 minutesNetwork has to handle these requests
  11. 11. Let’s Get Technical!
  12. 12. Trouble With Provisioning• Handset Manufacturers think they ownProvisioning• Variation in Provisioning methods on differentfirmware versions• Hard to build for the general case
  13. 13. Trouble with Provisioning:Inconsistency
  14. 14. Every Handset Requests theConfiguration Differently• Yealink• All info in the User Agent• Polycom• By default, no phone identification• Can enable info in User Agent but has to be turned on• Some phones do XML and some even do arbitrary text fils
  15. 15. Codecs• Some phones have different toggles for Codecs• Yealink requires you to put a 1 to activate Codecs• Cisco requires you to put the name• SNOM requires you to build a listCONSISTENCY? NAH.
  16. 16. YealinkCiscoY U NO USECONSISTENCY?SNOMCodecs
  17. 17. Cisco (Timezones in GMT Time)Polycom (Timezones in Seconds)Y U NO USECONSISTENCY?Timezones
  18. 18. Yealink
  19. 19. Polycom
  20. 20. Now for the Painful Part• There is no workaround• To make provisioning work for your customers, you have todo a lot of leg work• Anticipate which handsets clients will want• Test, test and test some moreConcealing Complexity is of paramount concernEasy becomes unmanageable over time
  21. 21. Yeah it really is that BadBut maybe we can do something about it…
  22. 22. Oh by the way… The hardestpart about provisioning?THE USER
  23. 23. Users, Resellers, etc.• “I don’t like this ringtone”• “Why do I have to push two buttons when my oldsystem only required one to intercom?”• “I want two line keys, one for my private calls and onefor support”• “My MWI makes noise when it goes off, make it stop”• “I want the logo changed for my customers”• Oh, and implied:• I DON’T WANT TO TOUCH ANYTHING TO DOTHIS
  24. 24. Simplicity is Prerequisite forReliability -Edsger W. Dijkstra
  25. 25. Designing a Simple Provisioner• Anticipate Client Demands• If a phone doesn’t support HTTP, users should be notified• Use known good firmware/config files• Don’t get fancy• It is not possible to standardize provisioning settings acrosshandsets• The best that can be done is to conceal this complexityfrom the consumers of the serviceFinal Detail: It has to work every time
  26. 26. One last detail:Getting the URL into the phone• Two ways of doing it: DHCP66 or Manually• DHCP option 66• Router service for including Provisioning URL in header• Great for local installs and fast provisioning on a single site• Manual• Going into the GUI and manually entering the ProvisioningURL• Can often pay distributors a small fee to pre-load URL
  27. 27. Our Experience Installing Usingour Provisioner• 140 Phones on one campus, <4 hours• 30 Phones in a small office, <1 hour• Demo provisioning live for clients• Really powerful demo for resellers• Multi-site installs >1000 phones, <1 DayCompare to Cisco @ 2.1 hours per handset (Source AberdeenStudy, 2011 TCO)
  28. 28. Lessons from the front lines• Timing Settings on Handsets• Codec Issues?• Worst Manufacturer? Best?• Provisioning things other than handsets (modems,ATAs, Conference Phones)
  29. 29. Let’s take some time to pontificate aboutprovisioning at scale…The Tsunami of Pings
  30. 30. • Provisioning is hard because ofzero standardization in theindustry• Best solution is to hidecomplexity from your clients• We did a lot of leg work so youdon’t have to; use our provisionerRecap
  31. 31. QUESTIONS???

×