<?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: Ascom/Swissvoice DECT Phone Hacking</title>
	<atom:link href="http://blog.ginkel.com/2009/01/ascom-swissvoice-dect-phone-hacking/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ginkel.com/2009/01/ascom-swissvoice-dect-phone-hacking/</link>
	<description>A Geek&#039;s Thoughts on Life, Arts, Software and Technology</description>
	<lastBuildDate>Fri, 30 Dec 2011 09:48:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Running Asterisk on a FRITZ!Box 7270 &#171; cat /dev/braindump</title>
		<link>http://blog.ginkel.com/2009/01/ascom-swissvoice-dect-phone-hacking/comment-page-1/#comment-324</link>
		<dc:creator>Running Asterisk on a FRITZ!Box 7270 &#171; cat /dev/braindump</dc:creator>
		<pubDate>Sun, 20 Dec 2009 13:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ginkel.com/?p=8#comment-324</guid>
		<description>[...] a week ago I started experimenting with running Asterisk on my FRITZ!Box 7270 to replace my DECT phone, which has been getting a bit long in the tooth, with a SIP client running on my new Motorola [...]</description>
		<content:encoded><![CDATA[<p>[...] a week ago I started experimenting with running Asterisk on my FRITZ!Box 7270 to replace my DECT phone, which has been getting a bit long in the tooth, with a SIP client running on my new Motorola [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philipp</title>
		<link>http://blog.ginkel.com/2009/01/ascom-swissvoice-dect-phone-hacking/comment-page-1/#comment-31</link>
		<dc:creator>Philipp</dc:creator>
		<pubDate>Thu, 26 Mar 2009 13:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ginkel.com/?p=8#comment-31</guid>
		<description>Thank you for this very valuable tip! My T-Com Sinus 500i (which is a Swisscom OEM build) had severe problems that couldn&#039;t be solved with the so-called factory reset.

Using the service menu and doing a real full reset did the trick.

Note to Sinus 500i users: The procedure is almost the same as described here, with the exception that a big black &#039;S&#039;-icon will show up in the upper left display corner upon completion of the keypress sequence. Navigating to that icon and pressing the right softkey will get you into the service menu.</description>
		<content:encoded><![CDATA[<p>Thank you for this very valuable tip! My T-Com Sinus 500i (which is a Swisscom OEM build) had severe problems that couldn&#8217;t be solved with the so-called factory reset.</p>
<p>Using the service menu and doing a real full reset did the trick.</p>
<p>Note to Sinus 500i users: The procedure is almost the same as described here, with the exception that a big black &#8216;S&#8217;-icon will show up in the upper left display corner upon completion of the keypress sequence. Navigating to that icon and pressing the right softkey will get you into the service menu.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

