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

<channel>
	<title>MyVoipApp products blog</title>
	<atom:link href="http://www.myvoipapp.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.myvoipapp.com/blog</link>
	<description>Software based VOIP server</description>
	<lastBuildDate>Wed, 02 May 2012 07:22:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>UDP 5060 is blocked by ISP, can I use another port?</title>
		<link>http://www.myvoipapp.com/blog/2012/05/02/udp-5060-is-blocked-by-isp-can-i-use-another-port/</link>
		<comments>http://www.myvoipapp.com/blog/2012/05/02/udp-5060-is-blocked-by-isp-can-i-use-another-port/#comments</comments>
		<pubDate>Wed, 02 May 2012 07:22:51 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer Cloud]]></category>
		<category><![CDATA[blocking]]></category>
		<category><![CDATA[isp]]></category>
		<category><![CDATA[sip port]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=200</guid>
		<description><![CDATA[Some cloud-mss customers ask us this problem because the standard SIP port (UDP 5060) is blocked by their ISP in their countries. So we upgrade cloud-MSS to support several UDP ports: 5060, 6060 and 8080. In the cloud management interface, &#8230; <a href="http://www.myvoipapp.com/blog/2012/05/02/udp-5060-is-blocked-by-isp-can-i-use-another-port/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Some cloud-mss customers ask us this problem because the standard SIP port (UDP 5060) is blocked by their ISP in their countries.</p>
<p>So we upgrade cloud-MSS to support several UDP ports: 5060, 6060 and 8080. In the cloud management interface, you can select one of them in &#8220;Basic call / System information&#8221;. Please refer to following figure for more details:</p>
<div id="attachment_201" class="wp-caption alignnone" style="width: 676px"><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2012/05/cloud-mss-en.png"><img class="size-full wp-image-201" title="cloud-mss-en" src="http://www.myvoipapp.com/blog/wp-content/uploads/2012/05/cloud-mss-en.png" alt="" width="666" height="477" /></a><p class="wp-caption-text">Cloud-MSS configuration for several SIP ports</p></div>
<p>If you select a UDP port which is not standard 5060, you must change configurations in SIP phones/clients. Below figure is a demo configuration of xlite since we change the port to 8080.</p>
<div id="attachment_202" class="wp-caption alignnone" style="width: 449px"><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2012/05/xlite.png"><img class="size-full wp-image-202" title="xlite" src="http://www.myvoipapp.com/blog/wp-content/uploads/2012/05/xlite.png" alt="" width="439" height="502" /></a><p class="wp-caption-text">Xlite configuration with UDP port 8080</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/05/02/udp-5060-is-blocked-by-isp-can-i-use-another-port/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MSS V6.5 updated to support &#8220;speed-dialing&#8221; feature</title>
		<link>http://www.myvoipapp.com/blog/2012/04/16/mss-v6-5-updated-to-support-speed-dialing-feature/</link>
		<comments>http://www.myvoipapp.com/blog/2012/04/16/mss-v6-5-updated-to-support-speed-dialing-feature/#comments</comments>
		<pubDate>Mon, 16 Apr 2012 02:21:35 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[pbx]]></category>
		<category><![CDATA[speed dial]]></category>
		<category><![CDATA[voip]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=197</guid>
		<description><![CDATA[V6.5 has been upgraded to support &#8220;speed dialing&#8221; feature. In fact, previous versions can also support &#8220;speed dialing&#8221; feature by using &#8220;dial plan&#8221; functions. To do that, customers need make configurations with several tables, it could be difficult. With the &#8230; <a href="http://www.myvoipapp.com/blog/2012/04/16/mss-v6-5-updated-to-support-speed-dialing-feature/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>V6.5 has been upgraded to support &#8220;speed dialing&#8221; feature.</p>
<p>In fact, previous versions can also support &#8220;speed dialing&#8221; feature by using &#8220;dial plan&#8221; functions. To do that, customers need make configurations with several tables, it could be difficult. With the new version, we separate a independent table to configure &#8220;speed dial&#8221; and it is so easy to support it.</p>
<p>Please refer to our document for more details about this feature:</p>
<p><a href="http://www.myvoipapp.com/docs/mss_services/speed-dial/index.html" target="_blank">http://www.myvoipapp.com/docs/mss_services/speed-dial/index.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/04/16/mss-v6-5-updated-to-support-speed-dialing-feature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trigger different IVR for different incoming calls</title>
		<link>http://www.myvoipapp.com/blog/2012/04/06/trigger-different-ivr-for-different-incoming-calls/</link>
		<comments>http://www.myvoipapp.com/blog/2012/04/06/trigger-different-ivr-for-different-incoming-calls/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 13:45:20 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[ivr]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=193</guid>
		<description><![CDATA[miniSipServer is upgraded to V6.5 to support different IVR for different incoming calls. It is very easy to configure MSS to do that, please refer to online document: http://www.myvoipapp.com/docs/mss_services/auto_attendant/index.html#multi-ivr For example, if we want to trigger different IVR for another &#8230; <a href="http://www.myvoipapp.com/blog/2012/04/06/trigger-different-ivr-for-different-incoming-calls/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>miniSipServer is upgraded to V6.5 to support different IVR for different incoming calls.</p>
<p>It is very easy to configure MSS to do that, please refer to online document:</p>
<p><a href="http://www.myvoipapp.com/docs/mss_services/auto_attendant/index.html#multi-ivr" target="_blank">http://www.myvoipapp.com/docs/mss_services/auto_attendant/index.html#multi-ivr</a></p>
<p>For example, if we want to trigger different IVR for another external line (such as &#8220;1234&#8243;), we can configure the &#8220;IVR services&#8221; with following record:</p>
<pre>dial plan = default
Called number = 1234  <span style="color: #0000ff;">&lt;--This is the external line name/account</span>
IVR-XML file name = aa2.xml <span style="color: #0000ff;">&lt;--your own IVR-XML file</span></pre>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/04/06/trigger-different-ivr-for-different-incoming-calls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Call recording</title>
		<link>http://www.myvoipapp.com/blog/2012/03/10/call-recording/</link>
		<comments>http://www.myvoipapp.com/blog/2012/03/10/call-recording/#comments</comments>
		<pubDate>Sat, 10 Mar 2012 14:03:19 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[audio]]></category>
		<category><![CDATA[call recording]]></category>
		<category><![CDATA[lawful interception]]></category>
		<category><![CDATA[service]]></category>
		<category><![CDATA[voip]]></category>
		<category><![CDATA[wav]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=190</guid>
		<description><![CDATA[miniSipServer is upgraded today to support &#8220;call recording&#8221; feature. This feature can be used to record local user&#8217;s audio stream. Please refer to following service document: http://www.myvoipapp.com/docs/mss_services/call-recording/index.html]]></description>
			<content:encoded><![CDATA[<p>miniSipServer is upgraded today to support &#8220;call recording&#8221; feature. This feature can be used to record local user&#8217;s audio stream.</p>
<p>Please refer to following service document:</p>
<p><a href="http://www.myvoipapp.com/docs/mss_services/call-recording/index.html" target="_blank">http://www.myvoipapp.com/docs/mss_services/call-recording/index.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/03/10/call-recording/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speed dialing in cloud IP-PBX</title>
		<link>http://www.myvoipapp.com/blog/2012/02/29/speed-dialing-in-cloud-ip-pbx/</link>
		<comments>http://www.myvoipapp.com/blog/2012/02/29/speed-dialing-in-cloud-ip-pbx/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 12:45:09 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[Docs & FAQ]]></category>
		<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer Cloud]]></category>
		<category><![CDATA[abbreviated dialing]]></category>
		<category><![CDATA[speed dial]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=187</guid>
		<description><![CDATA[&#8220;Speed dialing&#8221;, sometimes it is also named as &#8220;abbreviated dialing&#8221;, is a tranditional PBX service. It allows the user to invoke a call by pressing a reduced number of keys. This service is particularly useful for phone users who dial &#8230; <a href="http://www.myvoipapp.com/blog/2012/02/29/speed-dialing-in-cloud-ip-pbx/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>&#8220;Speed dialing&#8221;, sometimes it is also named as &#8220;abbreviated dialing&#8221;, is a tranditional PBX service. It allows the user to invoke a call by pressing a reduced number of keys. This service is particularly useful for phone users who dial certain numbers on a regular basis.</p>
<p>In cloud-miniSipServer, it is very easy to configure this service. Please take a look at following figure:</p>
<p><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/speeddial.png"><img class="alignnone size-full wp-image-188" title="speeddial" src="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/speeddial.png" alt="Speed dial configuration in cloud-pbx" width="810" height="190" /></a></p>
<p>What we need do is just clicking menu &#8220;Advance service / Speed dialing&#8221; to add some records.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/02/29/speed-dialing-in-cloud-ip-pbx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hunt-group in Cloud IPPBX</title>
		<link>http://www.myvoipapp.com/blog/2012/02/24/hunt-group-in-cloud-ippbx/</link>
		<comments>http://www.myvoipapp.com/blog/2012/02/24/hunt-group-in-cloud-ippbx/#comments</comments>
		<pubDate>Fri, 24 Feb 2012 04:52:26 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer Cloud]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[hunt-group]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=178</guid>
		<description><![CDATA[Yesterday we upgraded Cloud-miniSipServer to support hunt-group feature. HG feature has been supported in local minisipserver for a long time. Lots of small companies use this feature to service their customers. The HG service in cloud-minisipserver is almost same with &#8230; <a href="http://www.myvoipapp.com/blog/2012/02/24/hunt-group-in-cloud-ippbx/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Yesterday we upgraded Cloud-miniSipServer to support hunt-group feature.</p>
<p>HG feature has been supported in local minisipserver for a long time. Lots of small companies use this feature to service their customers. The HG service in cloud-minisipserver is almost same with local-minisipserver, such as same service log, same configurations.</p>
<p>The difference is GUI display. Please refer to following figures.</p>
<p>One is for cloud-minisipserver.</p>
<div id="attachment_180" class="wp-caption alignnone" style="width: 297px"><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/cloud1.png"><img class="size-full wp-image-180" title="HG in cloud" src="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/cloud1.png" alt="HG configuration in cloud pbx" width="287" height="235" /></a><p class="wp-caption-text">HG configuration in cloud pbx</p></div>
<p>another is for local-minisipserver:</p>
<div id="attachment_181" class="wp-caption alignnone" style="width: 440px"><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/local.png"><img class="size-full wp-image-181" title="HG in local PBX" src="http://www.myvoipapp.com/blog/wp-content/uploads/2012/02/local.png" alt="HG configuration in local IP-PBX" width="430" height="145" /></a><p class="wp-caption-text">HG configuration in local IP-PBX</p></div>
<p>For more details of hunt-group service, please refer to our online document:</p>
<p><a href="http://www.myvoipapp.com/docs/mss_services/hunting_group/index.html" target="_blank">http://www.myvoipapp.com/docs/mss_services/hunting_group/index.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/02/24/hunt-group-in-cloud-ippbx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple-OEM plan</title>
		<link>http://www.myvoipapp.com/blog/2012/02/03/simple-oem-plan/</link>
		<comments>http://www.myvoipapp.com/blog/2012/02/03/simple-oem-plan/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 08:54:41 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[oem]]></category>
		<category><![CDATA[sip server]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=176</guid>
		<description><![CDATA[This year, we provide simple-oem plan for our customers. More and more customers ask us to provide a OEM product to integrate with their products. Then, they could provide a VoIP total solution to their final customers. They also hope &#8230; <a href="http://www.myvoipapp.com/blog/2012/02/03/simple-oem-plan/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This year, we provide simple-oem plan for our customers.</p>
<p>More and more customers ask us to provide a OEM product to integrate with their products. Then, they could provide a VoIP total solution to their final customers. They also hope to have their own product price, and so on.</p>
<p>This plan is used to fit such requirements. We hope most partners can benefit from our plan.</p>
<p>Please refer to following document for details about this plan:</p>
<p><a href="http://www.myvoipapp.com/resellers/simple-oem/index.html" target="_blank">http://www.myvoipapp.com/resellers/simple-oem/index.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/02/03/simple-oem-plan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Run as windows service</title>
		<link>http://www.myvoipapp.com/blog/2012/01/21/run-as-windows-service/</link>
		<comments>http://www.myvoipapp.com/blog/2012/01/21/run-as-windows-service/#comments</comments>
		<pubDate>Sat, 21 Jan 2012 10:36:32 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[ippbx]]></category>
		<category><![CDATA[sip]]></category>
		<category><![CDATA[voip]]></category>
		<category><![CDATA[windows service]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=169</guid>
		<description><![CDATA[Some customers often ask us how to run miniSipServer as windows service? It is a interesting topic. After research, we think it is very reasonable to run miniSipServer as windows service. For example, the server could be reboot for some &#8230; <a href="http://www.myvoipapp.com/blog/2012/01/21/run-as-windows-service/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Some customers often ask us how to run miniSipServer as windows service?</p>
<p>It is a interesting topic. After research, we think it is very reasonable to run miniSipServer as windows service. For example, the server could be reboot for some exception, so administrator hope miniSipServer can auto-start together and GUI is unnecessary once the IP-PBX has been configured successfully.</p>
<p>With the release of version 6.2.1, our customers can run miniSipServer as windows service now.</p>
<p>After install new miniSipServer, we can find a new exe file whose name is &#8216;msscli.exe&#8217;. It is a command line application without GUI interface. In fact, &#8216;msscli.exe&#8217; has the same SIP server core with &#8216;mss.exe&#8217; which is the GUI version.</p>
<p>In another way, we need &#8216;sc.exe&#8217; command to create windows service. &#8216;sc.exe&#8217; is widows own application.</p>
<p>We assume that miniSipServer is installed in directory &#8216;d:\myvoipapp\minisipserver&#8217;, then we can begin now:</p>
<p>To create a windows service:</p>
<pre>sc create minisipserver binPath= "d:\myvoipapp\miniSipServer\msscli.exe" start= auto depend= tcpip</pre>
<p>Note: the option name includes equal sign and blank space sign. We can use miniSipServer web management system to administrate MSS. Please refer to following document for details.</p>
<p><a href="http://www.myvoipapp.com/docs/mss_services/web_management/index.html" target="_blank">http://www.myvoipapp.com/docs/mss_services/web_management/index.html</a></p>
<p>BTW, If run as windows service, the web management system will always start-up even without administrator password.</p>
<p>To start miniSipServer service:</p>
<pre>sc start minisipserver</pre>
<p>To stop miniSipServer service:</p>
<pre>sc stop minisipserver</pre>
<p>To delete miniSipServer service:</p>
<pre>sc delete minisipserver</pre>
<p>We need mention that you MUST stop and delete miniSipServer service firstly if you want to install or upgrade a new miniSipServer version.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2012/01/21/run-as-windows-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The most easy-to-use IP-PBX for Ubuntu/Linux</title>
		<link>http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/</link>
		<comments>http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/#comments</comments>
		<pubDate>Mon, 26 Dec 2011 04:31:33 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[Releases]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[ippbx]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[voip]]></category>
		<category><![CDATA[WINE]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=158</guid>
		<description><![CDATA[If you have tried miniSipServer on Windows platform, you can find it is so easy to configure or manage a IP-PBX because miniSipServer provides a perfect GUI interface. You can find it is very easy to do that on Ubuntu/Linux &#8230; <a href="http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>If you have tried miniSipServer on Windows platform, you can find it is so easy to configure or manage a IP-PBX because miniSipServer provides a perfect GUI interface.</p>
<p>You can find it is very easy to do that on Ubuntu/Linux because miniSipServer can support GUI interface on Ubuntu/Linux now!  WINE is unnecessary now!</p>
<p>Please visit our download page to download miniSipServer .deb packages according to your requirements:</p>
<p><a title="miniSipServer GUI download" href="http://www.myvoipapp.com/download" target="_blank">http://www.myvoipapp.com/download</a></p>
<p>After you download .deb file from our website, please click (or double-click) it to install MSS. No more actions! So easy, so funny.</p>
<p>After you finish your install, you will find miniSipServer at &#8220;Applications / Internet&#8221; group.</p>
<p>Following figure is a screenshot of MSS running on Kubuntu:</p>
<div id="attachment_159" class="wp-caption alignnone" style="width: 683px"><a href="http://www.myvoipapp.com/blog/wp-content/uploads/2011/12/mss_gui_en.png"><img class="size-full wp-image-159" title="MSS main windows on Kubuntu" src="http://www.myvoipapp.com/blog/wp-content/uploads/2011/12/mss_gui_en.png" alt="" width="673" height="359" /></a><p class="wp-caption-text">MSS main windows on Kubuntu</p></div>
<p>In another way, if you just want to run a command line sip server, you can also go to directory &#8220;/opt/sipserver&#8221; and find &#8220;msscli&#8221; which is a command-line miniSipServer and has the same core with GUI-miniSipServer.  You can manage and configure it through <a href="http://www.myvoipapp.com/docs/mss_services/web_management/index.html" target="_blank">web interface</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Block some extensions</title>
		<link>http://www.myvoipapp.com/blog/2011/12/13/block-some-extensions/</link>
		<comments>http://www.myvoipapp.com/blog/2011/12/13/block-some-extensions/#comments</comments>
		<pubDate>Tue, 13 Dec 2011 05:36:52 +0000</pubDate>
		<dc:creator>Gilson</dc:creator>
				<category><![CDATA[How-to]]></category>
		<category><![CDATA[miniSipServer ( local )]]></category>
		<category><![CDATA[block]]></category>
		<category><![CDATA[call level]]></category>
		<category><![CDATA[outgoing]]></category>

		<guid isPermaLink="false">http://www.myvoipapp.com/blog/?p=155</guid>
		<description><![CDATA[Sometimes, we need limit the call right of some extensions. For example, we want to limit only specific extensions can make out-group calls to outsides, others can only make calls between extensions. In MSS, we use &#8220;call level&#8221; feature to &#8230; <a href="http://www.myvoipapp.com/blog/2011/12/13/block-some-extensions/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Sometimes, we need limit the call right of some extensions. For example, we want to limit only specific extensions can make out-group calls to outsides, others can only make calls between extensions.</p>
<p>In MSS, we use &#8220;call level&#8221; feature to do it. By default, we don&#8217;t assign &#8220;call level&#8221; to any called number prefix in &#8220;analyze called number&#8221; table. That means all extensions can have the same right. To limit extensions, we should indicatedifferent &#8220;call level&#8221; to the called number prefix and assign relative &#8220;call level&#8221; right to special extensions, then they will have the right to make such calls.</p>
<p>For example, the default out-group call prefix is &#8220;9&#8243;. Please click menu &#8220;Dial plan /  Analyze called number&#8221; and edit or add a record whose prefix is &#8220;9&#8243; and route type is &#8220;external line&#8221;. In this configuration, we can select &#8220;call level 1&#8243; to this prefix &#8220;9&#8243;.</p>
<p>Then, please click menu &#8220;data / local users&#8221; and edit or add a local user. In the pop-up dialog, please click &#8220;Basic Call&#8221; tab and enable &#8220;Call level 1&#8243; to this extension.</p>
<p>After that, the extension has the &#8220;call level 1&#8243; right to make calls to outside by dialing &#8220;9xxxxx&#8221;. For others, since they don&#8217;t have &#8220;call level 1&#8243; right, their calls will be rejected when they dial &#8220;9xxxxx&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.myvoipapp.com/blog/2011/12/13/block-some-extensions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

