Migrating from a Cloud Phone Provider to SoundCurve

migrating from a cloud phone provider to soundcurve
portfolio main img

Customer: Belville, Basore and Fitzpatrick Law

Prepared: 1/19/2017

Requirements

  • Increase telecom system availability to 99.9% on an annualized basis
  • Discontinue large machinery/equipment capital expenditures and replace with lower cost, expense based model
  • Reduce monthly phone bill expense by a minimum of 20%
  • Implement offsite, encrypted, nightly back-ups
  • Reduce labor required for IP Phone deployment and configuration changes

Total Hours Labor: 285

solutions
product solution

Proposed Solutions

  1. Migrate on-premise PBX to cloud based PBX. Goals addressed:
    • Increase telecom system availability to 99.9% on an annualized basis
    • Discontinue large machinery/equipment capital expenditures and replace with lower cost, expense based model
    • Reduce monthly telecom costs by a minimum of 20%
  2. Procure new SIP trunk provider
    • Increase telecom system availability to 99.9% on an annualized basis
    • Reduce monthly telecom costs by a minimum of 20%
  3. Implement Backup/Disaster Recovery protocols
    • Increase telecom system availability to 99.9% on an annualized basis
    • Implement offsite, encrypted, nightly back-ups
  4. Implement Cloud based IP Phone configuration manager
    • Reduce labor required for IP Phone deployment

Scope Estimate

  1. Migrate on-premise PBX to cloud based PBX: 103 hours
    • Development: 80 hours
    • Testing: 20 hours
    • Level 1 training: 2 hours
    • Set up Pingdom uptime monitoring: 1 hour
  2. Procure new SIP Trunk provider: 56 hours
    • Outbound traffic production burn-in/testing: 4 hours
    • Inbound traffic production burn-in/testing: 12 hours
    • DID migration: 40 hours
  3. Implement Backup/Disaster Recovery Protocols: 112 hours
    • Develop scripts for key file backup to Amazon S3 Cloud storage instance: 60 hours
    • Develop recovery scripts: 20 hours
    • Deploy new configurations to IP Phones: 2 hours
    • Backup/restore testing: 30 hours
  4. Implement Cloud based IP Phone configuration manager: 14 hours
    • Create configuration templates for each phone model: 2 hours
    • Create configurations for each IP Phone: 8 hours
    • Deploy cloud FTP instance: 2 hours
    • Migrate and Test IP Phones: 2 hours
results ver2
table for implementation

Implementation

Project duration: 65 business days
Total Labor Hours: 265

Project Execution Timeline

project execution timeline
pingdom result

Results

99.91%

Telecom system availability increased to 99.91%

1 Minute

Support Contacts are automatically notified by text message within 1 min of a server outage.

$4,400

capital expenditure for equipment upgrade avoided and replaced with $147.86/mo cloud server/storage expenses

32%

SIP Trunk phone bill reduced from ~$3,800/mo to $2,581/mo, a 32% reduction

5 minutes

IP Phone deployment time reduced from 3 person interaction to 1 person, ~20 min to 5 min. Update time reduced to ~5 min from 15 min

Related Blog Articles