Cisco Device Migration to Asterisk at Scale
•Download as PPTX, PDF•
1 like•200 views
The document summarizes Target's migration of their phone system from Cisco Call Manager (CUCM) to an open source Asterisk platform. The migration involved moving over 15 phone models and multiple voice gateway models from CUCM to Asterisk while minimizing disruption. A team of Cisco experts helped automate the migration using custom tooling to remotely survey sites and migrate endpoints with a single button click, provisioning the new system and rebooting phones remotely. While some older phone models took longer to reboot, the migration was successful and allowed Target to teach their "relic" phones new open source tricks completely remotely.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cisco Device Migration to Asterisk at Scale
Similar to Cisco Device Migration to Asterisk at Scale (20)
Recently uploaded
Recently uploaded (20)
Cisco Device Migration to Asterisk at Scale
- 1. © 2020 Target Corporation The Great Migration Cisco Device Migration To Asterisk at Scale Jason Park Lead Engineer Target Voice Engineering October 22, 2020
- 2. © 2020 Target Corporation Target Voice Engineering Introduction 1 Jason Park • Asterisk since 2003 • dCAP in 2011 • Kamailio / OpenSips / FreeSwitch • Open source since 1995 • Missouri born, living in Minnesota • Target since May 2018 jason.park@target.com @jrpark
- 3. © 2020 Target Corporation Target Voice Engineering Agenda 2 • The Quest – The Mission • The Relics – The Endpoints • The Old Ways – How We Use To Do It • The Heroes – The Team • The Way of the Wizards – The New Way • The Magic – Migration Tooling • The Magic – Provisioning ”Bridge” • The Treasures and Tribulations – The Takeaways • Court – Q&A
- 4. © 2020 Target Corporation Target Voice Engineering The Quest 3 Requirements and Goals • Migrate from CUCM to the new Hydra open source platform • Asterisk • Kamailio • Radically decentralized • Feature removal • Minimize impact to Target guests and team members • Reuse Cisco endpoints when possible • No truck rolls • Automate as much as possible • Tame the Hydra
- 5. © 2020 Target Corporation Target Voice Engineering The Relics 4 Cisco Endpoints • 15 Phone Models • Multiple VG Models • Model difference challenges • Provisioning challenges
- 6. © 2020 Target Corporation Target Voice Engineering The Old Ways 5 How would we have done this 2 years ago? Physical Site Survey Document Endpoints From CUCM Apply Business Rules To Docs Configure in New System Remote Engineers Backend Onsite Technicians DHCP Team After Hours Reboot Phones Monitor Firmware Flashing Monitor Re-Reg Complete Backend Work
- 7. © 2020 Target Corporation Target Voice Engineering The Heroes 6 • Who do you find to do hundreds of after-hours cuts to a new open source based platform? • Asterisk experts? • Kamailio experts? • Analysts? • Technicians? • ? • Cisco subject matter experts! The Team
- 8. © 2020 Target Corporation Target Voice Engineering The Way of the Wizards 7 • Migration tooling for automation • Remote site surveys using the tooling and our business rules • Needed changes made before cutover on the CUCM side • DHCP changed weeks prior to cutover • Remote engineers perform cutover How We Are Doing It Today
- 9. © 2020 Target Corporation Target Voice Engineering The Magic 8 • Web-based migration tool built in to our management interface • Cisco data integration with their AXL script API • Remote site surveys using the API and our business rules • Remote engineers perform cutover by clicking the button: Gather fresh data from Cisco, insert in to the new platform, reboot the phones and monitor the results. Migration Tooling The Big Red Button
- 10. © 2020 Target Corporation Target Voice Engineering The Magic 9 • Support for new device standard and our Cisco “relics” • Multiple Protocols • DHCP Tags • Dynamic mapping of older protocols • ”Proxy” before the cutover • Cutover the provisioning when the store gets cutover Provisioning ”Bridge”
- 11. © 2020 Target Corporation Target Voice Engineering The Treasures and Tribulations 10 • Some of the relics can take 20 minutes to flash and reboot • Some relics may use an entirely different configuration scheme • This can be done completely remotely and still provide a great experience for the end user • You can teach old dogs new tricks Did we learn anything?
- 12. © 2020 Target Corporation Target Voice Engineering Court – Q&A 11 Jason Park, Lead Engineer, Target Voice Engineering jason.park@target.com – @jrpark
Editor's Notes
- Short bio
- Explain project name
- Lots of models, lots of problems
- BUSY slide, on purpose, go through quick and harp the complexity and number of steps Physical site survey by a vendor Document all of the endpoints and configuration out of CUCM Apply business rule logic and make changes in the documentation as needed Configure all of the documented devices in the new system Remote engineers performing the backend cutover Onsite vendor technicians checking the status of the cutover Another team performing a DHCP change after hours Reboot phones remotely or onsite Monitor phone software flashes Monitor phone registrations to new system Complete backend work
- How did we end up with a group of Cisco SMEs doing cuts?
- Today’s simpler process
- The big red button
- I don’t like have a bunch of static configuration files for thousands of endpoints laying around. Different protocols, proxy, dhcp tag differences.
- Positives, negatives, learnings