VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.
-
Upload
rolf-morgan -
Category
Documents
-
view
221 -
download
4
Transcript of VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.
![Page 1: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/1.jpg)
VoIP: Full Lifecycle Management
Russell M. ElsnerAPM Technology DirectorOPNET Technologies, Inc.
![Page 2: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/2.jpg)
Agenda
• Motivation• Components of the VoIP life cycle
– Pre-deployment– End-user experience monitoring– Continuous optimization
• Benefits of an end-to-end approach• Conclusion
![Page 3: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/3.jpg)
Motivation
• The wide acceptance of VoIP leads to the false hope that VoIP is “just another application”
• However, most VoIP deployments fail initially– New challenges managing data and voice on same network– Requires careful planning of capacity, QoS, etc.
• Additional challenges in maintaining adequate voice service quality as additional applications are deployed over same network infrastructure
• Performance problems will occur sooner or later– Can be network, server or application related– Need for problem detection and root cause analysis solutions
![Page 4: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/4.jpg)
Challenges
• Before deployment– Is my network ready for VoIP?– How do I configure my network to accommodate VoIP?
• After deployment– Is my VoIP service delivering adequate call quality?– What is the root cause of a performance problem?– How do I resolve the problem?– How do I guarantee performance is maintained as new
users and applications are added to the network?
![Page 5: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/5.jpg)
VOIP Life Cycle
Continuously reengineer andoptimize the network• Add additional capacity or QoS to resolve
performance issues• Tune queues based on measure data and VOIP
volumes • Trend VOIP and data traffic to predict future
capacity bottlenecks
• Test configuration changes prior to deployment in virtual network environment
Baseline data traffic• Baseline data traffic for pre-deployment
planning and post-deployment evaluation
Perform VoIP readiness assessment• Build network model with baseline data traffic • Add VOIP traffic (projected call volumes) • Predict MOS or R-Factor and impact on
data traffic • Add capacity or QoS, if required • Predict behavior under failure scenarios
Tra
ffic
dat
a
1. Pre-DeploymentPlanning & Assessment
2. Ongoing Operations
3. Optimization
Monitor and troubleshoot VoIP traffic• Track call quality of VoIP traffic• Evaluate how data traffic is affected• Troubleshoot performance problems with drill-
down into specific calls• Compare current network load with forecast
![Page 6: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/6.jpg)
VOIP Life Cycle
Continuously reengineer andoptimize the network• Add additional capacity or QoS to resolve
performance issues• Tune queues based on measure data and VOIP
volumes • Trend VOIP and data traffic to predict future
capacity bottlenecks
• Test configuration changes prior to deployment in virtual network environment
Baseline data traffic• Baseline data traffic for pre-deployment
planning and post-deployment evaluation
Perform VoIP readiness assessment• Build network model with baseline data traffic • Add VOIP traffic (projected call volumes) • Predict MOS or R-Factor and impact on
data traffic • Add capacity or QoS, if required • Predict behavior under failure scenarios
Tra
ffic
dat
a
1. Pre-DeploymentPlanning & Assessment
2. Ongoing Operations
3. Optimization
Monitor and troubleshoot VoIP traffic• Track call quality of VoIP traffic• Evaluate how data traffic is affected• Troubleshoot performance problems with drill-
down into specific calls• Compare current network load with forecast
![Page 7: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/7.jpg)
Pre-deployment
• What is in my network today?– Identify devices and configurations– Baseline applications and traffic– Overlay traffic on network topology
• Impact of adding a new technology or application such as VoIP?– Testing in lab environment– Pilot projects and emulation on production network– Network simulation in virtual network environment
![Page 8: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/8.jpg)
What is in my network today?
Step 1: Build a topological view of the network based on device configuration data
![Page 9: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/9.jpg)
What is in my network today?
Step 2: Collect application traffic data
![Page 10: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/10.jpg)
What is in my network today?
Step 3: Overlay traffic on network topology
![Page 11: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/11.jpg)
Pre-deploymentPlanning
• Lab testing: needed but not able to replicate scale of full deployment
• Pilot projects or emulation on production network should be handled with care not to break existing operations
• Simulation in a virtual network environment is able to reproduce full scale deployment without affecting the production network
![Page 12: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/12.jpg)
VoIP Planning
• Assess the impact of VoIP on existing network and data• Predict bandwidth and performance (MOS, R-Factor) impact• Generate design recommendations w.r.t. capacity, QoS, etc.
![Page 13: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/13.jpg)
VOIP Life Cycle
Continuously reengineer andoptimize the network• Add additional capacity or QoS to resolve
performance issues• Tune queues based on measure data and VOIP
volumes • Trend VOIP and data traffic to predict future
capacity bottlenecks
• Test configuration changes prior to deployment in virtual network environment
Baseline data traffic• Baseline data traffic for pre-deployment
planning and post-deployment evaluation
Perform VoIP readiness assessment• Build network model with baseline data traffic• Add VOIP traffic (projected call volumes) • Predict MOS or R-Factor and impact on
data traffic • Add capacity or QoS, if required • Predict behavior under failure scenarios
Tra
ffic
dat
a
1. Pre-DeploymentPlanning & Assessment
2. Ongoing Operations
3. Optimization
Monitor and troubleshoot VoIP traffic• Track call quality of VoIP traffic• Evaluate how data traffic is affected• Troubleshoot performance problems with drill-
down into specific calls• Compare current network load with forecast
![Page 14: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/14.jpg)
Ongoing Operations• Monitor and troubleshoot poor call quality from the end-user’s
perspective– Monitor the interaction of both data and VoIP running on the same network– Monitor real-calls with passive speech quality analysis
• Receive automatic alerts based on low MOS scores• Easily identify the root-cause of poor call quality before it affects the
business
![Page 15: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/15.jpg)
VOIP Life Cycle
Continuously reengineer andoptimize the network• Add additional capacity or QoS to resolve
performance issues• Tune queues based on measure data and VOIP
volumes • Trend VOIP and data traffic to predict future
capacity bottlenecks
• Test configuration changes prior to deployment in virtual network environment
Baseline data traffic• Baseline data traffic for pre-deployment
planning and post-deployment evaluation
Perform VoIP readiness assessment• Build network model with baseline data traffic • Add VOIP traffic (projected call volumes) • Predict MOS or R-Factor and impact on
data traffic • Add capacity or QoS, if required • Predict behavior under failure scenarios
Tra
ffic
dat
a
1. Pre-DeploymentPlanning & Assessment
2. Ongoing Operations
3. Optimization
Monitor and troubleshoot VoIP traffic• Track call quality of VoIP traffic• Evaluate how data traffic is affected• Troubleshoot performance problems with drill-
down into specific calls• Compare current network load with forecast
![Page 16: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/16.jpg)
ContinuousOptimization
• Growth and change affect network and application performance
• Need to be planned for in advance– Assess the impact of adding new VoIP
users, perform redesign to add new branch offices, etc.
– Optimize network capacity and QoS configurations as VoIP and other traffic growth in your network
– Validate configuration changes prior to deployment to identify security gaps and minimize the risk of downtime
![Page 17: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/17.jpg)
Benefits of anEnd-to-End Approach
Address different parts of the life cycle with a common toolset:– Accelerate VoIP deployments by accurate pre-
deployment planning– Optimize the end-user experience– Rapidly move from problem detection to root cause
analysis and problem resolution– Minimize errors by ensuring all decision making is based
on common and up-to-date network data
![Page 18: VoIP: Full Lifecycle Management Russell M. Elsner APM Technology Director OPNET Technologies, Inc.](https://reader036.fdocuments.us/reader036/viewer/2022062421/56649cf05503460f949bef20/html5/thumbnails/18.jpg)
Conclusion• Before you roll out VoIP, make sure that
– You understand the current network configuration– You baseline existing application traffic– You have adequate network capacity– You define the call quality that meets your user’s expectation
• After you have rolled out VoIP, make sure that– You monitor and troubleshoot call traffic and end-user experience– You leverage traffic measurements for adequate planning and QoS– You continuously reengineer the network for growth and change– You validate changes before deployment
• Use a full life cycle approach to guarantee network and application performance before, during, and after deployment