<?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: Memo to Asterisk PCI Card Manufacturers:  Please Build This!</title>
	<atom:link href="http://www.voipsupply.com/blog/memo-to-asterisk-pci-card-manufacturers-please-build-this/feed" rel="self" type="application/rss+xml" />
	<link>http://www.voipsupply.com/blog/memo-to-asterisk-pci-card-manufacturers-please-build-this</link>
	<description>Everything you need to know about VoIP</description>
	<lastBuildDate>Fri, 18 May 2012 11:50:55 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: roderickm</title>
		<link>http://www.voipsupply.com/blog/memo-to-asterisk-pci-card-manufacturers-please-build-this/comment-page-1#comment-23812</link>
		<dc:creator>roderickm</dc:creator>
		<pubDate>Mon, 08 Dec 2008 18:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.voipsupply.com/?p=4572#comment-23812</guid>
		<description>When I visit my favorite online t-shirt seller Threadless.com, they offer each t-shirt design in a variety of sizes, colors, and types (guys tee, girly tee, hoody, etc). They helpfully group the options together on one page to show all the configurations available for that design, while showing the variation in pricing and inventory/availability.

You might consider the same for your online store, grouping the combinations in a condensed, easy-to-understand way. Perhaps a dropbox for the 28 FXO/FXS choices and a checkbox for whether to include hardware echo cancellation. That would reduce 56 SKUs to one sales page for the PCI cards, and you might do the same for the PCIe base card, the AEX2400.

You mentioned environmental concerns -- building a card that included twice the number of ports required (just in case a customer wants to change all their FXO ports to FXS) is wasteful by definition... and more expensive for everyone involved. If given the choice between an all-FXO card and a switchable FXO/FXS card that cost say, 65-85% more, how many customers would pay the premium?

It&#039;s actually very &quot;green&quot; to offer 112 different configurations with just five parts: PCI base card, PCIe base card, echo cancelling DSP module, 4-port FXO module, and 4-port FXS module.</description>
		<content:encoded><![CDATA[<p>When I visit my favorite online t-shirt seller Threadless.com, they offer each t-shirt design in a variety of sizes, colors, and types (guys tee, girly tee, hoody, etc). They helpfully group the options together on one page to show all the configurations available for that design, while showing the variation in pricing and inventory/availability.</p>
<p>You might consider the same for your online store, grouping the combinations in a condensed, easy-to-understand way. Perhaps a dropbox for the 28 FXO/FXS choices and a checkbox for whether to include hardware echo cancellation. That would reduce 56 SKUs to one sales page for the PCI cards, and you might do the same for the PCIe base card, the AEX2400.</p>
<p>You mentioned environmental concerns &#8212; building a card that included twice the number of ports required (just in case a customer wants to change all their FXO ports to FXS) is wasteful by definition&#8230; and more expensive for everyone involved. If given the choice between an all-FXO card and a switchable FXO/FXS card that cost say, 65-85% more, how many customers would pay the premium?</p>
<p>It&#8217;s actually very &#8220;green&#8221; to offer 112 different configurations with just five parts: PCI base card, PCIe base card, echo cancelling DSP module, 4-port FXO module, and 4-port FXS module.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

