How to setup CCIE Voice Home lab with Dynamips/VMware

This is an attempt to simulate a decent CCIE Voice home lab on a single PC (with oodles of memory and a bleeding edge CPU).

• What can it do?

• Frame Relay/OSPF
  
• Calls between all sites using 4 digit or full E.164 numbers
• Full route plans using RG, RL, RP and H323 gateways or trunks
  
• SRST
  
• AAR
  
• Voicemail integration of CCM/CME with Unity
• IPCC (almost everything)
• CME , COR, dial plan with 4 digit or full E.164 dialing
• WAN QoS
• Call manager Applications - IPMA, Ext Mob, Attendant Console
• Gatekeepers, IPIP GW, SIP gateways and trunks

• What doesn't work?

• Anything that involves a DSP like transcoding, conferencing or calls with multiple codecs
  
• Any type of voice port configuration - PRI or CAS, FXO/FXS, E&M..
  
• Anything related to the 6500, VG248, ATA (although it might be possible to connect to an ATA externally if you are adventurous - all it needs is a DHCP address and access to CCM), specifically port configuration or QoS.
  
• CUE or anything related to it
• LAN QoS
• MGCP

• How is this done?

• Four routers in dynamips, one for PSTN, one each for HQ, RS1, RS2
• Frame relay over T1 cross-overs between all three sites
• All four routers connected by FE to a virtual switch for H.323 traffic
• VMware server with CCM/IPCC on one VM, Unity on another, 3 virtual networks
  
• Third VM running Windows 2000Pro (XP is a hog) with 3 NIC cards
• Multiple copies of IP Blue 'evaluation' phone on the w2k workstation for HQ, RS1,RS2, PSTN phones.
• Basic configurations as detailed below for all routers.
• Lots and lots of memory and a bleeding edge CPU.
• Did I tell you lots and lots of memory and a bleeding edge CPU?
• Patience - If all of this stuff is running at once, this thing will be crawling - start up only the stuff you need, and it will rock!

Following is a diagram of how it is all set up

• VMware is set up with three network adapters vmnet1,vmnet2 and vmnet3 with ip addresses as 10.101.1.1/24, 10.102.1.1/24 and 10.103.1.1/24
• HQ, RS1 and RS2 connected to PSTN via T1 crossover and frame-relay encapsulation
  
• HQ, RS1 and RS2 routers has their fa0/0 interface with 10.[101/102/103].1.254
• HQ, RS1 and RS2 routers has the loopback0 with 10.[11/12/13].1.254
  
• PSTN, HQ, RS1 and RS2 has their fa0/1 interface as 10.100.1.[1/2/3/4]
  
• HQ, RS1 and RS2 has VOIP dial-peers with 'session-target ipv4:10.100.1.1'
• PSTN router has CME enabled and the extensions 911,101xxxyyyy,202xxxyyyy, 303xxxyyyy and so on..
• PSTN router has VOIP dial peers pointing to the appropriate router for the extensions that belong at that site, for example 'session target ipv4:10.11.1.254' for 'destination-pattern 101xxxyyyy'
• CME with B-ACD on the RS2 router
• SRST with AA on the RS1 router
• IPIPGW must be running on the HQ and RS1 routers - here's why. CCM will have HQ and RS1 routers configured as H.323 gateways - so the call to "PSTN" is a call to the H.323 gateway, which hits the router and.. the router in turn sends the call over h.323 to the "PSTN" simulator. So, the call has two h.323 legs to go one way - 'voice service voip, allow connections h323 to h323' - sound familiar? :-)

Forgot to mention one key part - My laptop is not running Windows - I am a long time Linux fan and is running Slackware 11.0, VMware server 1.0.3 on a Dell D620 with dual Centrino and 2GB of RAM.

That's pretty much what I can think of now.. Configs are included below to have the basic connectivity going as mentioned above. Rack your brains to build out the rest.

There are excellent notes by people elsewhere on the net on how to get CCM installed in a VM, how to launch multiple IP blue phones simultaneously (speaking of IP blue phones, I will write up another tip for getting multiple of those phones running quickly and post it here next), et cetera, et cetera..

Standard Disclaimers, just to avoid any hard feelings going forward :-)

I CANNOT provide you IOS images or CCM/IPCC software, All the trademarks and references of any of the commercial/ non commercial software/hardware referenced in this post are the properties of their respective owners and I do not claim any rights to them whatsoever... and last but not least, I am not responsible for anything that results directly or indirectly from following my instructions here - anything at all including but not limited to 'your computer blowing up' or 'your girlfriend/wife leaving you since you got hooked to VMware or dynamips'.

Three cheers for dynamips , dynagen and VMware.. and good luck for those who are working on their CCIE Voice labs!!

Dynagen .NET file for the network section :

I used 2691 routers since they can do IOS with IPIPGW, Frame relay, dot1q trunks, dhcp server, CME, SRST , h.323, SIP and so on with IOS 12.4 on 128MB RAM. The IOS I used is c2691-adventerprisek9_ivs-mz.124-9.T1. Yes, I know that this is not the same IOS mentioned in the lab blue print at Cisco's site, but this does most of what 'wanted to learn' using this environment. The idlepc values are specific to my IOS, and might not work if you use a different IOS - I get the dynamips CPU/memory usage down to 30%/32% approximately with these values when all of the devices up and running (CPU spikes momentarily to 99% while doing 'show running' or 'write mem' though).

ghostios = True
[localhost]

[[2691]]
image = /data/tftpboot/C2691-IP.BIN
ram = 128
slot1 = NM-4T

[[ROUTER PSTN]]
model = 2691
f0/1 = S4 1
s1/0 = HQ s1/0
s1/1 = RS1 s1/0
s1/2 = RS2 s1/0
idlepc = 0x60af83ec

[[ROUTER HQ]]
model = 2691
f0/0 = S1 1
f0/1 = S4 2
idlepc = 0x61f02640

[[ROUTER RS1]]
model = 2691
f0/0 = S2 1
f0/1 = S4 3
idlepc = 0x61f02640

[[ROUTER RS2]]
model = 2691
f0/0 = S3 1
f0/1 = S4 4
idlepc = 0x61f02640

[[ethsw S1]]
1 = access 1 NIO_linux_eth:vmnet1

[[ethsw S2]]
1 = access 1 NIO_linux_eth:vmnet2

[[ethsw S3]]
1 = access 1 NIO_linux_eth:vmnet3

[[ethsw S4]]
1 = access 100
2 = access 100
3 = access 100
4 = access 100

Relevant sections of the PSTN router

frame-relay switching

interface FastEthernet0/1
ip address 10.100.1.1 255.255.255.0
speed 100
full-duplex
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.100.1.1

interface Serial1/0
description HQ-RTR
no ip address
encapsulation frame-relay IETF
serial restart-delay 0
frame-relay lmi-type ansi
frame-relay intf-type dce
frame-relay route 201 interface Serial1/1 101
frame-relay route 202 interface Serial1/2 102

interface Serial1/1
description BR1-RTR
no ip address
encapsulation frame-relay IETF
no fair-queue
serial restart-delay 0
frame-relay lmi-type ansi
frame-relay intf-type dce
frame-relay route 101 interface Serial1/0 201

interface Serial1/2
description BR2-RTR
no ip address
encapsulation frame-relay IETF
serial restart-delay 0
frame-relay lmi-type ansi
frame-relay intf-type dce
frame-relay route 102 interface Serial1/0 202

ip route 10.11.1.0 255.255.255.0 10.100.1.2
ip route 10.12.1.0 255.255.255.0 10.100.1.3
ip route 10.13.1.0 255.255.255.0 10.100.1.4

tftp-server flash:P00307020200.bin
tftp-server flash:P00307020200.loads
tftp-server flash:P00307020200.sb2
tftp-server flash:P00307020200.sbn

dial-peer voice 2000 voip
destination-pattern 1011111...
session target ipv4:10.11.1.254
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

dial-peer voice 3000 voip
destination-pattern 2022222...
session target ipv4:10.12.1.254
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

dial-peer voice 4000 voip
destination-pattern 3033333...
session target ipv4:10.13.1.254
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

dial-peer voice 1 voip
incoming called-number .
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

telephony-service
load 7960-7940 P00307020200
max-ephones 1
max-dn 5
ip source-address 10.100.1.1 port 2000

ephone-dn 1 dual-line
number 911

ephone-dn 2 dual-line
number 1015551111

ephone-dn 3 dual-line
number 2025552222

ephone-dn 4 dual-line
number 3035553333

ephone-dn 5 dual-line
number 55987654321

ephone 1
mac-address 0000.0000.0000
type 7960
button 1:1 2:2 3:3 4:4 5:5

gateway

Sample Site router HQ:

voice service voip
allow-connections h323 to h323

interface Loopback0
ip address 10.11.1.254 255.255.255.255
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.11.1.254

interface FastEthernet0/0
ip address 10.101.1.254 255.255.255.0
speed 100
full-duplex

interface FastEthernet0/1
ip address 10.100.1.2 255.255.255.0
speed 100
full-duplex
no cdp enable

interface Serial1/0
no ip address
encapsulation frame-relay IETF
serial restart-delay 0
frame-relay lmi-type ansi

interface Serial1/0.1 point-to-point
ip address 10.200.1.1 255.255.255.0
ip ospf mtu-ignore
frame-relay interface-dlci 201

interface Serial1/0.2 point-to-point
ip address 10.200.2.1 255.255.255.0
ip ospf mtu-ignore
frame-relay interface-dlci 202

router ospf 1
network 10.200.1.0 0.0.0.255 area 0
network 10.200.2.0 0.0.0.255 area 0
network 10.101.1.0 0.0.0.255 area 0
network 10.102.1.0 0.0.0.255 area 0
network 10.103.1.0 0.0.0.255 area 0

dial-peer voice 1 voip
destination-pattern .T
session target ipv4:10.100.1.1
incoming called-number .
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

dial-peer voice 2010 voip
destination-pattern 1011111...
session target ipv4:10.101.1.10
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

gateway

In addition, create static routes on the workstation redirecting traffic for the HQ, RS1 and PSTN loopback interfaces through HQ router, and the CME related traffic to the CME router. This reduces delay to the PSTN phone (which again is on your w2k desktop with TFTP address pointing to 10.100.1.1)

..now let the comments begin.

posted by jayanm