<?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: How many Mongrels or FastCGI processes do I need?</title>
	<atom:link href="http://ertw.com/blog/2008/11/19/how-many-mongrels-or-fastcgi-processes-do-i-need/feed/" rel="self" type="application/rss+xml" />
	<link>http://ertw.com/blog/2008/11/19/how-many-mongrels-or-fastcgi-processes-do-i-need/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 26 Jul 2010 03:57:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: T Hodgen</title>
		<link>http://ertw.com/blog/2008/11/19/how-many-mongrels-or-fastcgi-processes-do-i-need/comment-page-1/#comment-104857</link>
		<dc:creator>T Hodgen</dc:creator>
		<pubDate>Mon, 19 Jul 2010 06:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://ertw.com/blog/2008/11/19/how-many-mongrels-or-fastcgi-processes-do-i-need/#comment-104857</guid>
		<description>Sean,

I worked for a company in the early 1980 (we used I8086 processor, 5mb drive, 512k memory with 4 serial ports) that provided a Management Information System for call centers operated by the former Bell Operating Companies.  We had over 300 of them around the US, in very large call centers.

Part of the product was a scheduling program that used Erlang B and C, along with Poisson Theory to create schedules for the agents shifts, including breaks, lunches, vacations, doc appointments, etc. based on past call history, and along with future predictions of incoming calls based on that history, with most recent giving higher presendence, and using queue time, abandons, busy, etc.   It worked very well, to the point that we adjusted our predictions every half hour to make minor adjustments, follow union labor rules, etc.

SHould be fun stuff to learn!

I&#039;ve read some notes about your video on troubleshooting VOIP with Wireshark, but can&#039;t find a link to it - although I&#039;m scouring your blog now hoping to find it.

Can you comment to me on if you know of any good analytical tools that work with wireshark, or are standalone, that do a good job of analyzing SIP?  I&#039;m hoping to find something that can see errors in the SIP signalling, etc. that can be used for troubleshooting in the field.

Thanks for any help you can offer.</description>
		<content:encoded><![CDATA[<p>Sean,</p>
<p>I worked for a company in the early 1980 (we used I8086 processor, 5mb drive, 512k memory with 4 serial ports) that provided a Management Information System for call centers operated by the former Bell Operating Companies.  We had over 300 of them around the US, in very large call centers.</p>
<p>Part of the product was a scheduling program that used Erlang B and C, along with Poisson Theory to create schedules for the agents shifts, including breaks, lunches, vacations, doc appointments, etc. based on past call history, and along with future predictions of incoming calls based on that history, with most recent giving higher presendence, and using queue time, abandons, busy, etc.   It worked very well, to the point that we adjusted our predictions every half hour to make minor adjustments, follow union labor rules, etc.</p>
<p>SHould be fun stuff to learn!</p>
<p>I&#8217;ve read some notes about your video on troubleshooting VOIP with Wireshark, but can&#8217;t find a link to it &#8211; although I&#8217;m scouring your blog now hoping to find it.</p>
<p>Can you comment to me on if you know of any good analytical tools that work with wireshark, or are standalone, that do a good job of analyzing SIP?  I&#8217;m hoping to find something that can see errors in the SIP signalling, etc. that can be used for troubleshooting in the field.</p>
<p>Thanks for any help you can offer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
