<?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: Lippis Report Issue 89: Session Initiation Protocol (SIP): An Industry Update</title>
	<atom:link href="http://lippisreport.com/2007/09/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2007/09/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/</link>
	<description>Resources for Network / IT Business Decision Makers</description>
	<lastBuildDate>Mon, 21 May 2012 12:58:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: ipad application</title>
		<link>http://lippisreport.com/2007/09/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/comment-page-1/#comment-250214</link>
		<dc:creator>ipad application</dc:creator>
		<pubDate>Sun, 09 Jan 2011 06:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/2007/09/12/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/#comment-250214</guid>
		<description>-----------------------------------------------------------
&quot;I have been reading your entries during my afternoon break, and I have to admit the whole article has been very enlightening and very well composed. I  thought I would let you know that for some reason this blog does not display well in World wide web Explorer 8. I wish Microsoft would quit changing their software. I  have a question for you. Do you thoughts exchanging weblog roll links? That would be really cool! &quot;</description>
		<content:encoded><![CDATA[<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
&#8220;I have been reading your entries during my afternoon break, and I have to admit the whole article has been very enlightening and very well composed. I  thought I would let you know that for some reason this blog does not display well in World wide web Explorer 8. I wish Microsoft would quit changing their software. I  have a question for you. Do you thoughts exchanging weblog roll links? That would be really cool! &#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VoIP, Led by SIP, Forges Ahead - Caller IP</title>
		<link>http://lippisreport.com/2007/09/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/comment-page-1/#comment-43309</link>
		<dc:creator>VoIP, Led by SIP, Forges Ahead - Caller IP</dc:creator>
		<pubDate>Sun, 25 Nov 2007 15:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/2007/09/12/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/#comment-43309</guid>
		<description>[...] The folks at the Lippis Group do their usual comprehensive job in this report on SIP. Indeed, the piece has a double benefit. On one hand, it breaks overall SIP technology into three easier-to-understand elements: SIP connections, SIP endpoints and the SIP platform. The piece defines each of these elements and, perhaps most importantly, lists the main players in each. For instance, the key vendors in the SIP connections category are Avaya, Cisco, Siemens, Nortel, Alcatel, ShoreTel and Mitel. The piece says that many service providers have entered the trunking segment during the past two years. In the U. S., new service providers include AGN Networks, AT&amp;T, BandTel, Global Crossing, Onvoy, Paetec, Verizon Business, McLeodUSA, Qwest and TelePacific. [...]</description>
		<content:encoded><![CDATA[<p>[...] The folks at the Lippis Group do their usual comprehensive job in this report on SIP. Indeed, the piece has a double benefit. On one hand, it breaks overall SIP technology into three easier-to-understand elements: SIP connections, SIP endpoints and the SIP platform. The piece defines each of these elements and, perhaps most importantly, lists the main players in each. For instance, the key vendors in the SIP connections category are Avaya, Cisco, Siemens, Nortel, Alcatel, ShoreTel and Mitel. The piece says that many service providers have entered the trunking segment during the past two years. In the U. S., new service providers include AGN Networks, AT&amp;T, BandTel, Global Crossing, Onvoy, Paetec, Verizon Business, McLeodUSA, Qwest and TelePacific. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sflau01</title>
		<link>http://lippisreport.com/2007/09/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/comment-page-1/#comment-37055</link>
		<dc:creator>sflau01</dc:creator>
		<pubDate>Thu, 13 Sep 2007 15:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/2007/09/12/lippis-report-issue-89-session-initiation-protocol-sip-an-industry-update/#comment-37055</guid>
		<description>Hi, 

I have difficulty downloading some whitepapers identified on the right hand side of this document. Ths download seems OK but an error prevents it to be displayed.  Is there a way to rectify this problem.  The Whitepapers that I am interested in are:
1. Session Border ControllerDelivering Interactive Communications Across IP Network Borders
2. SIP Trunking Benefits and Best Practices
3. Integrating Telephony Services Into .NET Applications

Thanks,
Stephen Lau</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I have difficulty downloading some whitepapers identified on the right hand side of this document. Ths download seems OK but an error prevents it to be displayed.  Is there a way to rectify this problem.  The Whitepapers that I am interested in are:<br />
1. Session Border ControllerDelivering Interactive Communications Across IP Network Borders<br />
2. SIP Trunking Benefits and Best Practices<br />
3. Integrating Telephony Services Into .NET Applications</p>
<p>Thanks,<br />
Stephen Lau</p>
]]></content:encoded>
	</item>
</channel>
</rss>

