26.09.2012 Views

Triple-Play Service Deployment

Triple-Play Service Deployment

Triple-Play Service Deployment

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8: Troubleshooting VoIP<br />

Common Causes<br />

• Network Congestion<br />

• Buffer overruns in network components<br />

• Priority queuing and traffic shaping problems<br />

Packet Delay – end-to-end network latency<br />

• Customer experience – over talk and echo, contributor to jitter buffer discarded packets<br />

Common Causes<br />

• Priority queuing and traffic shaping problems (CoS/QoS)<br />

• Choice of CODEC selection (packetization, buffering, compression)<br />

• Network congestion<br />

Packet Jitter - variation of arrival time between packets.<br />

• Customer Experience - Clicking/popping noise to the end user, garbled speech.<br />

Common causes<br />

• Variation in network traffic levels<br />

• Priority queuing and traffic shaping problems in combined VoIP / data networks<br />

• Best Test – direct measurement of Jitter<br />

Isolating VoIP problems<br />

The following steps detail some of the ways that service providers<br />

might respond to a customer’s complaint that a phone does not<br />

work. The first step is to determine if the problem is in the network,<br />

a provisioning issue, CPE related issue, or a customer issue. To<br />

accomplish this task, the technician must perform an IP phone<br />

emulation test. The next step is to attempt registration of the test<br />

device with the gatekeeper/proxy server. The test set conducts<br />

signaling decodes and displays signaling error messages. It proves<br />

connectivity to the gatekeeper/proxy server and verifies<br />

provisioning of the customer’s unique alias.The technician also uses<br />

the device to place test calls on and off the network.<br />

Another set of tests verifies the IP phone’s connectivity. A ping test<br />

suite can help determine if a registration problem exists. The test<br />

pings the gatekeeper/proxy server IP address. If off-net calls fail,<br />

gateway provisioning may be causing the trouble or there may be a<br />

connectivity issue. The latter can be identified by pinging the<br />

gateway device’s IP address. A trace route test suite is performed if<br />

the ping test fails with the gateway or gatekeeper/proxy server. The<br />

trace route helps isolate path/device connectivity problems.<br />

217

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!