<?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/"
	>

<channel>
	<title>Sirius Packet Solutions</title>
	<atom:link href="http://www.siriuspackets.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.siriuspackets.com</link>
	<description>Routing packets where the sun don't shine!</description>
	<pubDate>Thu, 01 Oct 2009 17:21:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Cisco Packet Tracer 5.1 Download</title>
		<link>http://www.siriuspackets.com/2009/10/01/cisco-packet-tracer-51-download/</link>
		<comments>http://www.siriuspackets.com/2009/10/01/cisco-packet-tracer-51-download/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 17:21:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<category><![CDATA[IP Routing]]></category>

		<category><![CDATA[IP Services]]></category>

		<category><![CDATA[cisco ccna lab]]></category>

		<category><![CDATA[cisco virtual router]]></category>

		<category><![CDATA[download packet tracer]]></category>

		<category><![CDATA[packet tracer]]></category>

		<category><![CDATA[packet tracer download]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=128</guid>
		<description><![CDATA[This is the best way you can practice and familiarize yourself with Cisco routers and IOS for people wanting to get started with Cisco products. I have used this tool in the past and found it to be very helpful. The intuitive graphics shows you the packet flow for the network you configure from scratch. [...]]]></description>
			<content:encoded><![CDATA[<p>This is the best way you can practice and familiarize yourself with Cisco routers and IOS for people wanting to get started with Cisco products. I have used this tool in the past and found it to be very helpful. The intuitive graphics shows you the packet flow for the network you configure from scratch. Almost like the real thing. Perfect for setting up your virtual lab.</p>
<p>Packet Tracer 5.1 is the latest version of Cisco’s simulation software. The main objective of Packet Tracer is to serve as a support tool for the Cisco Academy. This tool is extremely useful for both students and teachers. Basically, Packet Tracerallows you to build a network with a range of simulated “real-life” equipment (Cisco equipment, of course), so different configuration options can be tested. You get a range of routers, switches, end-client systems and connections to build the simulated network. The operating systems of the routers and even some portions of PC’s are also simulated. This way, users can learn to configure routers and see the changes they make on the networks.</p>
<p>Teachers can even make an interactive test using the program, which can be graded immediately by the program. It is one of the most complete tools for network learning; however, it can also help simulate and assess equipment options for real networks. It is really a tool to have; however, in order to download it from the original site, you need a Cisco Academy account, but the program has a free license.</p>
<p><a rel="attachment wp-att-130" href="http://www.siriuspackets.com/2009/10/01/cisco-packet-tracer-51-download/packettracer51_setupexe/">packettracer51_setupexe</a> educational purposes only. download</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/10/01/cisco-packet-tracer-51-download/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Configuring DHCP Snooping on a Catalyst 6500 IOS</title>
		<link>http://www.siriuspackets.com/2009/07/29/configuring-dhcp-snooping-on-a-catalyst-6500-ios/</link>
		<comments>http://www.siriuspackets.com/2009/07/29/configuring-dhcp-snooping-on-a-catalyst-6500-ios/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 00:55:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=125</guid>
		<description><![CDATA[To be posted 07/31. The proper way to configure this!
]]></description>
			<content:encoded><![CDATA[<p>To be posted 07/31. The proper way to configure this!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/07/29/configuring-dhcp-snooping-on-a-catalyst-6500-ios/feed/</wfw:commentRss>
		</item>
		<item>
		<title>EIGRP Formula: Calculation Method for Composite Metric</title>
		<link>http://www.siriuspackets.com/2009/04/17/eigrp-formula-calculation-method-for-composite-metric/</link>
		<comments>http://www.siriuspackets.com/2009/04/17/eigrp-formula-calculation-method-for-composite-metric/#comments</comments>
		<pubDate>Fri, 17 Apr 2009 14:50:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<category><![CDATA[IP Routing]]></category>

		<category><![CDATA[change default eigrp]]></category>

		<category><![CDATA[dual algorithm]]></category>

		<category><![CDATA[eigrp formula]]></category>

		<category><![CDATA[eigrp k values]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=116</guid>
		<description><![CDATA[There have been many posts on the Internet explaining how EIGRP gets its composite metric. I&#8217;ve been running around searching for information and it seems that there are NOT that many people who seem to post this info. Here it is, the real calculation method for EIGRP metrics.
Everyone says EIGRP metric is based off bandwidth [...]]]></description>
			<content:encoded><![CDATA[<p>There have been many posts on the Internet explaining how EIGRP gets its composite metric. I&#8217;ve been running around searching for information and it seems that there are NOT that many people who seem to post this info. Here it is, the real calculation method for EIGRP metrics.</p>
<p>Everyone says EIGRP metric is based off bandwidth (BW) and delay (DLY), which are values determined &#8220;per-interface&#8221; as shown below in bold:</p>
<p><strong>EIGRP Algorithm / Formula:<br />
</strong> Composite Metric = 256 * ([K1 * BW + K2 * BW/(256-Load) + K3 * DLY] * [K5/(RELY + K4)])</p>
<p>Default EIGRP K-Values are K1=1, K2=0, K3=1, K4=0, K5=0.  To modify the or change the K values for calculation to include the other non-default variables you input the command below:</p>
<p style="text-align: center;"><strong><span style="text-decoration: underline;"><span style="color: #ff0000;">What they don&#8217;t really emphasize and its important for the formula!</span></span></strong></p>
<p style="text-align: left;"><span><span style="color: #000000;">The bandwidth (BW) and delay (DLY) values are based on a &#8220;scaled average&#8221;.</span></span></p>
<p style="text-align: left;"><span><span style="color: #000000;">Bandwidth for EIGRP = (10<sup>7</sup> / Interface Bandwidth)<br />
Delay for EIGRP = (Interface Delay in usec / 10)</span></span></p>
<blockquote>
<p style="text-align: left;"><span><span style="color: #000000;">So the formula ends up being Metric = 256( (10,000,000/ BW) + (DELAY/10)).<br />
To modify any EIGRP K-values to use more variables, enter command shown below:</span></span></p>
<p style="text-align: left;"><span><span style="color: #000000;"><br />
</span></span></p></blockquote>
<blockquote>
<p style="text-align: left;"><span><span style="color: #000000;">CRNARVSDRR02(config-router)#metric weights ?<br />
&lt;0-8&gt;  Type Of Service (Only TOS 0 supported)</span></span></p>
<p>CRNARVSDRR02(config-router)#metric weights 0 ?<br />
&lt;0-255&gt;  K1</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 ?<br />
&lt;0-255&gt;  K2</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 0 ?<br />
&lt;0-255&gt;  K3</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 0 1 ?<br />
&lt;0-255&gt;  K4</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 0 1 0 ?<br />
&lt;0-255&gt;  K5</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 0 1 0 0 ?<br />
&lt;cr&gt;</p>
<p>CRNARVSDRR02(config-router)#metric weights 0 1 0 1 0 0</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/04/17/eigrp-formula-calculation-method-for-composite-metric/feed/</wfw:commentRss>
		</item>
		<item>
		<title>MPLS with WCCP do not mix!</title>
		<link>http://www.siriuspackets.com/2009/03/28/mpls-with-wccp-do-not-mix/</link>
		<comments>http://www.siriuspackets.com/2009/03/28/mpls-with-wccp-do-not-mix/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 13:29:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[General]]></category>

		<category><![CDATA[MPLS]]></category>

		<category><![CDATA[WAN Acceleration]]></category>

		<category><![CDATA[mpls data center]]></category>

		<category><![CDATA[mpls switching]]></category>

		<category><![CDATA[mpls te]]></category>

		<category><![CDATA[wae]]></category>

		<category><![CDATA[wae hardware wccp]]></category>

		<category><![CDATA[wan acceleration]]></category>

		<category><![CDATA[wccp]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=103</guid>
		<description><![CDATA[Problem:
So I was working on implementing WCCP redirection for networks to get TCP accelerated between two data centers and I ran into a problem. The problem was that subnets behind the core switches were not getting WCCP redirected into the WAAS units. So I wonder why? It&#8217;s matching the redirect-list ACL and shows up in [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Problem:</strong><br />
So I was working on implementing WCCP redirection for networks to get TCP accelerated between two data centers and I ran into a problem. The problem was that subnets behind the core switches were not getting WCCP redirected into the WAAS units. So I wonder why? It&#8217;s matching the redirect-list ACL and shows up in the ACL hit counters. Subnets directly connected on the CORE switch was getting accelerated fine, I saw TFO matches in the WAE-7371s but any subnet behind in the ACCESS switches were NOT getting accelerated. They were still in PT: pass-through. So I said to myself, wtf?!</p>
<p>After a few hours of thinking in my private office with a magazine, I realized&#8230; crap, this is an MPLS-enabled data center&#8230; from source IP: 10.10.12.0/24 to destination: 10.20.20.0/24 is applied an MPLS label and switched instead of IP routed towards the destined network.</p>
<div id="attachment_107" class="wp-caption alignleft" style="width: 567px"><img class="size-full wp-image-107" title="MPLS Shim Header" src="http://www.siriuspackets.com/wp-content/uploads/2009/03/mpls_shim_header.gif" alt="MPLS Shim Header" width="557" height="224" /><p class="wp-caption-text">MPLS Shim Header</p></div>
<p>So that means there is an extra SHIM HEADER between L2 and L3&#8230; if WCCP gets redirected based on IP, then uhh&#8230; crap, it never will see the IP header because the CORE is reading the MPLS LABEL when the ACCESS pushed a label as the IP packet came ingress into VLAN12 on ACCESS switches. Bingo!!! This was the reason why WCCP wasn&#8217;t redirecting anything behind my CORE switches in the data center.</p>
<p><strong>Solution:</strong> I had to remove MPLS-TE paths from source 10.10.12.0/24 towards 10.20.20.0/24 with a special policy, everything else gets label switched as usual. I really hate doing these &#8220;one-off&#8221; type configurations but it was the only way I could get WCCP working to the WAAS units in an MPLS enabled data center environment.  I really do hope Cisco IOS supports MPLS labels in WCCP in the future&#8230;. After my fix, I was successfully seeing &#8220;optimized&#8221; connections in both source/destination WAAS boxes. No more MPLS shim header, so WCCP was able to read the IP header to redirect transparently.</p>
<p> </p>
<div id="attachment_111" class="wp-caption alignleft" style="width: 592px"><img class="size-full wp-image-111" title="WAAS and MPLS Enabled Data Center" src="http://www.siriuspackets.com/wp-content/uploads/2009/03/waas-mpls-datacenter1.jpg" alt="WAAS with MPLS-enabled Data Center" width="582" height="660" /><p class="wp-caption-text">WAAS with MPLS-enabled Data Center</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/28/mpls-with-wccp-do-not-mix/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Another SIP CME Configuration</title>
		<link>http://www.siriuspackets.com/2009/03/28/sip-cme-configuration/</link>
		<comments>http://www.siriuspackets.com/2009/03/28/sip-cme-configuration/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 11:53:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[VoIP]]></category>

		<category><![CDATA[cme sample config]]></category>

		<category><![CDATA[sip cme config]]></category>

		<category><![CDATA[sip trunk config]]></category>

		<category><![CDATA[sip trunk sample]]></category>

		<category><![CDATA[sip trunking cisco]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=74</guid>
		<description><![CDATA[CME - CLI Config
This is a sample CLI configuration for Call Manager Express (CME).
Please make sure to setup all of the local functionality of the CME before trying to setup the SIP Trunks.
When you are ready to setup the SIP trunks, the first thing you wll need to do is setup a translation rule. The [...]]]></description>
			<content:encoded><![CDATA[<p>CME - CLI Config<br />
This is a sample CLI configuration for Call Manager Express (CME).</p>
<p>Please make sure to setup all of the local functionality of the CME before trying to setup the SIP Trunks.</p>
<p>When you are ready to setup the SIP trunks, the first thing you wll need to do is setup a translation rule. The translation rule will help you structure how outbound calls are dialed and sent to any 3rd Party SIP provider for trunking services. Read on&#8230;</p>
<p><span id="more-74"></span></p>
<p>Translation Rule:</p>
<blockquote><p>voice translation-rule 3<br />
rule 1 /^9\(&#8230;&#8230;.\)$/ /+1626\1/<br />
!&#8211; Local Calling &#8220;626&#8243; is the local area code<br />
rule 2 /^9\(&#8230;&#8230;&#8230;.\)$/ /+1\1/<br />
!&#8211; 10 Digit Calling adds &#8220;+1&#8243;<br />
rule 3 /^9\(.*\)$/ /+\1/<br />
!&#8211;  11 Digit Dialing adds &#8220;+&#8221;<br />
rule 4 /^9\(&#8230;&#8230;&#8230;..\)$/ /+\1/<br />
!&#8211;  Catch-all<br />
rule 5 /^9011\(.*\)$/ /+\1/<br />
!&#8211;  International Dialing strips the &#8220;011&#8243; and adds &#8220;+&#8221;</p></blockquote>
<p>Configuration of a translation-profile that ties a multiple translation-rule behavior</p>
<p>Translation-Profile:<br />
(I&#8217;m still testing this. there is a difference between &#8220;translation-rule&#8221; and &#8220;voice translation-rule&#8221; commands for voip-to-voip vs. voip-to-pots)</p>
<blockquote><p>voice translation-profile SIP-OUTBOUND<br />
translate calling 2<br />
translate called 1<br />
translate redirect-target 3<br />
translate redirect-called 3</p></blockquote>
<p>The Dial-Peer is next. It is where the acctual trunk information is setup.</p>
<p>Dial-Peer:</p>
<blockquote><p>dial-peer voice 1 voip<br />
description ** Outgoinging call to SIP trunk **<br />
translation-profile outgoing SIP-OUTBOUND<br />
destination-pattern 9[2-9]&#8230;&#8230;T<br />
voice-class codec 1<br />
!&#8211; force dial-tones to pass inband in the SIP control channel, otherwise the tones don&#8217;t get sent across properly for IVRs &#8211;!<br />
voice-class sip dtmf-relay force rtp-nte<br />
session protocol sipv2<br />
session target ipv4:216.82.224.202<br />
!&#8211; This is the IP address of your SIP provider&#8217;s server (bandwidth.com, etc) &#8211;!<br />
dtmf-relay rtp-nte<br />
ip qos dscp cs5 media<br />
ip qos dscp cs4 signaling<br />
clid network-number 6265551212<br />
!&#8211; This is how you setup for a global outbound callerID, only if your SIP provider allows &#8211;!<br />
no vad</p></blockquote>
<p>Now here is a sample of how to configure a user phone:</p>
<blockquote><p>ephone-dn 1 dual-line<br />
number 1212 secondary +16265551212<br />
!&#8211; Make sure you insert the &#8220;+1&#8243; into the number in order to recognize inbound calls. &#8211;!<br />
label 6265551212<br />
description Temp User<br />
name Temp User<br />
call-forward noan 6000<br />
!&#8211; timeout 10 This is to call FWD no Answer to VM @ extension 6000 &#8211;!<br />
corlist incoming user900-international</p></blockquote>
<p>SIP User Agent:<br />
Registration to the SIP proxy server &#8211;</p>
<blockquote><p>sip-ua<br />
! &#8212; authentication to for SIP registration &#8211;!<br />
credentials username  password  realm<br />
! &#8212; authentication for SIP proxy when connecting calls &#8211;!<br />
authentication username  password  realm<br />
no remote-party-id<br />
! &#8212; optional: this line below tells your SIP server the caller-id to send to the called number  &#8211;!<br />
calling-info sip-to-pstn number set<br />
! &#8212; optional: what is received on YOUR IP phone&#8217;s caller-id display for incoming calls from SIP server &#8211;!<br />
! &#8212; note: if you set these calling-info commands, it rewrites the caller-id info so you won&#8217;t see who&#8217;s the original caller &#8211;!<br />
calling-info pstn-to-sip from number set<br />
retry invite 2<br />
retry register 10<br />
timers connect 100<br />
registrar dns:sip3.voipvoip.com expires 3600<br />
sip-server dns:sip3.voipvoip.com<br />
notify telephone-event max-duration 500<br />
host-registrar<br />
presence enable</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/28/sip-cme-configuration/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ASA 5500 SSL VPN LDAP Authentication</title>
		<link>http://www.siriuspackets.com/2009/03/28/asa-5500-ssl-vpn-ldap-authentication/</link>
		<comments>http://www.siriuspackets.com/2009/03/28/asa-5500-ssl-vpn-ldap-authentication/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 11:48:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Security]]></category>

		<category><![CDATA[anyconnect]]></category>

		<category><![CDATA[asa]]></category>

		<category><![CDATA[authentication]]></category>

		<category><![CDATA[ldap]]></category>

		<category><![CDATA[ssl vpn]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=81</guid>
		<description><![CDATA[In this post I demonstrate how to configure the Cisco Adaptive Security Appliance (ASA) to use an LDAP server for authentication of WebVPN users. The LDAP server in this example is Microsoft Active Directory. In this example Lightweight Directory Access Protocol (LDAP) authentication is configured for WebVPN users, but this configuration can be used for [...]]]></description>
			<content:encoded><![CDATA[<p>In this post I demonstrate how to configure the Cisco Adaptive Security Appliance (ASA) to use an LDAP server for authentication of WebVPN users. The LDAP server in this example is Microsoft Active Directory. In this example Lightweight Directory Access Protocol (LDAP) authentication is configured for WebVPN users, but this configuration can be used for all other types of remote access clients as well. Simply assign the AAA server group to the desired connection profile (tunnel group). <br />
Ok if you want to use AD we must use LDAP and in some cases we will have to configure an LDAP attribute-map…I have put together a sample config you can use. It’s a sample ldap aaa-server configuration. I put a (#x) where there is something you need to modify to be specific to your environment. There is an explanation for each number below. Read on&#8230;.</p>
<p><span id="more-81"></span></p>
<blockquote><p>aaa-server cisco protocol ldap aaa-server cisco host 192.168.10.100 (#1)   ldap-base-dn DC=yourdomainname,DC=com (#2)   ldap-scope subtree   ldap-naming-attribute samAccountName   ldap-login-password adminpass (#3)   ldap-login-dn CN=Administrator,CN=users,DC=yourdomainname,DC=com (#4)<br />
tunnel-group mytunnelgroup general-attributes   authentication-server-group cisco (#5)</p></blockquote>
<p>#1 - replace 192.168.10.100 with the ip address of your aaa-server<br />
#2 - this is where the asa is going to start its search for users it needs to authenticate. In my example we start at the top of the heirarchy (yourdomainname.com)<br />
#3 - you need to have an administrative user setup on you AD so that we can bind with the AD and send user authentication requests. This is the password the admin user has.<br />
#4 - This is the complete string of the admin user. To get the complete string go to the AD box, open a command prompt and run the dsquery command on the admin username (the asterisks broaden the search) dsquery user -name *Administrator*<br />
#5 - replace mytunnelgroup with the name of your vpn tunnel-group<br />
Now authentication is done via group attributes in AD in most instances via the dialin attributes msallowdialin attribute and using tunneling protocols attribute but I have some customers that would like to use the memberof attribute instead so that they can prevent members of other AD groups from connecting to the ASA…this can be done using LDAP schema 65 attribute mapping…for instance…the ASA/PIX uses the Cisco LDAP attribute ASA5505-IETF-Radius-Class to enforce policies from a specific group-policy for Remote Access VPN sessions (IPSec, SVC, WebVPN or Clientless). The LDAP attribute (65) is equivalent to Radius Class (25) attribute.<br />
On the ASA create an ldap-attribute-map with  the minimum mapping and associate it with the ldap aaa-server.</p>
<blockquote><p>5500-1(config-aaa-server-host)# show runn ldap ! ldap attribute-map Map1 map-name  memberOf ASA5505-IETF-Radius-Class map-value memberOf CN=AD-Group1,CN=Users,DC=CompanyA,DC=com ASA-Group1-Allow-Access map-value memberOf CN=AD-Group2,CN=Users,DC=CompanyA,DC=com ASA-Group2-Deny-Access ! 5500-1(config-aaa-server-host)# </p></blockquote>
<p>OK so what is being enforced with the above mapping?<br />
1) user1 in AD group AD-Group1 will be placed-landed on ASA group-policy ASA-Group1-Allow-Access. In this ASA group then you can set vpn-tunnel-protocol to allow only svc and webvpn types for example.<br />
2) user2 in AD group AD-Group2 will be placed-landed on ASA group-policy ASA-Group2-Deny-Access. In this ASA group then you can set vpn-tunnel-protocol to allow only ipsec types for example. Therefore svc/webvpn types would be disallowed.<br />
Note: If the AD user is part of multiple AD groups, make sure the AD user’s memberof/group of interest is at the top of the list ,since as of 7.2.x , the appliance only enforces the 1st memberOf attribute that is parsed. The single AD group (memberOf) limitation has been removed in 8.0 where the ASA is able to make policy decisions based on multiple AD groups.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/28/asa-5500-ssl-vpn-ldap-authentication/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Call Manager Express to 3rd Party SIP Provider Sample Configuration</title>
		<link>http://www.siriuspackets.com/2009/03/22/call-manager-express-to-3rd-party-sip-provider-sample-configuration/</link>
		<comments>http://www.siriuspackets.com/2009/03/22/call-manager-express-to-3rd-party-sip-provider-sample-configuration/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 01:24:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[VoIP]]></category>

		<category><![CDATA[call manager express]]></category>

		<category><![CDATA[cisco sip cme]]></category>

		<category><![CDATA[cme]]></category>

		<category><![CDATA[cme config]]></category>

		<category><![CDATA[SIP]]></category>

		<category><![CDATA[sip trunk config]]></category>

		<category><![CDATA[sip trunk sample]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=58</guid>
		<description><![CDATA[This took me about 8-12 hours to figure out (considering I don&#8217;t really have voip experience), but I recently canceled one of my consulting contracts where I was using EasyVPN client on my home 2811 and terminated into one of my consulting client&#8217;s Cisco VPNc3000 concentrator for Call Manager 4.3 communication for my IP phones [...]]]></description>
			<content:encoded><![CDATA[<p>This took me about 8-12 hours to figure out (considering I don&#8217;t really have voip experience), but I recently canceled one of my consulting contracts where I was using EasyVPN client on my home 2811 and terminated into one of my consulting client&#8217;s Cisco VPNc3000 concentrator for Call Manager 4.3 communication for my IP phones at home. Yes I was getting free phone service! Bad news, I was constantly on-call <img src='http://www.siriuspackets.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  </p>
<p>So since I am not consulting there anymore, I wasn&#8217;t able to get IP phone service anymore. My connection to their Cisco Call Manager box was about to be terminated&#8230; what do I do now I ask myself. I still want to use Cisco VoIP at home because I had a nice intercom and paging system so I didn&#8217;t have to scream for my girlfriend across the house to bring my food over to the office.  So I did some research and seen some things about low cost or even free SIP service.  I ended up going with a SIP provider from &#8220;voipvoip.com&#8221; because they were offering $6.95/month BYOD (bring your own device) which I had my trusty Cisco 2811 that included <em>unlimited incoming</em> minutes and <em>1.9 cents/minute outbound</em>.  The KEY part I wanted was having simultaneous channels inbound and outbound so I can have conference bridges with my Cisco MeetingPlace Express server I will be setting up later.  I was allowed up to 2 channels incoming and 4 channels outgoing. Cool right?  So its a typical pay-as-you-go plan&#8230; I will start off with this and see how my monthly bills are later. </p>
<p>Heres the problem&#8230;. as I was browsing the company support pages, I noticed there weren&#8217;t any configuration guides for CISCO. There was stuff for Asterisk, TrixBox, 3CX, and a few others such as SIP phones, etc.   Then I thought, no problem&#8230; I will google this and find some sample configurations to a 3rd party SIP proxy server with some sample dial-peer templates and Im good to go.   A few hours later, I discovered that (1) this sample config does not exist or (2) it is really difficult to find perhaps because not many people do this? or (3) I just really stink in googling.  I like to think it is #1 and #2.   </p>
<p>So here is my sample configuration that I have implemented to help those that are looking for or wanting a similar setup with Call Manager Express.<br />
I am running CME 7.1 and am in process of setting up my Cisco Unity Express NM (NM-CUE) module with a Cisco MeetingPlace Express server. I will definitely write about that as I configure those in the weeks ahead.</p>
<p><span id="more-58"></span></p>
<div id="attachment_98" class="wp-caption alignleft" style="width: 753px"><img class="size-full wp-image-98 " title="SIP VoIP Network" src="http://www.siriuspackets.com/wp-content/uploads/2009/03/voip-network.jpg" alt="SIP VoIP Network" width="743" height="302" /><p class="wp-caption-text">SIP VoIP Network</p></div>
<blockquote><p>Current configuration : 15683 bytes<br />
!<br />
! Last configuration change at 17:27:51 PDT Sun Mar 22 2009<br />
! NVRAM config last updated at 17:27:52 PDT Sun Mar 22 2009<br />
!<br />
version 12.4<br />
service nagle<br />
service tcp-keepalives-in<br />
service tcp-keepalives-out<br />
service timestamps debug datetime localtime show-timezone<br />
service timestamps log datetime localtime show-timezone<br />
service password-encryption<br />
service linenumber<br />
!<br />
hostname CME-2811-ROUTER<br />
!<br />
boot-start-marker<br />
boot-end-marker<br />
!<br />
logging message-counter syslog<br />
logging buffered 32768<br />
enable secret 5<br />
!<br />
no aaa new-model<br />
clock timezone PDT -7<br />
!<br />
dot11 syslog<br />
no ip source-route<br />
!<br />
!<br />
ip cef<br />
no ip dhcp use vrf connected<br />
ip dhcp excluded-address 192.168.11.1 192.168.11.64<br />
ip dhcp excluded-address 192.168.11.240 192.168.11.255<br />
ip dhcp excluded-address 192.168.10.1 192.168.10.64<br />
ip dhcp excluded-address 192.168.10.240 192.168.10.255<br />
!<br />
ip dhcp pool WIRELESS-DHCP<br />
import all<br />
network 192.168.11.0 255.255.255.0<br />
update dns both<br />
default-router 192.168.11.1<br />
dns-server 68.238.64.12 68.238.128.12<br />
option 150 ip 10.1.231.1<br />
!<br />
ip dhcp pool INTERNAL-DHCP<br />
import all<br />
network 192.168.10.0 255.255.255.0<br />
update dns both<br />
default-router 192.168.10.1<br />
option 150 ip 10.1.231.1<br />
dns-server 68.238.64.12 68.238.128.12<br />
!<br />
!<br />
ip domain name siriuspackets.com<br />
ip name-server 4.2.2.4<br />
ip name-server 68.238.64.12<br />
ip multicast-routing<br />
ip multicast multipath<br />
no ipv6 cef<br />
ntp source FastEthernet0/1<br />
ntp update-calendar<br />
ntp server ntp-01.caltech.edu<br />
ntp server time7.apple.com<br />
!<br />
multilink bundle-name authenticated<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
voice service voip<br />
allow-connections h323 to h323<br />
allow-connections h323 to sip<br />
allow-connections sip to h323<br />
allow-connections sip to sip<br />
no supplementary-service sip moved-temporarily<br />
no supplementary-service sip refer<br />
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco<br />
!<br />
!<br />
!<br />
voice class codec 1<br />
codec preference 1 g711ulaw<br />
codec preference 2 g729r8<br />
codec preference 3 g711alaw<br />
codec preference 4 g729br8<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
!<br />
voice hunt-group 1 parallel<br />
final 6000<br />
list 801,802,803,804,805,806,807,808<br />
timeout 20<br />
pilot 800<br />
!<br />
!<br />
!<br />
voice translation-rule 1<br />
rule 1 /^911$/ /911/<br />
rule 2 /^9(.*)/ /1/<br />
!<br />
voice translation-rule 2<br />
rule 1 /^.*/ /5551234567/<br />
!<br />
!<br />
voice translation-profile PSTN-FORWARDING<br />
translate redirect-target 3<br />
translate redirect-called 3<br />
!<br />
voice translation-profile PSTN-OUTGOING<br />
translate calling 2<br />
translate called 1<br />
translate redirect-target 3<br />
translate redirect-called 3<br />
!<br />
!<br />
voice-card 0<br />
!<br />
!<br />
!<br />
!<br />
!<br />
archive<br />
log config<br />
hidekeys<br />
!<br />
!<br />
crypto ipsec transform-set TS-IPSEC-SET esp-aes esp-sha-hmac<br />
!<br />
!<br />
!<br />
!<br />
ip telnet source-interface FastEthernet0/1<br />
ip ftp source-interface FastEthernet0/1<br />
ip tftp source-interface FastEthernet0/1<br />
ip ssh version 2<br />
!<br />
class-map match-any CM-CRITICAL-APPS<br />
match access-group 2000<br />
class-map match-any CM-VOICE-CONTROL<br />
match  dscp cs3<br />
match  dscp cs5<br />
match ip dscp af31<br />
match ip dscp af32<br />
class-map match-any CM-CRITICAL-DATA1<br />
match  dscp af42<br />
match protocol ipsec<br />
class-map match-any CM-CRITICAL-DATA2<br />
match  dscp af43<br />
class-map match-any CM-NETWORK-MGMT<br />
match protocol icmp<br />
match protocol telnet<br />
class-map match-any CM-VOICE<br />
match  dscp ef<br />
match ip dscp cs5<br />
match ip dscp ef<br />
!<br />
!<br />
policy-map PM-WAN-EDGE-OUT<br />
class CM-VOICE<br />
priority percent 30<br />
class CM-VOICE-CONTROL<br />
bandwidth percent 10<br />
class CM-CRITICAL-DATA1<br />
bandwidth percent 20<br />
random-detect dscp-based<br />
class CM-CRITICAL-DATA2<br />
bandwidth percent 36<br />
random-detect dscp-based<br />
class class-default<br />
fair-queue<br />
random-detect<br />
policy-map PM-LAN-EDGE-IN<br />
class CM-NETWORK-MGMT<br />
set dscp af42<br />
class CM-CRITICAL-APPS<br />
set dscp af43<br />
class CM-VOICE<br />
class CM-VOICE-CONTROL<br />
class class-default<br />
set dscp default<br />
!<br />
!<br />
translation-rule 3<br />
Rule 1 ^91&#8230;&#8230;. 1<br />
Rule 2 9&#8230;&#8230; 1626<br />
Rule 3 6000 6265551212<br />
!<br />
!<br />
!<br />
!<br />
!<br />
interface Loopback0<br />
ip address 10.1.231.1 255.255.255.255<br />
ip pim sparse-mode<br />
!<br />
interface FastEthernet0/0<br />
ip address 192.168.10.1 255.255.255.0<br />
ip flow ingress<br />
ip pim sparse-mode<br />
ip nat inside<br />
ip virtual-reassembly<br />
load-interval 30<br />
duplex auto<br />
speed auto<br />
service-policy input PM-LAN-EDGE-IN<br />
!<br />
interface FastEthernet0/0.10<br />
encapsulation dot1Q 10<br />
ip address 192.168.11.1 255.255.255.0<br />
ip flow ingress<br />
ip pim sparse-mode<br />
ip nat inside<br />
ip virtual-reassembly<br />
!<br />
interface FastEthernet0/1<br />
bandwidth 25000<br />
ip address dhcp<br />
no ip proxy-arp<br />
ip nbar protocol-discovery<br />
ip pim sparse-mode<br />
ip nat outside<br />
ip virtual-reassembly<br />
ip igmp query-interval 5<br />
load-interval 30<br />
duplex auto<br />
speed auto<br />
max-reserved-bandwidth 100<br />
service-policy output PM-WAN-EDGE-OUT<br />
!<br />
router rip<br />
version 2<br />
passive-interface FastEthernet0/0<br />
passive-interface FastEthernet0/0.10<br />
network 192.168.1.0<br />
network 192.168.10.0<br />
network 192.168.11.0<br />
maximum-paths 16<br />
no auto-summary<br />
!<br />
ip default-gateway 192.168.1.1<br />
ip forward-protocol nd<br />
ip http server<br />
ip http access-class 10<br />
no ip http secure-server<br />
ip http path flash:/gui<br />
!<br />
!<br />
no ip pim dm-fallback<br />
ip pim send-rp-announce Loopback0 scope 16<br />
ip pim send-rp-discovery Loopback0 scope 16<br />
ip nat inside source list INTERNAL-NET interface FastEthernet0/1 overload<br />
!<br />
!<br />
ip access-list extended INTERNAL-NET<br />
permit ip 192.168.10.0 0.0.0.255 any<br />
permit ip 192.168.11.0 0.0.0.255 any<br />
!<br />
access-list 2000 remark //PERMIT-QOS-CRITICAL-APPS//<br />
access-list 2000 permit tcp any any eq 3389<br />
access-list 2000 permit tcp any any eq telnet<br />
access-list 2000 permit tcp any any eq 22<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 10.0.0.0 0.255.255.255<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 192.168.254.0 0.0.0.255<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 192.168.255.0 0.0.0.255<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 172.16.0.0 0.0.255.255<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 172.200.0.0 0.0.255.255<br />
access-list 2500 permit ip 192.168.10.0 0.0.0.255 224.0.0.0 15.255.255.255<br />
access-list 2500 permit ip 192.168.11.0 0.0.0.255 10.0.0.0 0.255.255.255<br />
access-list 2500 permit ip 192.168.11.0 0.0.0.255 224.0.0.0 15.255.255.255<br />
!<br />
!<br />
!<br />
!<br />
!<br />
tftp-server flash:apps75.8-4-1-23.sbn<br />
tftp-server flash:cnu75.8-4-1-23.sbn<br />
tftp-server flash:cvm75sccp.8-4-1-23.sbn<br />
tftp-server flash:dsp75.8-4-1-23.sbn<br />
tftp-server flash:jar75sccp.8-4-1-23.sbn<br />
tftp-server flash:SCCP75.8-4-2S.loads<br />
tftp-server flash:term61.default.loads<br />
tftp-server flash:WLAN-1.2.1.SBN<br />
tftp-server flash:TNUX-1.2.1.SBN<br />
tftp-server flash:TNUXR-1.2.1.SBN<br />
tftp-server flash:APPS-1.2.1.SBN<br />
tftp-server flash:GUI-1.2.1.SBN<br />
tftp-server flash:SYS-1.2.1.SBN<br />
tftp-server flash:term75.default.loads<br />
tftp-server flash:CP7921G-1.2.1.LOADS<br />
tftp-server flash:Desktops/320&#215;212x12/List.xml<br />
tftp-server flash:Desktops/320&#215;212x12/CampusNight.png<br />
tftp-server flash:Desktops/320&#215;212x12/CiscoFountain.png<br />
tftp-server flash:Desktops/320&#215;212x12/MorroRock.png<br />
tftp-server flash:Desktops/320&#215;212x12/NantucketFlowers.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-CampusNight.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-CiscoFountain.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-Fountain.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-MorroRock.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-NantucketFlowers.png<br />
tftp-server flash:Desktops/320&#215;212x12/Fountain.png<br />
tftp-server flash:Desktops/320&#215;212x12/CiscoLogo.png<br />
tftp-server flash:Desktops/320&#215;212x12/TN-CiscoLogo.png<br />
tftp-server flash:Desktops/320&#215;216x16/List.xml<br />
tftp-server flash:Desktops/320&#215;212x16/List.xml<br />
tftp-server flash:gui/admin_user.html<br />
tftp-server flash:gui/admin_user.js<br />
tftp-server flash:gui/CiscoLogo.gif<br />
tftp-server flash:gui/Delete.gif<br />
tftp-server flash:gui/dom.js<br />
tftp-server flash:gui/downarrow.gif<br />
tftp-server flash:gui/ephone_admin.html<br />
tftp-server flash:gui/logohome.gif<br />
tftp-server flash:gui/normal_user.html<br />
tftp-server flash:gui/normal_user.js<br />
tftp-server flash:gui/Plus.gif<br />
tftp-server flash:gui/sxiconad.gif<br />
tftp-server flash:gui/Tab.gif<br />
tftp-server flash:gui/telephony_service.html<br />
tftp-server flash:gui/uparrow.gif<br />
tftp-server flash:gui/xml-test.html<br />
tftp-server flash:gui/xml.template<br />
tftp-server flash:apps37sccp.1-2-1-0.bin<br />
tftp-server flash:APPSH-1.3.1.SBN<br />
tftp-server flash:GUIH-1.3.1.SBN<br />
tftp-server flash:CP7925G-1.3.1.LOADS<br />
tftp-server flash:SYSH-1.3.1.SBN<br />
tftp-server flash:TNUXH-1.3.1.SBN<br />
tftp-server flash:WLANH-1.3.1.SBN<br />
tftp-server flash:Analog1.raw<br />
tftp-server flash:Analog2.raw<br />
tftp-server flash:AreYouThere.raw<br />
tftp-server flash:AreYouThereF.raw<br />
tftp-server flash:Bass.raw<br />
tftp-server flash:CallBack.raw<br />
tftp-server flash:Chime.raw<br />
tftp-server flash:Classic1.raw<br />
tftp-server flash:Classic2.raw<br />
tftp-server flash:ClockShop.raw<br />
tftp-server flash:DistinctiveRingList.xml<br />
tftp-server flash:Drums1.raw<br />
tftp-server flash:Drums2.raw<br />
tftp-server flash:FilmScore.raw<br />
tftp-server flash:HarpSynth.raw<br />
tftp-server flash:Jamaica.raw<br />
tftp-server flash:KotoEffect.raw<br />
tftp-server flash:MusicBox.raw<br />
tftp-server flash:Piano1.raw<br />
tftp-server flash:Piano2.raw<br />
tftp-server flash:Pop.raw<br />
tftp-server flash:Pulse1.raw<br />
tftp-server flash:Ring1.raw<br />
tftp-server flash:Ring2.raw<br />
tftp-server flash:Ring3.raw<br />
tftp-server flash:Ring4.raw<br />
tftp-server flash:Ring5.raw<br />
tftp-server flash:Ring6.raw<br />
tftp-server flash:Ring7.raw<br />
tftp-server flash:RingList.xml<br />
tftp-server flash:Sax1.raw<br />
tftp-server flash:Sax2.raw<br />
tftp-server flash:Vibe.raw<br />
!<br />
control-plane<br />
!<br />
!<br />
!<br />
!<br />
mgcp fax t38 ecm<br />
!<br />
!<br />
!<br />
dial-peer voice 4 voip<br />
description ==INTERNATIONAL CALL TO SIP TRUNK==<br />
translation-profile outgoing PSTN-CALLFORWARDING<br />
destination-pattern 9011T<br />
voice-class codec 1<br />
voice-class sip dtmf-relay force rtp-nte<br />
session protocol sipv2<br />
session target sip-server<br />
dtmf-relay rtp-nte<br />
no vad<br />
!<br />
dial-peer voice 5 voip<br />
description ==STAR CODE TO SIP TRUNK==<br />
translation-profile outgoing PSTN-CALLFORWARDING<br />
destination-pattern *..<br />
voice-class codec 1<br />
voice-class sip dtmf-relay force rtp-nte<br />
session protocol sipv2<br />
session target sip-server<br />
dtmf-relay rtp-nte<br />
no vad<br />
!<br />
dial-peer voice 1 voip<br />
description ==OUTGOING CALL TO SIP TRUNK==<br />
translation-profile outgoing PSTN-OUTGOING<br />
destination-pattern 9[0-1][2-9]..[2-9]&#8230;&#8230;<br />
translate-outgoing called 3<br />
voice-class codec 1<br />
voice-class sip dtmf-relay force rtp-nte<br />
session protocol sipv2<br />
session target sip-server<br />
dtmf-relay rtp-nte<br />
ip qos dscp cs5 media<br />
ip qos dscp cs5 signaling<br />
no vad<br />
!<br />
dial-peer voice 2 voip<br />
description ==OUTGOING CALL TO SIP TRUNK=<br />
translation-profile outgoing PSTN-OUTGOING<br />
destination-pattern 9[2-9]..[2-9]&#8230;&#8230;<br />
voice-class codec 1<br />
voice-class sip dtmf-relay force rtp-nte<br />
session protocol sipv2<br />
session target sip-server<br />
dtmf-relay rtp-nte<br />
no vad<br />
!<br />
!<br />
num-exp 5551234567 800<br />
sip-ua<br />
! &#8212; for authenticating to the SIP server to do initial registration &#8211;!<br />
credentials username 5551234567 password 7<br />
realm sip3.voipvoip.com<br />
! &#8212; for SIP proxy authentication while making outbound calls &#8211;!<br />
authentication username 5551234567 password 7<br />
realm sip3.voipvoip.com<br />
! &#8212; optional: to hard code your caller-id when you call outbound &#8211;!<br />
calling-info sip-to-pstn number set 5551234567<br />
! &#8212; optional: to hard code caller-id received from incoming calls &#8211;!<br />
calling-info pstn-to-sip from number set 5551234567<br />
no remote-party-id<br />
retry invite 2<br />
retry register 10<br />
timers connect 100<br />
! &#8212; specifying sip registration server here &#8211;!<br />
registrar dns:sip3.voipvoip.com expires 3600<br />
! &#8212; specifying the actual SIP server you are registering to for calls &#8211;!<br />
sip-server dns:sip3.voipvoip.com<br />
notify telephone-event max-duration 500<br />
host-registrar<br />
presence enable<br />
!<br />
!<br />
!<br />
telephony-service<br />
max-ephones 12<br />
max-dn 32<br />
ip source-address 10.1.231.1 port 2000<br />
auto assign 1 to 12<br />
calling-number initiator<br />
timeouts interdigit 5<br />
timeouts ringing 120<br />
load 7921 CP7921G-1.2.1<br />
load 7960-7940 term75.default<br />
time-zone 5<br />
dialplan-pattern 1 62655512.. extension-length 2 no-reg<br />
voicemail 6000<br />
max-conferences 8 gain -6<br />
call-forward system redirecting-expanded<br />
moh music-on-hold.au<br />
multicast moh 239.100.100.5 port 2010<br />
web admin system name admin password &lt;web passwd&gt;<br />
dn-webedit<br />
time-webedit<br />
transfer-system full-consult dss<br />
secondary-dialtone 9<br />
create cnf-files version-stamp 7960 Mar 22 2009 13:17:17<br />
!<br />
!<br />
ephone-template  1<br />
! &#8212; option to interrupt someone while they are on a call &#8211;!<br />
softkeys remote-in-use  CBarge Newcall<br />
softkeys hold  Resume Newcall Join<br />
! &#8212; digital display buttons on your IP phone &#8212; !<br />
softkeys connected  TrnsfVM Park Confrn Endcall Trnsfer Hold<br />
max-calls-per-button 3<br />
busy-trigger-per-button 2<br />
!<br />
!<br />
ephone-dn  1<br />
number 801 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  2<br />
number 802 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  3<br />
number 803 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  4<br />
number 804 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  5<br />
number 805 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  6<br />
number 806 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  7<br />
number 807 no-reg primary<br />
allow watch<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  8<br />
number 808 no-reg primary<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  30<br />
number 889 no-reg primary<br />
park-slot timeout 10 limit 5 recall<br />
!<br />
!<br />
ephone-dn  31<br />
number 800 no-reg primary<br />
label 800<br />
name PRIMARY HUNT<br />
call-forward busy 6000<br />
call-forward noan 6000 timeout 18<br />
!<br />
!<br />
ephone-dn  32<br />
number 888 no-reg primary<br />
paging ip 239.255.255.6 port 2009<br />
!<br />
!<br />
ephone  1<br />
device-security-mode none<br />
mac-address 000D.ED6C.43B7<br />
ephone-template 1<br />
paging-dn 32<br />
codec g729r8<br />
type 7960<br />
button  1:1 2:31<br />
!<br />
!<br />
!<br />
ephone  2<br />
device-security-mode none<br />
mac-address 0021.553E.0D65<br />
ephone-template 1<br />
max-calls-per-button 4<br />
paging-dn 32<br />
type 7921<br />
button  1:2 2:31<br />
!<br />
!<br />
!<br />
ephone  3<br />
device-security-mode none<br />
mac-address 0013.C428.640F<br />
ephone-template 1<br />
paging-dn 32<br />
type 7960<br />
button  1:3 2:31<br />
!<br />
!<br />
!<br />
ephone  4<br />
device-security-mode none<br />
mac-address 0021.553E.043E<br />
ephone-template 1<br />
max-calls-per-button 4<br />
paging-dn 32<br />
type 7921<br />
button  1:4 2:31<br />
!<br />
!<br />
!<br />
ephone  5<br />
device-security-mode none<br />
mac-address 0014.F276.4428<br />
ephone-template 1<br />
paging-dn 32<br />
type 7960<br />
button  1:5 2:31<br />
!<br />
!<br />
!<br />
ephone  6<br />
device-security-mode none<br />
mac-address 0013.C427.F8FC<br />
ephone-template 1<br />
paging-dn 32<br />
type 7960<br />
button  1:6 2:31<br />
!<br />
!<br />
!<br />
ephone  7<br />
device-security-mode none<br />
mac-address 0013.C427.F5E0<br />
ephone-template 1<br />
paging-dn 32<br />
type 7960<br />
button  1:7 2:31<br />
!<br />
!<br />
!<br />
ephone  8<br />
device-security-mode none<br />
!<br />
!<br />
!<br />
ephone  9<br />
no phone-ui speeddial-fastdial<br />
no phone-ui snr<br />
no multicast-moh<br />
device-security-mode none<br />
!<br />
!<br />
!<br />
ephone  10<br />
no phone-ui speeddial-fastdial<br />
no phone-ui snr<br />
no multicast-moh<br />
device-security-mode none<br />
!<br />
!<br />
!<br />
ephone  11<br />
no phone-ui speeddial-fastdial<br />
no phone-ui snr<br />
no multicast-moh<br />
device-security-mode none<br />
!<br />
!<br />
!<br />
ephone  12<br />
no phone-ui speeddial-fastdial<br />
no phone-ui snr<br />
no multicast-moh<br />
device-security-mode none<br />
!<br />
!<br />
alias exec siib show ip interface brief<br />
!<br />
line con 0<br />
exec-timeout 120 0<br />
logging synchronous<br />
line aux 0<br />
line vty 0 4<br />
exec-timeout 120 0<br />
password 7 &lt;password here&gt;<br />
logging synchronous<br />
login<br />
!<br />
scheduler allocate 20000 1000<br />
process cpu threshold type total rising 90 interval 10 falling 50 interval 10<br />
end</p></blockquote>
<p>So I will finish up by explaining what this does. If you call the PSTN incoming phone number (555)123-4567, &#8220;num-exp&#8221; will convert to digits 800. Then I have a parallel hunt-group configured where 800 will ring all my extensions 801,802,803, etc.  If no one answers in the hunt-group&#8230; go to voicemail at ext: 6000.</p>
<p>For outbound, I have &#8220;dial-peer voice 1 voip&#8221; and &#8220;dial-peer voice 2 voip&#8221;, this will match #1 when I dial 9,16505551212, I created the #2 for people who come to my house and need to use the phone just in case they forget to push 1+ before area code + phone number. In CA, we have to dial +1+area code+7-digit number at all times now.   So it matches dial-peer voice 1 voip map when I call 9,16505551212 right and then my call gets sent out to the SIP trunk right? Wrong&#8230; I need to strip the &#8220;9&#8243; digit out of the string otherwise it will be included in my called number. So for that I have &#8220;translation-outgoing called 3&#8243; in there to strip out the 9.  I am still working on E911 and stuff so that doesn&#8217;t work yet. But what I can do is make outbound calls and send my SIP provider the correct numbers so my call completes successfully!</p>
<p>What I have discovered was that there were 2 different types of translation-rules.<br />
#1 Command: voice translation-rule &lt;#&gt;     is different from<br />
#2 Command: translation-rule &lt;#&gt; </p>
<p>What #1 does is translate your called/calling number when you are going voip-to-analog. #2 translates your voip-to-voip called/calling string!<br />
So you will see in the configuration &#8220;translation-profile outgoing PSTN-OUTGOING&#8221; which doesn&#8217;t really do anything in my situation because I don&#8217;t have any analog/digital cards in my router such as an FXO or PRI. But I kept the config line in there some day I decide to get a backup analog line.</p>
<p>There are still some rules and destination-patterns I need to tweak so I will be updating this later. But overall, this configuration works. I am able to make outbound US calls, receive incoming calls&#8230; page all the house phones when I dial 888, park my calls at ext: 889, and have voicemail at ext: 6000.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/22/call-manager-express-to-3rd-party-sip-provider-sample-configuration/feed/</wfw:commentRss>
		</item>
		<item>
		<title>WCCPv1 vs. WCCPv2</title>
		<link>http://www.siriuspackets.com/2009/03/21/wccpv1-vs-wccpv2/</link>
		<comments>http://www.siriuspackets.com/2009/03/21/wccpv1-vs-wccpv2/#comments</comments>
		<pubDate>Sun, 22 Mar 2009 05:47:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[IP Services]]></category>

		<category><![CDATA[WAN Acceleration]]></category>

		<category><![CDATA[wccp]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=40</guid>
		<description><![CDATA[WCCPv1:
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;
1. Only single router can participate in a cluster of WCCP-capable devices
2. Intercepts and redirects HTTP and HTTPS
3. Does not allow load balancing
WCCPv2:
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;
1. Supports multiple routers can redirect to clusters and devices, allows for load balancing.
2. Support for non HTTP and HTTPS protocols such as other TCP or UDP packets.
3. Capable of MD5 authentication.
4. Notification [...]]]></description>
			<content:encoded><![CDATA[<p>WCCPv1:<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
1. Only single router can participate in a cluster of WCCP-capable devices<br />
2. Intercepts and redirects HTTP and HTTPS<br />
3. Does not allow load balancing</p>
<p>WCCPv2:<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
1. Supports multiple routers can redirect to clusters and devices, allows for load balancing.<br />
2. Support for non HTTP and HTTPS protocols such as other TCP or UDP packets.<br />
3. Capable of MD5 authentication.<br />
4. Notification capabilities for web cache overloading to the router<br />
5. Load Balancing based on hashing or masking algorithms</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/21/wccpv1-vs-wccpv2/feed/</wfw:commentRss>
		</item>
		<item>
		<title>WCCP &#8220;accelerated&#8221; option</title>
		<link>http://www.siriuspackets.com/2009/03/21/wccp-accelerated-option/</link>
		<comments>http://www.siriuspackets.com/2009/03/21/wccp-accelerated-option/#comments</comments>
		<pubDate>Sun, 22 Mar 2009 05:41:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[WAN Acceleration]]></category>

		<category><![CDATA[wae]]></category>

		<category><![CDATA[wae hardware wccp]]></category>

		<category><![CDATA[wan acceleration]]></category>

		<category><![CDATA[wccp]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=38</guid>
		<description><![CDATA[This option allows 6500/7600 to use hardware acceleration for WCCP packets in Layer 2. This method in theory allows you to utilize up to 3Gbps of traffic on a PFC2 card, perhaps even more with a PFC3B.
The device (eg: WAE or ACNS) needs to have layer 2 adjacency with the 6500 switch in order to [...]]]></description>
			<content:encoded><![CDATA[<p>This option allows 6500/7600 to use hardware acceleration for WCCP packets in Layer 2. This method in theory allows you to utilize up to 3Gbps of traffic on a PFC2 card, perhaps even more with a PFC3B.</p>
<p>The device (eg: WAE or ACNS) needs to have layer 2 adjacency with the 6500 switch in order to take advantage of hardware redirection. If you do not have layer 2 direct adjacency, then most likely you will have to use the GRE tunneling method of WCCP to redirect transparently.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/21/wccp-accelerated-option/feed/</wfw:commentRss>
		</item>
		<item>
		<title>OSPF packet types and LSA packets</title>
		<link>http://www.siriuspackets.com/2009/03/21/ospf-lsa-packets/</link>
		<comments>http://www.siriuspackets.com/2009/03/21/ospf-lsa-packets/#comments</comments>
		<pubDate>Sun, 22 Mar 2009 05:29:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[IP Routing]]></category>

		<category><![CDATA[ip routing]]></category>

		<category><![CDATA[ospf]]></category>

		<category><![CDATA[ospf lsa]]></category>

		<category><![CDATA[ospf packet type]]></category>

		<guid isPermaLink="false">http://www.siriuspackets.com/?p=36</guid>
		<description><![CDATA[OSPF packet types are different from OSPF LSA types.
LSA&#8217;s are represented by one of these packet types.
Check out the diagram to get a better understanding for the different types of OSPF packet types.
Step 1: Hello packet received from a neighbor router causes an OSPF interface to be in INIT STATE regardless of other variables at [...]]]></description>
			<content:encoded><![CDATA[<p>OSPF packet types are different from OSPF LSA types.<br />
LSA&#8217;s are represented by one of these packet types.<br />
Check out the diagram to get a better understanding for the different types of OSPF packet types.</p>
<div id="attachment_96" class="wp-caption alignnone" style="width: 330px"><img class="size-full wp-image-96 " title="OSPF Packet Types" src="http://www.siriuspackets.com/wp-content/uploads/2009/03/ospf-packet.jpg" alt="OSPF Packet Types" width="320" height="214" /><p class="wp-caption-text">OSPF Packet Types</p></div>
<p><strong>Step 1:</strong> Hello packet received from a neighbor router causes an OSPF interface to be in INIT STATE regardless of other variables at this point. Hello packet contains things like (a) router-id (b) area id (c) AuthType (d) authentication (e)Netmask (f)Hello Int (g)Dead Int (h)DR (i)BDR (g) Neighbor IP<br />
<strong>Step 2 (optional):</strong>  If its a broadcast/multiaccess environment, the interface will go into TWO-WAY state to see who will be the DR (designated router) and BDR (backup designated router) based on the info provided in the HELLO packet. This can also be triggered by receiving a DBD packet.<br />
<strong>Step 3 (optional):</strong> EXSTART state on the interface is when its OK to start exchanging topological databases between neighbors after DR/BDR is determined.<br />
<strong>Step 4: </strong>EXCHANGE state is the actual &#8220;exchange&#8221; of databases using the database descriptor packet.<br />
<strong>Step 5:</strong> LOADING state, based on the DBD packets received. Some parts of the database might be out-of-date so then the Router sends link-state requests, updates, and acknowledgements to make sure everything is all synchronized between the two neighbors and databases match up. The meaning is pretty straight forward, request is a request for an LSA-type 1,2,3,4,5, or 7. Update is when the router provides the actual route prefix/mask/area info, and Acknowledgement is when it tells the neighbor &#8220;OK I received your packet in good condition&#8221;.<br />
<strong>Step 6:</strong> FULL state, databases are all up to date and synchronized with all the other routers in the area topology, good to go for inserting routes into the forwarding table now!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.siriuspackets.com/2009/03/21/ospf-lsa-packets/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
