<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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>Comments on: Remote Call Forward an Extension without a phone connected</title>
	<atom:link href="http://www.scscblogs.com/catalysttech/index.php/2009/06/remote-call-forward-an-extension-without-a-phone-connected/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scscblogs.com/catalysttech/index.php/2009/06/remote-call-forward-an-extension-without-a-phone-connected/</link>
	<description>the Tech Support Group of Catalyst Telecom</description>
	<lastBuildDate>Mon, 26 Apr 2010 21:02:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: mikeo</title>
		<link>http://www.scscblogs.com/catalysttech/index.php/2009/06/remote-call-forward-an-extension-without-a-phone-connected/comment-page-1/#comment-35</link>
		<dc:creator>mikeo</dc:creator>
		<pubDate>Thu, 18 Jun 2009 16:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.scscblogs.com/catalysttech/?p=582#comment-35</guid>
		<description>This was suggested by an Avaya engineer. Call forwarding does not require a button with lights. Analog telephones as well as system phones can be forwarded using the feature code and there is no visual indication of forwarding being active. I agree to make sure that the End User is aware up front that in the instance of a power failure that the RCF will be set to off and will need to be reset. This is very useful for those end users with outside sales reps who do not have a need for a desk phone.</description>
		<content:encoded><![CDATA[<p>This was suggested by an Avaya engineer. Call forwarding does not require a button with lights. Analog telephones as well as system phones can be forwarded using the feature code and there is no visual indication of forwarding being active. I agree to make sure that the End User is aware up front that in the instance of a power failure that the RCF will be set to off and will need to be reset. This is very useful for those end users with outside sales reps who do not have a need for a desk phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coolkirk</title>
		<link>http://www.scscblogs.com/catalysttech/index.php/2009/06/remote-call-forward-an-extension-without-a-phone-connected/comment-page-1/#comment-34</link>
		<dc:creator>coolkirk</dc:creator>
		<pubDate>Thu, 18 Jun 2009 13:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.scscblogs.com/catalysttech/?p=582#comment-34</guid>
		<description>This may work but is not supported by Avaya. With out a ‘real’ set with the feature programmed on button with a LED, the user won’t know if the feature is off or on until they figure out they are not getting phone calls. For instance, with a power failure this feature is reset to OFF – no phone no LED – user won’t know until someone complains. But that maybe alright if the client understands that up front.</description>
		<content:encoded><![CDATA[<p>This may work but is not supported by Avaya. With out a ‘real’ set with the feature programmed on button with a LED, the user won’t know if the feature is off or on until they figure out they are not getting phone calls. For instance, with a power failure this feature is reset to OFF – no phone no LED – user won’t know until someone complains. But that maybe alright if the client understands that up front.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
