Вы находитесь на странице: 1из 9

SIP Troubleshooting for Cisco Collaboration LAB

Part 1: Lab Information


Lab objectives
• Explore SIP configuration.
• Practice SIP troubleshooting tools and methodology.
• Get hands-on experience with SIP traces and debugs.
• Find information in debugs.
• Explore various SIP messages and call flows.

Lab Description
In this lab, you will configure SIP user agents such as a Softphone, Cisco SBC
(CUBE) and CUCM.

These SIP user agents will be configured to work with each other and
communicate with the ITSP.

Your task will be to troubleshoot, understand and configure the SIP user
agents to work in different scenarios.

Lab Notes
This lab exercise is built on top of each other, so that each task has to be
completed in order to attempt the next task.

The whole lab is based on free software and temporary licenses, which I’ll
show you how to get.

We will be using the free PC version of VMware Player hypervisor for the
virtualization layer.
In case you have an ESXi server with the appropriate resources, don’t
hesitate to use it, fully or partially.

If you are going to use your PC to run the VM’s, do note that you’ll have a
VM with another IP address on your computer, and it might trigger some PC
Firewalls. Keep that in mind when you’re troubleshooting (depending on your
PC FW, you might have to create some rules or turn it off).
Lab Topology
The lab will be based on vCUBE and CUCM that can be installed on your PC or
a lab environment in case you don’t have enough resources to run both.

As long as you have IP connectivity, you can easily split the VM’s on two
hypervisors.

Virtualization Resources
Hypervisor- VMware player

vCUBE – CSR1000v. vCPU – 1 / RAM – 4GB / Storage – 8GB

CUCM – v10.x and above. vCPU – 1 / RAM – 4GB / Storage – 80GB

*You can oversubscribe vCPU and RAM resources and use ‘thin provisioning’
on CUCM’s storage but actual performance will depend on your PC.

Lab Assessment
Since this is a practical troubleshooting course, a certificate will be given for
demonstrating advanced troubleshooting skills in real-life simulated
scenarios.

Your lab performance is assessed using a form, answers to which you’ll be


able to find when completing the tasks in the lab.
You can fill the answers during or after you finish the lab.

The passing score is 80%. A certificate will be sent automatically upon


completion.

Enter the assessment here. You may repeat it several times.


Part 2: Lab Setup & Tasks
Lab Setup
• Download & install VMware player.
• Download & install CUCM & ova files on VMware player.
You can use this guide to create a bootable ISO.
• Download & install CSR1000v ISO on VMware player.
• Sign up for a free account with iptel.org (our ITSP) and get yourself a
username, password and an associated number (Alias) for incoming calls.
• Please verify that your alias can be used in ‘to’ and ‘from’ uri as such:

• Download and install MicroSIP

CUBE Setup
Basic Network setup

• Give your CUBE a name


hostname vCUBE
• Configure your LAN Gig interface with a Static IP Address and add a
default route.
• Configure DNS
IP name-server 8.8.8.8 8.8.4.4

CUBE setup

• Add CUBE capabilities


voice service voip
mode border-element license capacity 100
allow-connections sip to sip
sip
call-route url (*for name dialing routing)
Call routing

• Incoming calls from CUCM

voice class codec 1


codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8

voice class uri 1 sip


host ipv4:cucm-ip-address

dial-peer voice 1 voip


description incoming calls from CUCM
session protocol sipv2
incoming uri via 1
voice-class codec 1
dtmf-relay sip-kpml

• Incoming calls from ITSP

dial-peer voice 2 voip


description incoming calls from ITSP
session protocol sipv2
incoming called-number your-itsp-alias-number
voice-class codec 1
dtmf-relay sip-kpml

• Outgoing calls to CUCM

dial-peer voice 3 voip


session protocol sipv2
session target ipv4: cucm-ip-address
destination-pattern your-itsp-alias-number
voice-class codec 1
dtmf-relay sip-kpml
• Outgoing calls to ITSP

voice class uri 2 sip


host dns:iptel.org (*for name dialing routing)

dial-peer voice 4 voip


session protocol sipv2
session target sip-server
destination uri 2
voice-class codec 1
dtmf-relay sip-kpml

sip-ua
sip-server dns:iptel.org

CUCM Config

• Add a SIP trunk towards CUBE. Use:


Task 1
Register MicroSIP Client

1. Create a new SIP Phone Security Profile to enable SIP Digest


Authentication.
Copy Third-party SIP Device Advanced - Standard SIP Non-Secure Profile
And mark the Enable Digest Authentication Checkbox.
2. Add a new phone (Third-Party SIP Device – Advanced)
3. Add a new user named ‘MicroSIP’ to use for Digest Auth.
4. Register the MicroSIP Client to CUCM.

*TS Note: Use SIP logs to properly place Digest username and extension.

Task 2
Register CUBE to the ITSP.

Use the command:


sip-ua
registrar dns:iptel.org

sip-ua
credentials username your-itsp-user password your-itsp-password realm
sip.iptel.org

Are you receiving any error from the ITSP? Why?


What does it take for CUBE to register to the ITSP?

*TS Notes: there might be a timeout between registration request messages,


so you might have to be patient.
The timeout is due to DNS Cache used by the CSR to translate the registrar’s
DNS via an SRV record, which is set by default to 3600 seconds.
You can temporary change it by using:
sip-ua
timers dns registrar-cache 60

I do recommend you to change it back once you are registered.

Also, a quick reminder, a simple sip messages debug won’t be enough to see
registration requests.

Finally, verify that you are registered using the command:


show sip-ua register status
You can also try to force the registration by removing re re-entering the
registrar command under SIP-UA

Task 3
Incoming Call

1. Using CUCM, route your ITSP alias number to the MicroSIP client.
2. Go to sip2sip.info (scroll down) and download the SIP Client app for
your OS.
3. Install it and create an account as instructed.
4. Make a call to your Alias number (XXXX@iptel.org) from the SIP2SIP
client.

Are you able to see the incoming messages on CUBE?


Does the CUBE send any response?
Why?
What advanced debug can you run to find out?

This task is complete when CUBE sends a 100 trying response to the ITSP for
the incoming call.

Task 4
Make a call from SIP2SIP client to your iptel.org alias number again.

Is your CUCM registered MicroSIP client ringing?


Does the call reach CUCM?
If not, why?
What is the error message?
Can CUBE find an incoming Dial-Peer?
Which one?
Why?
You can use the “debug voip dialpeer inout” command for Dial-Peer TS.

This task is complete when CUBE matches Dial-Peer 2 as the Incoming Dial-
Peer.

Task 5
Repeat the call.
Can CUBE match an outgoing Dial-Peer?
Which one does it match?
Why?
This task is complete when CUBE sends an Invite request to the CUCM and
the MicroSIP client is ringing.

Task 6
Create a SIP Route Pattern

1. Configure a SIP Route pattern to route ‘*@iptel.org’ towards CUBE:

2. Make a call from the MicroSIP client to: thetestcall@iptel.org.

Can you make the call?


What is the error?
Why?

This task is complete when you receive an 100 Trying from the ITSP.

Task 7
Make a call from the MicroSIP client to: thetestcall@iptel.org.

Can CUBE complete the call?


What is the error? What is the source of the error?
Is there anything missing for the call to go through?

Task 8
Make a call from the MicroSIP client to: thetestcall@iptel.org.

Record a message and press #

Does the DTMF work?


Which DTMF method is negotiated between CUCM and CUBE?
Which DTMF method is negotiated between CUBE and ITSP?
Which DTMF method can be configured to allow end to end DTMF?
This task is complete when DTMF’s are going through to the ITSP and you
pass the echo test.

Task 9
Make a call to early_music@iptel.org from the MicroSIP client.

Is the call going through?


What is the error you receive?
What is the source of the error?
How can you fix it? What does the ITSP require in the initial INVITE for the
call to succeed?

This task is complete when you get a ringback tone for the call.

Task 10
Make a call to early_music@iptel.org from the MicroSIP client.

Is the call going through?


Is there a SIP error message?
What provisional response do we receive from the ITSP?
What does it mean?
How does the CUBE respond?
How does the CUCM respond?
How does the CUCM should respond for the Music to play?
What CUCM configuration is responsible for it?

This task is complete when you can hear the music being played.