le)# translate called 2 Now that we've got our translations in order, we can create the dial peer. You could create the dial peer before you made the translation, but it just wouldn't work. The commands are all the same as the incoming peer with the exception that we're config- uring a destination-pattern this time. This destination pattern matches any 11-digit dialed number that starts with a 9: R1-PBX(config)#dial-peer voice 90 voip R1-PBX(config-dial-peer)# translation-profile outgoing SIP-Outbound R1-PBX(config-dial-peer)# destination-pattern 9 R1-PBX(config-dial-peer)# session protocol sipv2 R1-PBX(config-dial-peer)# session target sip-server R1-PBX(config-dial-peer)# dtmf-relay rtp-nte R1-PBX(config-dial-peer)# codec g711ulaw R1-PBX(config-dial-peer)# no vad This works well for dialing friends and family, but one thing we need to consider is people dialing 911 for emergencies. There are a couple of ways to deal with this, de- pending on whether your provider supplies E-911 service. Ours does, SO all we need to do is provide a dial plan that will accept 911 as a destination pattern, since the one we just created does not. The first dial peer addresses people who dial 911 in a panic without remembering that they need to dial 9 first: R1-PBX(config)#dial-peer voice 91 voip R1-PBX(config-dial-peer)# translation-profile outgoing SIP-Outbound R1-PBX(config-dial-peer)# destination-pattern 911 R1-PBX(config-dial-peer)# session protocol sipv2 R1-PBX(config-dial-peer)# session target sip-server R1-PBX(config-dial-peer)# dtmf-relay rtp-nte R1-PBX(config-dial-peer)# codec g711ulaw R1-PBX(config-dial-peer)# no vad We need another to match in the case that someone does remember to dial 9 first. Everything is the same except for the dial peer identifier and the destination pattern, SO to save space, I'll show only the destination pattern: Chapter VolP R1-PBX(config-dial-peer)# destination-pattern 9911 Here's a destination pattern that allows 411 and 911 (as well as 211, 311, 511, 611, 711, and 811): R1-PBX(config-dial-pee