<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/3.3.2" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Welcome to the VoIP Blog</title>
		<link>http://www.voip-blog.co.uk/index.php</link>
		<atom:link rel="self" type="application/rss+xml" href="http://www.voip-blog.co.uk/index.php?tempskin=_rss2" />
		<description>The Voip blog.  Useful stuff for VoIP in the UK.</description>
		<language>en-GB</language>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=3.3.2"/>
		<ttl>60</ttl>
				<item>
			<title>Install CUCM 7 on VMware Fusion</title>
			<link>http://www.voip-blog.co.uk/index.php/2010/02/03/install-cucm-7-on-vmware-fusion</link>
			<pubDate>Wed, 03 Feb 2010 17:25:36 +0000</pubDate>			<dc:creator>admin</dc:creator>
			<category domain="alt">Cisco Unified Communication Manager</category>
<category domain="alt">Cisco Unified Communications Manager Business Edition</category>
<category domain="main">Call Control</category>
<category domain="alt">Cisco Unity Connection</category>
<category domain="alt">VMware</category>			<guid isPermaLink="false">36@http://voip-blog.co.uk/</guid>
						<description>&lt;p&gt;Installing Cisco Unified Communications Manager on VMware Fusion can be tricky if you don't know what settings to use.&lt;/p&gt;
&lt;p&gt;The image below shows settings that work well with CUCM 7.x.&lt;/p&gt;
&lt;p&gt;&lt;img style=&quot;float: left;&quot; src=&quot;/media/blogs/voip-blog/CUCM-7-FUSION.gif&quot; alt=&quot;cucm-on-fusion-settings&quot; width=&quot;613&quot; height=&quot;400&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&amp;#160;&lt;/p&gt;
&lt;p&gt;&amp;#160;&lt;/p&gt;&lt;div class=&quot;item_footer&quot;&gt;&lt;p&gt;&lt;small&gt;&lt;a href=&quot;http://www.voip-blog.co.uk/index.php/2010/02/03/install-cucm-7-on-vmware-fusion&quot;&gt;Original post&lt;/a&gt; blogged on &lt;a href=&quot;http://b2evolution.net/&quot;&gt;b2evolution&lt;/a&gt;.&lt;/small&gt;&lt;/p&gt;&lt;/div&gt;</description>
			<content:encoded><![CDATA[<p>Installing Cisco Unified Communications Manager on VMware Fusion can be tricky if you don't know what settings to use.</p>
<p>The image below shows settings that work well with CUCM 7.x.</p>
<p><img style="float: left;" src="http://www.voip-blog.co.uk/media/blogs/voip-blog/CUCM-7-FUSION.gif" alt="cucm-on-fusion-settings" width="613" height="400" /></p>
<p>&#160;</p>
<p>&#160;</p><div class="item_footer"><p><small><a href="http://www.voip-blog.co.uk/index.php/2010/02/03/install-cucm-7-on-vmware-fusion">Original post</a> blogged on <a href="http://b2evolution.net/">b2evolution</a>.</small></p></div>]]></content:encoded>
								<comments>http://www.voip-blog.co.uk/index.php/2010/02/03/install-cucm-7-on-vmware-fusion#comments</comments>
			<wfw:commentRss>http://www.voip-blog.co.uk/index.php?tempskin=_rss2&#38;disp=comments&#38;p=36</wfw:commentRss>
		</item>
				<item>
			<title>NAT SIP range on UC500/CME</title>
			<link>http://www.voip-blog.co.uk/index.php/2009/11/21/nat-sip-range-on-uc500-cme</link>
			<pubDate>Sat, 21 Nov 2009 20:25:05 +0000</pubDate>			<dc:creator>admin</dc:creator>
			<category domain="alt">Cisco Unified Communications Manager Express</category>
<category domain="main">Cisco Unified Communications 500 Series</category>
<category domain="alt">Call Control</category>
<category domain="alt">Network Configuration</category>			<guid isPermaLink="false">35@http://voip-blog.co.uk/</guid>
						<description>&lt;p&gt;&lt;span class=&quot;clear&quot;&gt;This example describes how to use a single public IP address in conjunction with a NAT port range on an IOS router. This would be suitable when using a Cisco UC500 or CME based system behind a router. The diagram below demonstrates the example topology used in this scenario. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;clear&quot;&gt;Cisco 877 IP Information&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;clear&quot;&gt;Public Interface: 20.20.20.20&lt;br /&gt;Private Interface: 192.168.0.1/30&lt;br /&gt;&lt;br /&gt;Cisco Uc500 IP Information&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span class=&quot;clear&quot;&gt;Routed Interface: 192.168.0.2/30&lt;br /&gt;Loopback Interface: 10.1.1.1 (SIP services bound to this interface)&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div class=&quot;image_block&quot; style=&quot;text-align: center;&quot;&gt;&lt;a href=&quot;/media/blogs/voip-blog/sipnat.png&quot;&gt;&lt;img style=&quot;vertical-align: middle;&quot; src=&quot;/media/blogs/voip-blog/sipnat.png&quot; alt=&quot;SIP NAT example&quot; width=&quot;444&quot; height=&quot;108&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;p&gt;As with any router providing internet access outbound access is likely provided with an overload statement such as this example.&lt;br /&gt;&lt;br class=&quot;codeblock&quot; /&gt;&lt;span class=&quot;small&quot;&gt;access-list 105 permit ip &amp;lt;inside networks&amp;gt; any&lt;br /&gt;route-map NAT_MAP permit 1&lt;br /&gt;match ip address 105&lt;br /&gt;ip nat inside source route-map NAT_MAP interface dialer1 overload&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;To allow a SIP mapping is very simple as per the statement below.&lt;br /&gt;&lt;br /&gt;&lt;span class=&quot;small&quot;&gt;ip nat inside source static tcp 10.1.1.1 5060 interface dialer1 5060&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;However, a large range of ports is required for RTP, and IOS based devices do not yet&amp;#160; have a straight port range option for NAT. The solution in this case is to utilise a route-map that matches the required RTP range (some SIP providers allow you to specify this).&lt;br /&gt;&lt;br /&gt;&lt;span class=&quot;small&quot;&gt;ip access-list extended UDP_RTP&lt;br /&gt; permit udp host &amp;lt;SIP HOST&amp;gt; any range 16384 37248&lt;br /&gt;!&lt;br /&gt;route-map SIP_NAT permit 10&lt;br /&gt; match ip address UDP_RTP&lt;br /&gt;!&lt;br /&gt;ip nat inside source static 10.1.1.1 20.20.20.20 route-map SIP_NAT&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Inbound and outbound calls via SIP should function correctly.&lt;/p&gt;
&lt;p&gt;&amp;#160;&lt;/p&gt;&lt;div class=&quot;item_footer&quot;&gt;&lt;p&gt;&lt;small&gt;&lt;a href=&quot;http://www.voip-blog.co.uk/index.php/2009/11/21/nat-sip-range-on-uc500-cme&quot;&gt;Original post&lt;/a&gt; blogged on &lt;a href=&quot;http://b2evolution.net/&quot;&gt;b2evolution&lt;/a&gt;.&lt;/small&gt;&lt;/p&gt;&lt;/div&gt;</description>
			<content:encoded><![CDATA[<p><span class="clear">This example describes how to use a single public IP address in conjunction with a NAT port range on an IOS router. This would be suitable when using a Cisco UC500 or CME based system behind a router. The diagram below demonstrates the example topology used in this scenario. </span></p>
<p><span class="clear">Cisco 877 IP Information<br /></span></p>
<p><span class="clear">Public Interface: 20.20.20.20<br />Private Interface: 192.168.0.1/30<br /><br />Cisco Uc500 IP Information</span></p>
<p><span class="clear">Routed Interface: 192.168.0.2/30<br />Loopback Interface: 10.1.1.1 (SIP services bound to this interface)<br /></span></p>
<div class="image_block" style="text-align: center;"><a href="http://www.voip-blog.co.uk/media/blogs/voip-blog/sipnat.png"><img style="vertical-align: middle;" src="http://www.voip-blog.co.uk/media/blogs/voip-blog/sipnat.png" alt="SIP NAT example" width="444" height="108" /></a></div>
<p>As with any router providing internet access outbound access is likely provided with an overload statement such as this example.<br /><br class="codeblock" /><span class="small">access-list 105 permit ip &lt;inside networks&gt; any<br />route-map NAT_MAP permit 1<br />match ip address 105<br />ip nat inside source route-map NAT_MAP interface dialer1 overload</span><br /><br />To allow a SIP mapping is very simple as per the statement below.<br /><br /><span class="small">ip nat inside source static tcp 10.1.1.1 5060 interface dialer1 5060</span><br /><br />However, a large range of ports is required for RTP, and IOS based devices do not yet&#160; have a straight port range option for NAT. The solution in this case is to utilise a route-map that matches the required RTP range (some SIP providers allow you to specify this).<br /><br /><span class="small">ip access-list extended UDP_RTP<br /> permit udp host &lt;SIP HOST&gt; any range 16384 37248<br />!<br />route-map SIP_NAT permit 10<br /> match ip address UDP_RTP<br />!<br />ip nat inside source static 10.1.1.1 20.20.20.20 route-map SIP_NAT</span><br /><br />Inbound and outbound calls via SIP should function correctly.</p>
<p>&#160;</p><div class="item_footer"><p><small><a href="http://www.voip-blog.co.uk/index.php/2009/11/21/nat-sip-range-on-uc500-cme">Original post</a> blogged on <a href="http://b2evolution.net/">b2evolution</a>.</small></p></div>]]></content:encoded>
								<comments>http://www.voip-blog.co.uk/index.php/2009/11/21/nat-sip-range-on-uc500-cme#comments</comments>
			<wfw:commentRss>http://www.voip-blog.co.uk/index.php?tempskin=_rss2&#38;disp=comments&#38;p=35</wfw:commentRss>
		</item>
				<item>
			<title>DSCP to TOS (Decimal)</title>
			<link>http://www.voip-blog.co.uk/index.php/2009/10/25/dscp-to-tos-decimal</link>
			<pubDate>Sun, 25 Oct 2009 21:29:10 +0000</pubDate>			<dc:creator>admin</dc:creator>
			<category domain="alt">Call Control</category>
<category domain="alt">Network Configuration</category>
<category domain="main">QoS</category>			<guid isPermaLink="false">33@http://voip-blog.co.uk/</guid>
						<description>&lt;p&gt;This is a useful table when you need to work out the TOS decimal value of DSCP.&lt;/p&gt;
&lt;p&gt;DSCP TOS&lt;br /&gt;0 0&lt;br /&gt;1 4&lt;br /&gt;2 8&lt;br /&gt;3 12&lt;br /&gt;4 16&lt;br /&gt;5 20&lt;br /&gt;6 24&lt;br /&gt;7 28&lt;br /&gt;8 32&lt;br /&gt;9 36&lt;br /&gt;10 40&lt;br /&gt;11 44&lt;br /&gt;12 48&lt;br /&gt;13 52&lt;br /&gt;14 56&lt;br /&gt;15 60&lt;br /&gt;16 64&lt;br /&gt;17 68&lt;br /&gt;18 72&lt;br /&gt;19 76&lt;br /&gt;20 80&lt;br /&gt;21 84&lt;br /&gt;22 88&lt;br /&gt;23 92&lt;br /&gt;24 96&lt;br /&gt;25 100&lt;br /&gt;26 104&lt;br /&gt;27 108&lt;br /&gt;28 112&lt;br /&gt;29 116&lt;br /&gt;30 120&lt;br /&gt;31 124&lt;br /&gt;32 128&lt;br /&gt;33 132&lt;br /&gt;34 136&lt;br /&gt;35 140&lt;br /&gt;36 144&lt;br /&gt;37 148&lt;br /&gt;38 152&lt;br /&gt;39 156&lt;br /&gt;40 160&lt;br /&gt;41 164&lt;br /&gt;42 168&lt;br /&gt;43 172&lt;br /&gt;44 176&lt;br /&gt;45 180&lt;br /&gt;46 184&lt;br /&gt;47 188&lt;br /&gt;48 192&lt;br /&gt;49 196&lt;br /&gt;50 200&lt;br /&gt;51 204&lt;br /&gt;52 208&lt;br /&gt;53 212&lt;br /&gt;54 216&lt;br /&gt;55 220&lt;br /&gt;56 224&lt;br /&gt;57 228&lt;br /&gt;58 232&lt;br /&gt;59 236&lt;br /&gt;60 240&lt;br /&gt;61 244&lt;br /&gt;62 248&lt;br /&gt;63 252&lt;/p&gt;&lt;div class=&quot;item_footer&quot;&gt;&lt;p&gt;&lt;small&gt;&lt;a href=&quot;http://www.voip-blog.co.uk/index.php/2009/10/25/dscp-to-tos-decimal&quot;&gt;Original post&lt;/a&gt; blogged on &lt;a href=&quot;http://b2evolution.net/&quot;&gt;b2evolution&lt;/a&gt;.&lt;/small&gt;&lt;/p&gt;&lt;/div&gt;</description>
			<content:encoded><![CDATA[<p>This is a useful table when you need to work out the TOS decimal value of DSCP.</p>
<p>DSCP TOS<br />0 0<br />1 4<br />2 8<br />3 12<br />4 16<br />5 20<br />6 24<br />7 28<br />8 32<br />9 36<br />10 40<br />11 44<br />12 48<br />13 52<br />14 56<br />15 60<br />16 64<br />17 68<br />18 72<br />19 76<br />20 80<br />21 84<br />22 88<br />23 92<br />24 96<br />25 100<br />26 104<br />27 108<br />28 112<br />29 116<br />30 120<br />31 124<br />32 128<br />33 132<br />34 136<br />35 140<br />36 144<br />37 148<br />38 152<br />39 156<br />40 160<br />41 164<br />42 168<br />43 172<br />44 176<br />45 180<br />46 184<br />47 188<br />48 192<br />49 196<br />50 200<br />51 204<br />52 208<br />53 212<br />54 216<br />55 220<br />56 224<br />57 228<br />58 232<br />59 236<br />60 240<br />61 244<br />62 248<br />63 252</p><div class="item_footer"><p><small><a href="http://www.voip-blog.co.uk/index.php/2009/10/25/dscp-to-tos-decimal">Original post</a> blogged on <a href="http://b2evolution.net/">b2evolution</a>.</small></p></div>]]></content:encoded>
								<comments>http://www.voip-blog.co.uk/index.php/2009/10/25/dscp-to-tos-decimal#comments</comments>
			<wfw:commentRss>http://www.voip-blog.co.uk/index.php?tempskin=_rss2&#38;disp=comments&#38;p=33</wfw:commentRss>
		</item>
				<item>
			<title>How to set Unified Communication Manager time</title>
			<link>http://www.voip-blog.co.uk/index.php/2009/10/25/how-to-set-unified-communication-manager-time</link>
			<pubDate>Sun, 25 Oct 2009 21:28:49 +0000</pubDate>			<dc:creator>admin</dc:creator>
			<category domain="main">Cisco Unified Communication Manager</category>
<category domain="alt">Call Control</category>			<guid isPermaLink="false">32@http://voip-blog.co.uk/</guid>
						<description>&lt;p&gt;&lt;strong&gt;NTP Configuration &lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This configuration applies to version 4.3 and earlier.&lt;strong&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The publisher should point to a dedicated NTP external time source.&lt;/p&gt;
&lt;p&gt;The subscribers should point to the publisher server.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Complete the following steps:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;1.&amp;#160; Disable the Windows Time service (W32Time) on the server.&lt;/p&gt;
&lt;p style=&quot;padding-left: 30px;&quot;&gt;Open the Windows Services snap-in.&lt;br /&gt;Right click the Windows Time service and select properties.&lt;br /&gt;In the Startup Type box, choose Disabled from the drop-down list.&lt;br /&gt;Click OK.&lt;/p&gt;
&lt;p&gt;2.&amp;#160; Edit the NTP demon configuration file. (ndpd.conf)&lt;/p&gt;
&lt;p style=&quot;padding-left: 30px;&quot;&gt;The ntpd.conf file is located in the &quot;C:\WINNT\system32\drivers\etc&quot; folder.&lt;br /&gt;Edit the file so it contains the required NTP server(s).&lt;/p&gt;
&lt;p style=&quot;padding-left: 60px;&quot;&gt;Sample:&lt;br /&gt;server 10.20.30.10&lt;br /&gt;server 10.20.30.11&lt;br /&gt;driftfile C:\WINNT\system32\drivers\etc\ntp.drift&lt;/p&gt;&lt;div class=&quot;item_footer&quot;&gt;&lt;p&gt;&lt;small&gt;&lt;a href=&quot;http://www.voip-blog.co.uk/index.php/2009/10/25/how-to-set-unified-communication-manager-time&quot;&gt;Original post&lt;/a&gt; blogged on &lt;a href=&quot;http://b2evolution.net/&quot;&gt;b2evolution&lt;/a&gt;.&lt;/small&gt;&lt;/p&gt;&lt;/div&gt;</description>
			<content:encoded><![CDATA[<p><strong>NTP Configuration </strong></p>
<p>This configuration applies to version 4.3 and earlier.<strong><br /></strong></p>
<p>The publisher should point to a dedicated NTP external time source.</p>
<p>The subscribers should point to the publisher server.</p>
<p><strong>Complete the following steps:</strong></p>
<p>1.&#160; Disable the Windows Time service (W32Time) on the server.</p>
<p style="padding-left: 30px;">Open the Windows Services snap-in.<br />Right click the Windows Time service and select properties.<br />In the Startup Type box, choose Disabled from the drop-down list.<br />Click OK.</p>
<p>2.&#160; Edit the NTP demon configuration file. (ndpd.conf)</p>
<p style="padding-left: 30px;">The ntpd.conf file is located in the "C:\WINNT\system32\drivers\etc" folder.<br />Edit the file so it contains the required NTP server(s).</p>
<p style="padding-left: 60px;">Sample:<br />server 10.20.30.10<br />server 10.20.30.11<br />driftfile C:\WINNT\system32\drivers\etc\ntp.drift</p><div class="item_footer"><p><small><a href="http://www.voip-blog.co.uk/index.php/2009/10/25/how-to-set-unified-communication-manager-time">Original post</a> blogged on <a href="http://b2evolution.net/">b2evolution</a>.</small></p></div>]]></content:encoded>
								<comments>http://www.voip-blog.co.uk/index.php/2009/10/25/how-to-set-unified-communication-manager-time#comments</comments>
			<wfw:commentRss>http://www.voip-blog.co.uk/index.php?tempskin=_rss2&#38;disp=comments&#38;p=32</wfw:commentRss>
		</item>
			</channel>
</rss>
