<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Pushkar bhatkoti's blog........... &#187; CME SIP trunking configuration example</title>
	<atom:link href="http://pushkarbhatkoti.wordpress.com/category/cme-cisco-unified-cme/cme-sip-trunking-configuration-example/feed/" rel="self" type="application/rss+xml" />
	<link>http://pushkarbhatkoti.wordpress.com</link>
	<description>Just another CCIE voice certified person's blog....</description>
	<lastBuildDate>Mon, 07 Sep 2009 15:06:44 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<cloud domain='pushkarbhatkoti.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://www.gravatar.com/blavatar/6d139ceb5b354b59d6e3f1222585db12?s=96&#038;d=http://s.wordpress.com/i/buttonw-com.png</url>
		<title>Pushkar bhatkoti's blog........... &#187; CME SIP trunking configuration example</title>
		<link>http://pushkarbhatkoti.wordpress.com</link>
	</image>
			<item>
		<title>CME SIP Trunking Configuration Example</title>
		<link>http://pushkarbhatkoti.wordpress.com/2009/01/10/cme-sip-trunking-configuration-example/</link>
		<comments>http://pushkarbhatkoti.wordpress.com/2009/01/10/cme-sip-trunking-configuration-example/#comments</comments>
		<pubDate>Sat, 10 Jan 2009 14:19:29 +0000</pubDate>
		<dc:creator>pushkarbhatkoti</dc:creator>
				<category><![CDATA[CME SIP trunking configuration example]]></category>
		<category><![CDATA[cisco cme sip trunk]]></category>
		<category><![CDATA[isp sip trunk]]></category>

		<guid isPermaLink="false">http://pushkarbhatkoti.wordpress.com/?p=172</guid>
		<description><![CDATA[Note: This article is pulled from:
Source: http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_example09186a00808ff666.shtml
All credit goes to Cisco.com
(Cisco keep moving the pages here and there so, I thot to keep a copy of it for benifit of everyeone.)
 

Introduction
Today, the telecommunications industry is in the process of making the 	 transition from long establishing switching and transport techonologies to 	 IP-based transport [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pushkarbhatkoti.wordpress.com&blog=4335568&post=172&subd=pushkarbhatkoti&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>Note: This article is pulled from:</p>
<p><span>Source: http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_example09186a00808ff666.shtml</span><br />
All credit goes to Cisco.com<br />
(Cisco keep moving the pages here and there so, I thot to keep a copy of it for benifit of everyeone.)</p>
<blockquote><p><strong> </strong></p></blockquote>
<hr />
<h2><a name="intro">Introduction</a></h2>
<p>Today, the telecommunications industry is in the process of making the 	 transition from long establishing switching and transport techonologies to 	 IP-based transport and edge devices. The IP communication revolution has 	 started to create a tremendous commercial impact in small and medium 	 businesses. These small and medium businesses are realizing that the use of IP 	 is very efficient because IP can use Voice, Video, and Data capabilities over a 	 single network, instead of using three separate special-purpose networks. 	 Figure 1 shows an IP telephony deployment trending towards IP trunking.</p>
<p><strong>Figure 1 &#8211; IP Telephony System</strong><img src="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config1.gif" border="0" alt="cme-sip-trunking-config1.gif" /></p>
<p>IP PBXs are starting to predominate in the business of the Voice 	 technology, and the TDM PBXs are no longer the primary source as the crossover 	 going between two Voice networks. The usage of the TDM PBXs has decreased in 	 the last couple of years, and the use of the IP PBX is becoming a good 	 investment in IP LANs and WANs. In order to connect to the PSTN, PBXs need some 	 sort of trunking such as TDM (T1/E1) or analog lines. IP PBXs can access the 	 PSTN using these types of trunks, but need a media gateway that converts the IP 	 voice traffic to traditional PSTN, which sometimes can result in successive 	 translation from IP domain to TDM domain. These successive translations 	 increase the maintenance costs of the gateways, increases latency, and reduces 	 voice quality.</p>
<p>In order to avoid these problems, the IP PBXs use protocols for session 	 initiation and management, the most prominent of which is Session Initiation 	 Protocol (SIP). This document provides a description on SIP trunking and Cisco 	 CallManager Express (CME), and a configuration to implement an IP-based 	 telephony system with CME using SIP trunking for inbound and outbound 	 calls.</p>
<h2><a name="prereq">Prerequisites</a></h2>
<h3><a name="req">Requirements</a></h3>
<p>Ensure that you meet these requirements before you attempt this 	 configuration:</p>
<ul>
<li>CME release 4.1 is installed</li>
<li>An image of Cisco IOS® Software Release 12.4(11)XJ or IOS 12.4(6th)T 		is on the router</li>
<li>An NM-CUE module is installed with CUE release 		2.3.4</li>
</ul>
<h3><a name="hw">Components Used</a></h3>
<p>The information in this document is based on these software and 	 hardware versions:</p>
<ul>
<li>Cisco 3825 Router on Cisco IOS Software Release 		12.4(11)XJ</li>
<li>Cisco Catalyst 3550 Switch on Cisco IOS Software Release 		12.4</li>
<li>Cisco IP 7960 Phone</li>
<li>Cisco CallManager Express 4.1</li>
<li>Cisco Unity Express 2.3.4</li>
</ul>
<p>The information in this document was created from the devices in a 	 specific lab environment. All of the devices used in this document started with 	 a cleared (default) configuration. If your network is live, make sure that you 	 understand the potential impact of any command.</p>
<h3><a name="conv">Conventions</a></h3>
<p>Refer to the 	 <a href="http://www.cisco.com/en/US/tech/tk801/tk36/technologies_tech_note09186a0080121ac5.shtml">Cisco 	 Technical Tips Conventions</a> for more information on document 	 conventions.</p>
<h2><a name="backinfo">SIP Protocol</a></h2>
<p>SIP is an ASCII based, application-layer control protocol that can be 	 used to establish, maintain, and terminate calls between two or more endpoints. 	 SIP has rapidly emerged as the standard protocol used in IP communications, 	 because it is a multimedia protocol that can be used for video sessions and 	 instant messaging in addition to voice. Also, SIP can handle conference 	 sessions and broadcasts, as well as one-to-one sessions. SIP has great 	 potential in transforming and developing the way people communicate. For this 	 reason, Cisco has and continues to play an important role in taking a 	 leadership to create new technologies that make SIP and its applications the 	 standard of IP communications.</p>
<p>SIP trunks are similar to a phone line, except that SIP trunks use the 	 IP network, not the PSTN. In addition, SIP trunks permit the convergence of 	 voice and data onto common all-IP connections. In order to access the IP 	 network using an SIP trunk, it is necessary that configurations be made on the 	 service provider, as well as on the customer side. Customers need to set and 	 configure CME, which is the PBX that will interpret the SIP signal adequately 	 and pass traffic successfully. The service provider needs to configure an SIP 	 Proxy Server. However, SIP trunks are more complicated to establish than 	 regular PSTN trunks. The reason is that a customer faces challenges in handling 	 different interpretation and implementations of SIP by equipment vendors, 	 delivering security, managing quality of service (QoS), enabling Network 	 Address Translation (NAT) and firewall traversal, and ensuring carrier-grade 	 reliability and continuity of service.</p>
<p>These points describe why SIP trunks are becoming so apparent in small 	 and medium businesses:</p>
<ul>
<li>Quick and Easy Deployment</li>
<li>Improved Utilization of Network Capacity</li>
<li>Potential for Consolidating and Lowering Telephony 		Costs</li>
<li>Economical Direct Inward Dial (DID)</li>
<li>Business Continuity</li>
</ul>
<h2><a name="topic1">CME SIP Trunk Support</a></h2>
<p>Cisco CME is an IP telephony solution that is integrated directly into 	 Cisco IOS software. CME permits small and medium businesses to deploy voice, 	 data, and video on a single platform. An IP telephony network is simple to set 	 because CME runs on a single router, which delivers a PBX functionality for 	 businesses. Therefore, by using CME, small and medium businesses can deliver IP 	 telephony and data routing using a single converged solution with minimal 	 costs.</p>
<h3><a name="dtmf">DTMF Relay for SIP Trunks</a></h3>
<p>CME started to support SIP trunking when CME 3.1 was released. However, 	 some problems existed when an SIP phone called an SCCP phone or tried to access 	 voicemail. The problem is that SCCP phones connected to CME require the use of 	 out-of-band DTMF relay to transport DTMF (digits) across VoIP connections, and 	 SIP phones use in-band tranports. A DTMF distortion existed between the two 	 devices. When CME 3.2 was released, support was added to the DTMF relay. DTMF 	 digits from SCCP could be converted to in-band DTMF relay mechanism through 	 RFC2833 or Notify methods.</p>
<p>CME currently supports this list of DTMF internetworking for SIP to SIP 	 calls:</p>
<ul>
<li>Notify &lt;&#8212;&gt; Notify since 12.4(4)T</li>
<li>RFC2833 &lt;&#8212;&gt; Notify since 12.4(4)T</li>
<li>Notify &lt;&#8212;&gt; RFC2833 since 12.4(4)T</li>
<li>Inband G711 &lt;&#8212;&gt; since 12.4(11)T <strong>[Requires 		Transcoder]</strong></li>
</ul>
<p>CME currently supports this DTMF internetworking for SIP to SCCP 	 calls:</p>
<ul>
<li>SCCP out-of-band—SIP Notify / RFC2833 since 		12.4(4)T</li>
</ul>
<h3><a name="codecs">Codec Support and Transcoding</a></h3>
<p>Another important aspect to consider when you set up an SIP trunk is 	 the codecs supported. Codecs represent the pulse-code modulation sample for 	 signals in voice frequencies. SIP trunks support these codecs: G.711 and G.729. 	 However, for different features such as Cisco Unity Express (CUE) and Music on 	 Hold (MOH), only codec G.711 is supported. This means that voice calls that use 	 SIP trunks using codec G.729 cannot access CUE, unless a transcoder exists to 	 permit the compression and decompression of voice streams to match the CUE 	 capabilities. MOH can also use codec G.729 to save bandwidth, but the codec 	 does not provide adequate quality MOH streams. This is due to the fact that 	 G.729 is optimized for speech. Therefore, you must force MOH to use 	 G.711.</p>
<h3><a name="call-fwd">Call Forward</a></h3>
<p>When a call comes in on an SIP trunk and gets forwarded (CFNA / CFB / 	 CFA), then the default behavior is for the CME to send the 302 &#8220;Moved 	 Temporarily&#8221; SIP message to the Service Provider (SP) proxy. The user portion 	 of the Contact Header in the 302 message might need to be translated to reflect 	 a DID that the SP proxy can route to. The host portion of the Contact Header in 	 the 302 message should be modified to reflect the Address of Record (AOR) using 	 the <strong>host-registrar</strong> CLI under sip-ua and the 	 <strong>b2bua</strong> CLI under the VoIP dial peer going to the CUE.</p>
<p>Some SIP proxies might not support this. If so, then you need to add 	 this:</p>
<blockquote>
<pre>Router(config)#<strong>voice service voip</strong></pre>
</blockquote>
<blockquote>
<pre>Router(conf-voi-serv)#<strong>no supplementary-service sip moved-temporarily</strong></pre>
</blockquote>
<p>Figure 2 shows the behavior of the CME system when the 302 message is 	 disabled.</p>
<p><strong>Figure 2 &#8211; Call Forward Busy (CFB) flow with 302 message 		disabled</strong><img src="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config2.gif" border="0" alt="cme-sip-trunking-config2.gif" /></p>
<p>This method will allow hairpinning of the 302 SIP messages for call 	 forwards on the CME. The above is also required if there are certain extensions 	 that have no DID mapping as the SP proxy might not know how to route such 	 calls. If you disable the 3xx response, the <strong>calling-number 	 initiator</strong> can be used to preserve the caller ID of the original 	 calling party.</p>
<h3><a name="call-transfer">Call Transfer</a></h3>
<p>When a call comes in on an SIP trunk to an SCCP Phone or CUE 	 AutoAttendant (AA) and is transferred, the CME by default will send a SIP REFER 	 message to the SP proxy. Most SP Proxy Servers do not support the REFER method. 	 This needs to be configured in order to force the CME to hairpin the 	 call:</p>
<blockquote>
<pre>Router(config)#<strong>voice service voip</strong></pre>
</blockquote>
<blockquote>
<pre>Router(conf-voi-serv)#<strong>no supplementary-service sip refer</strong></pre>
</blockquote>
<p>Figure 3 shows the behavior of the CME system with the REFER method 	 disabled.</p>
<p><strong>Figure 3 &#8211; Transfer with REFER disabled</strong><img src="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config3.gif" border="0" alt="cme-sip-trunking-config3.gif" /></p>
<p>If REFER is supported on the SIP proxy, the user portion of the 	 Refer-To and Referred-By must be translated to a DID that the SP proxy 	 understands. The host portion of the Refer-To and Referred-By fields must be an 	 IP address or DNS that the SP proxy can route to as well (this occurs by 	 default on CME 4.1).</p>
<h3><a name="call-hold">Call Hold</a></h3>
<p>If an SCCP phone places a call from PSTN on HOLD, the CME locally 	 changes the media. No SIP messages are sent across on the SIP trunk. Music on 	 Hold will be played to the user across the SIP trunk based on the CME 	 configuration.</p>
<h2><a name="conf">Configure</a></h2>
<p>In this section, you are presented with the information to configure 	 the features described in this document.</p>
<p><strong>Note: </strong>Use the 		<a href="http://www.cisco.com/pcgi-bin/Support/Cmdlookup/home.pl">Command 		Lookup Tool</a> (<span> <a href="http://tools.cisco.com/RPF/register/register.do">registered</a> customers only</span>)          to obtain more information on the commands used in this 		section.</p>
<h3><a name="diag">Network Diagram</a></h3>
<p>This document uses this network setup:</p>
<p><img src="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config4.gif" border="0" alt="cme-sip-trunking-config4.gif" /></p>
<h3><a name="configs">Configurations</a></h3>
<p>These configuration elements provide an outline of the steps required 	 to configure your CME with SIP trunks:</p>
<ul>
<li>Infrastructure Elements: Interfaces, TFTP and DHCP services, NTP, 		etc</li>
<li>Telephony-service: Enables IOS &#8220;PBX&#8221; call control on the CME platform 		including elements of phone management</li>
<li>Ephones an Ephones-dns: Define IP phones and their telephone 		numbers</li>
<li>Dial Plan: Dial-peers, extensions, voice-translation 		rules</li>
<li>IOS SIP Configuration: Enables SIP, phone registration with SIP 		proxy, call routing over trunks, etc</li>
<li>Voicemail Support: Cisco Unity Express</li>
<li>Switch Catalyst Configuration: IP address, Interfaces, 		etc</li>
</ul>
<p>This is the complete configuration needed to deploy a CME system with 	 SIP trunks:</p>
<table border="1" cellspacing="1" cellpadding="3" width="60%" bgcolor="#ffffff">
<tbody>
<tr>
<th>Router &#8211; CME Configuration</th>
</tr>
<tr>
<td bgcolor="#ffffff">
<pre>!
AUSNML-3825-01#<strong>show run</strong>
Building configuration...

Current configuration : 8634 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname AUSNML-3825-01
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$vBU1$MCMG1rXM5ejME8Wap6W0H1
!
no aaa new-model
clock timezone central -8
clock summer-time central recurring
ip cef
!
<em>
<span style="color:#0000ff;">!--- DHCP Configuration ---</span>
</em>
ip dhcp pool Voice
   network 172.22.100.0 255.255.255.0
   option 150 ip 172.22.1.107
   default-router 172.22.100.1
!
ip dhcp pool Data
   network 172.22.101.0 255.255.255.0
   option 150 ip 172.22.1.107
   default-router 172.22.101.1
!
!
ip domain name cisco.com
ip name-server 205.152.0.20
multilink bundle-name authenticated
!
voice-card 0
 no dspfarm
!
!
!
!
<em>
<span style="color:#0000ff;">!--- Voice Class and Service VoIP Configuration ---</span>
</em>
voice service voip
 allow-connections sip to sip
 no supplementary-service sip moved-temporarily
<em>
<span style="color:#0000ff;">!---Disable 302 sending</span>
</em>
 no supplementary-service sip refer
<em>
<span style="color:#0000ff;">!---Disable REFER sending</span>
</em>
 sip
  registrar server expires max 3600 min 3600
  localhost dns:domain.test.com
!
!
voice class codec 1
 codec preference 1 g711ulaw
!
!
!
!
!
!
!
!
!
!
!
<em>
<span style="color:#0000ff;">!--- Voice Translation Rules ---</span>
</em>
voice translation-rule 1
 rule 1 /5123781291/ /601/
<em>
<span style="color:#0000ff;">!--- An inbound rule for AA pilot "601</span>
</em>
 rule 2 /5123781290/ /600/
<em>
<span style="color:#0000ff;">!--- An inbound rule for the voicemail pilot "600"</span>
</em>
!
voice translation-rule 2
 rule 1 /^911$/ /911/
<em>
<span style="color:#0000ff;">!--- An outbound rule to allow "911"</span>
</em>
 rule 2 /^9(.*)/ /\1/
<em>
<span style="color:#0000ff;">!--- An outbound rule to strip "9" from PSTN calls</span>
</em>
!
voice translation-rule 3
 rule 1 /^.*/ /5123781291/
<em>
<span style="color:#0000ff;">!--- An outbound rule to change calling-number CLID to a
!--- "main" number</span>
</em>
!
voice translation-rule 4
 rule 1 /^9(.......)$/ /512\1/
<em>
<span style="color:#0000ff;">!--- An outbound rule to add areacode for local calls</span>
</em>
 rule 2 /600/ /5123788000/
<em>
<span style="color:#0000ff;">!--- An outbound rule to present the voicemail pilot extension as DID</span>
</em>
 rule 3 /601/ /5123788001/
<em>
<span style="color:#0000ff;">!--- An outbound rule to present the AA pilot extension as DID</span>
</em>
 rule 4 /^2(..)$/ /51237812\1/
<em>
<span style="color:#0000ff;">!--- An outbound rule to support transfers and call-forwards</span>
</em>
 rule 5 /^9(.*)/ /\1/
<em>
<span style="color:#0000ff;">!--- An outbound rule to strip "9" from "9+" transfers and call-forwards</span>
</em>
!
!
voice translation-profile CUE_Voicemail/AutoAttendant
<em>
<span style="color:#0000ff;">!--- Applied to the inbound dial-peers for CUE</span>
</em>
 translate called 1
!
voice translation-profile PSTN_CallForwarding
<em>
<span style="color:#0000ff;">!--- Applied to CUE dial-peers</span>
</em>
 translate redirect-target 4
 translate redirect-called 4
!
voice translation-profile PSTN_Outgoing
<em>
<span style="color:#0000ff;">!--- Applied to all outbound dial-peers</span>
</em>
 translate calling 3
 translate called 2
 translate redirect-target 4
 translate redirect-called 4
!
!
!
!
!
!
!
vlan internal allocation policy ascending
!
!
!
!
<em>
<span style="color:#0000ff;">!--- Internet Connection Configuration ---</span>
</em>
interface GigabitEthernet0/0
 no ip address
 duplex auto
 speed auto
 media-type rj45
 no keepalive
!
interface GigabitEthernet0/0.1
 encapsulation dot1Q 1 native
 ip address 172.22.1.71 255.255.255.0
!
interface GigabitEthernet0/0.20
 encapsulation dot1Q 20
 ip address 172.22.101.1 255.255.255.0
!
interface GigabitEthernet0/0.100
 encapsulation dot1Q 100
 ip address 172.22.100.1 255.255.255.0
!
interface GigabitEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
 media-type rj45
 no keepalive
!
interface Service-Engine1/0
 ip unnumbered GigabitEthernet0/0.1
 service-module ip address 172.22.1.253 255.255.255.0
 service-module ip default-gateway 172.22.1.71
!
ip route 0.0.0.0 0.0.0.0 172.22.1.1
ip route 172.22.1.253 255.255.255.255 Service-Engine1/0
!
!
ip http server
no ip http secure-server
!
!
!
<em>
<span style="color:#0000ff;">!--- TFTP Server Configuration  ---</span>
</em>
tftp-server flash:P0030702T023.bin
tftp-server flash:P0030702T023.loads
tftp-server flash:P0030702T023.sb2
tftp-server flash:P0030702T023.sbn
!
control-plane
!
!
!
!
!
!
!
<em>
<span style="color:#0000ff;">!--- SIP Trunk Configuration ---</span>
</em>
dial-peer voice 1 voip
 description **Incoming Call from SIP Trunk**
 translation-profile incoming CUE_Voicemail/AutoAttendant
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 incoming called-number .%
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 2 voip
 description **Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9........
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 3 voip
 description **Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9[2-9]..[2-9]......
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 4 voip
 description **Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9[0-1][2-9]..[2-9]......
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 5 voip
 description **911 Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 911
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 6 voip
 description **Emergency Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9911
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 7 voip
 description **911/411 Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9[2-9]11
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 8 voip
 description **International Outgoing Call to SIP Trunk**
 translation-profile outgoing PSTN_Outgoing
 destination-pattern 9011T
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
dial-peer voice 9 voip
 description **Star Code to SIP Trunk**
 destination-pattern *..
 voice-class codec 1
 voice-class sip dtmf-relay force rtp-nte
 session protocol sipv2
 session target sip-server
 dtmf-relay rtp-nte
 no vad
!
!
!
<em>
<span style="color:#0000ff;">!--- Voicemail Configuration ---</span>
</em>
dial-peer voice 10 voip
 description **CUE Voicemail**
 translation-profile outgoing PSTN_CallForwarding
 destination-pattern 600
 b2bua
<em>
<span style="color:#0000ff;">!--- Used by CME to send its IP address to SP proxy instead of CUE</span>
</em>
 session protocol sipv2
 session target ipv4:172.22.1.155
 dtmf-relay sip-notify
<em>
<span style="color:#0000ff;">!--- This can also be RFC2833 going to CUE</span>
</em>
 codec g711ulaw
<em>
<span style="color:#0000ff;">!--- CUE only supports G711ulaw as the codec</span>
</em>
 no vad
<em>
<span style="color:#0000ff;">!--- With VAD enabled, messages left on CUE could be blank or poor quality</span>
</em>
!
!
!
dial-peer voice 11 voip
 description **CUE Auto Attendant**
 translation-profile outgoing PSTN_CallForwarding
 destination-pattern 601
 b2bua
 session protocol sipv2
 session target ipv4:172.22.1.155
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!
!
<em>
<span style="color:#0000ff;">!--- SIP UA Configuration ---</span>
</em>
sip-ua
 authentication username 5123781000 password 075A701E1D5E415447425B
 no remote-party-id
 retry invite 2
 retry register 10
 retry options 0
 timers connect 100
 registrar dns:domain.test.com expires 3600
 sip-server dns:domain.test.com
  host-registrar
!
!
<em>
<span style="color:#0000ff;">!--- CME Telephony Service Configuration ---</span>
</em>
telephony-service
 no auto-reg-ephone
 load 7960-7940 P0030702T023
 max-ephones 168
 max-dn 500
 ip source-address 172.22.1.107 port 2000
 calling-number initiator
<em>
<span style="color:#0000ff;">!--- Preserves the caller-id of a call when transferred or forwarded</span>
</em>
 dialplan-pattern 1 51237812.. extension-length 3 extension-pattern 2.. no-reg
 voicemail 600
 max-conferences 12 gain -6
 call-forward pattern .T
 call-forward system redirecting-expanded
<em>
<span style="color:#0000ff;">!--- Enables translation rule features for call-forwarding</span>
</em>
 moh music-on-hold.au
 transfer-system full-consult dss
 transfer-pattern 9.T
 secondary-dialtone 9
 create cnf-files version-stamp Jan 01 2002 00:00:00
!
!
<em>
<span style="color:#0000ff;">!--- Ephone and Ephone-dn Configuration ---</span>
</em>
ephone-dn  11  dual-line
 number 201 secondary 5123781201 no-reg both
<em>
<span style="color:#0000ff;">!---"no-reg both" means do not try to register either extension with SP SIP Proxy</span>
</em>
 name John Smith
 call-forward busy 600
 call-forward noan 600 timeout 15
!
!
ephone-dn  12  dual-line
 number 202 secondary 5123781202 no-reg both
 name Enrique Zurita
 call-forward busy 600
 call-forward noan 600 timeout 15
!
!
ephone-dn  13
 number 5123788000
 description **DID Number for Voicemail**
!
!
ephone-dn  14
 number 5123788001
 description **DID Number for Auto Attendant*
!
!
ephone-dn  15
 number 8000... no-reg primary
 mwi on
!
!
ephone-dn  16
 number 8001... no-reg primary
 mwi off
!
!
ephone  1
 mac-address 0008.A371.28E9
 type 7960
 button  1:11
!
!
!
ephone  2
 mac-address 0008.A346.5C7F
 type 7960
 button  1:12
!
!
!
!
line con 0
 stopbits 1
line aux 0
 stopbits 1
line 66
 no activation-character
 no exec
 transport preferred none
 transport input all
 transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
line vty 0 4
 password ut69coe
 login
!
scheduler allocate 20000 1000
ntp server 172.22.1.107
!
end</pre>
</td>
</tr>
</tbody>
</table>
<table border="1" cellspacing="1" cellpadding="3" width="60%" bgcolor="#ffffff">
<tbody>
<tr>
<th>Router &#8211; CUE Configuration</th>
</tr>
<tr>
<td bgcolor="#ffffff">
<pre>se-172-22-1-253#<strong>show run</strong>

Generating configuration:

clock timezone America/Chicago

hostname se-172-22-1-253

ip domain-name localdomain

groupname Administrators create
groupname Broadcasters create

<em>
<span style="color:#0000ff;">!--- Users ---</span>
</em>
username Enrique create
username John create
username Enrique phonenumberE164 "5123781202"
username John phonenumberE164 "5123781201"
username Enrique phonenumber "202"
username John phonenumber "201"

<em>
<span style="color:#0000ff;">!--- AutoAttendant ---</span>
</em>
ccn application autoattendant
 description "**AutoAttendant**"
 enabled
 maxsessions 4
 script "aa.aef"
 parameter "busOpenPrompt" "AABusinessOpen.wav"
 parameter "operExtn" "601"
 parameter "welcomePrompt" "AAWelcome.wav"
 parameter "disconnectAfterMenu" "false"
 parameter "busClosedPrompt" "AABusinessClosed.wav"
 parameter "allowExternalTransfers" "false"
 parameter "holidayPrompt" "AAHolidayPrompt.wav"
 parameter "businessSchedule" "systemschedule"
 parameter "MaxRetry" "3"
 end application

<em>
<span style="color:#0000ff;">!--- MWI ---</span>
</em>
ccn application ciscomwiapplication
 description "ciscomwiapplication"
 enabled
 maxsessions 8
 script "setmwi.aef"
 parameter "CallControlGroupID" "0"
 parameter "strMWI_OFF_DN" "8001"
 parameter "strMWI_ON_DN" "8000"
 end application

<em>
<span style="color:#0000ff;">!--- Voicemail ---</span>
</em>
ccn application voicemail
 description "**Voicemail**"
 enabled
 maxsessions 4
 script "voicebrowser.aef"
 parameter "uri" "http://localhost/voicemail/vxmlscripts/login.vxml"
 parameter "logoutUri" "http://localhost/voicemail/vxmlscripts/mbxLogout.jsp"
 end application

<em>
<span style="color:#0000ff;">!--- SIP ---</span>
</em>
ccn subsystem sip
 gateway address "172.22.100.1"
<em>
<span style="color:#0000ff;">!--- Must match the "ip source-address" in telephony-service</span>
</em>
 dtmf-relay sip-notify
 mwi sip outcall
<em>
<span style="color:#0000ff;">!--- Subscribe / Notify and Unsolicited Notify have not been tested</span>
</em>
 transfer-mode blind bye-also
<em>
<span style="color:#0000ff;">!--- Testing with REFER method on CUE has caused certain call flows to break</span>
</em>
 end subsystem

<em>
<span style="color:#0000ff;">!--- Trigger Phones ---</span>
</em>
ccn trigger sip phonenumber 600
 application "voicemail"
 enabled
 maxsessions 4
 end trigger

ccn trigger sip phonenumber 601
 application "autoattendant"
 enabled
 maxsessions 4
 end trigger

service phone-authentication
 end phone-authentication

service voiceview
 enable
 end voiceview

<em>
<span style="color:#0000ff;">!--- Voicemail Mailboxes ---</span>
</em>
voicemail default mailboxsize 21120
voicemail broadcast recording time 300

voicemail mailbox owner "Enrique" size 300
 description "**Enrique_Mailbox**"
 expiration time 10
 messagesize 120
 end mailbox

voicemail mailbox owner "John" size 300
 description "**John'sMailbox**"
 expiration time 10
 messagesize 120
 end mailbox

end</pre>
</td>
</tr>
</tbody>
</table>
<table border="1" cellspacing="1" cellpadding="3" width="60%" bgcolor="#ffffff">
<tbody>
<tr>
<th>Switch Configuration</th>
</tr>
<tr>
<td bgcolor="#ffffff">
<pre><em>
<span style="color:#0000ff;">!--- Interface Connected to CME/CUE Router ---</span>
</em>
interface FastEthernet0/2
 description Trunk to 3825
 switchport trunk encapsulation dot1q
 switchport mode trunk
 no ip address
 duplex full
 speed 100

<em>
<span style="color:#0000ff;">!--- Interfaces Connected to the IP Phones ---</span>
</em>
interface FastEthernet0/7
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 20
<em>
<span style="color:#0000ff;">!--- Data Traffic ---</span>
</em>
 switchport mode trunk
 switchport voice vlan 100
<em>
<span style="color:#0000ff;">!--- Voice Traffic ---</span>
</em>
 no ip address
 spanning-tree portfast

interface FastEthernet0/8
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 20
 switchport mode trunk
 switchport voice vlan 100
 no ip address
 spanning-tree portfast

<em>
<span style="color:#0000ff;">!--- IP Address ---</span>
</em>
interface Vlan1
 ip address 172.22.1.194 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.22.1.1
ip http server</pre>
</td>
</tr>
</tbody>
</table>
<h2><a name="veri">Verify</a></h2>
<p>There is currently no verification procedure available for this 	 configuration.</p>
<h2><a name="tshoot">Troubleshoot</a></h2>
<p>This section provides information you can use to troubleshoot your 	 configuration.</p>
<p>The 	 <a href="https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl">Output Interpreter Tool</a> (<span> <a href="http://tools.cisco.com/RPF/register/register.do">registered</a> customers only</span>)          (OIT) supports certain 	 <strong>show</strong> commands. Use the OIT to view an analysis of 	 <strong>show</strong> command output.</p>
<p><strong>Note: </strong>Refer to 		<a href="http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a008017874c.shtml">Important 		Information on Debug Commands</a> before you use 		<strong>debug</strong> commands.</p>
<h3><a name="reg">Troubleshooting Registration</a></h3>
<p>Troubleshooting the SIP trunk on CME involves the same commands you use 	 for IOS SIP GW troubleshooting and CME troubleshooting. Use these commands in 	 order to check if your DN is registered:</p>
<ul>
<li><strong>show sip-ua register status</strong>—Use this 		command to display the status of E.164 numbers that a SIP gateway has 		registered with an external primary SIP registrar.</li>
<li><strong>debug ccsip message</strong>—Enables all SIP SPI 		message tracing, such as those that are exchanged between the SIP user-agent 		client (UAC) and the access server.</li>
</ul>
<h3><a name="call-setup">Troubleshooting Call Setup</a></h3>
<p>Commands for troubleshooting calls over SIP trunks are essentially the 	 same as you use for regular SIP GW and CME troubleshooting.</p>
<p><strong>Show</strong> commands:</p>
<ul>
<li><strong>show ephone registered</strong>—Verifies ephone 		registration.</li>
<li><strong>show voip rtp connection</strong>—Displays 		information about RTP named-event packets, such as caller-ID number, IP 		address, and ports for both the local and remote endpoints.</li>
<li><strong>show sip-ua call</strong>—Displays active UAC and 		user agent server (UAS) information on SIP calls.</li>
<li><strong>show call active voice brief</strong>—Displays 		active call information for voice calls or fax transmissions in 		progress.</li>
</ul>
<p><strong>Debug</strong> commands:</p>
<ul>
<li><strong>debug ccsip message</strong>—Enables all SIP SPI 		message tracing, such as those that are exchanged between the SIP UAC and the 		access server.</li>
<li><strong>debug voip ccapi inout</strong>—Traces the 		execution path through the call control API.</li>
<li><strong>debug voice translation</strong>—Checks the 		functionality of a translation rule.</li>
<li><strong>debug ephone detail mac-address <span style="font-weight:normal;font-style:italic;">&lt;mac of 		phone&gt;</span> </strong>—Sets detail debugging for the Cisco IP 		phone.</li>
<li><strong>debug voip rtp session 		named-events</strong>—Enables debugging for Real-Time Transport Protocol 		(RTP) named events packets.</li>
<li><strong>debug sccp message</strong>—Displays the sequence 		of the SCCP messages.</li>
</ul>
<p>Push Bhatkoti</p>
<p>CCIE voice#21569</p>
<p><span class="content"><br />
</span></p>
<p><span class="content"><br />
</span></p>
  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/pushkarbhatkoti.wordpress.com/172/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/pushkarbhatkoti.wordpress.com/172/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/pushkarbhatkoti.wordpress.com/172/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/pushkarbhatkoti.wordpress.com/172/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/pushkarbhatkoti.wordpress.com/172/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/pushkarbhatkoti.wordpress.com/172/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/pushkarbhatkoti.wordpress.com/172/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/pushkarbhatkoti.wordpress.com/172/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/pushkarbhatkoti.wordpress.com/172/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/pushkarbhatkoti.wordpress.com/172/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pushkarbhatkoti.wordpress.com&blog=4335568&post=172&subd=pushkarbhatkoti&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://pushkarbhatkoti.wordpress.com/2009/01/10/cme-sip-trunking-configuration-example/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/89c6928aa356ad85cfc4a6752fea7f09?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">pushkarbhatkoti</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config1.gif" medium="image">
			<media:title type="html">cme-sip-trunking-config1.gif</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config2.gif" medium="image">
			<media:title type="html">cme-sip-trunking-config2.gif</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config3.gif" medium="image">
			<media:title type="html">cme-sip-trunking-config3.gif</media:title>
		</media:content>

		<media:content url="http://www.cisco.com/image/gif/paws/91535/cme-sip-trunking-config4.gif" medium="image">
			<media:title type="html">cme-sip-trunking-config4.gif</media:title>
		</media:content>
	</item>
	</channel>
</rss>