From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 30 Jun 2011 09:45:33 +0200
From: Lucio De Re <lucio@proxima.alt.za>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20110630074533.GK2315@fangle.proxima.alt.za>
References: <alpine.OSX.2.00.1106251407010.5932@haldir.orthanc.ca>
	<20110626051734.GA2315@fangle.proxima.alt.za>
	<alpine.BSF.2.00.1106291527300.37792@legolas.orthanc.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1106291527300.37792@legolas.orthanc.ca>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [9fans] SIP
Topicbox-Message-UUID: f7d43d62-ead6-11e9-9d60-3106f5b1d025

On Wed, Jun 29, 2011 at 03:34:32PM -0700, Lyndon Nerenberg wrote:
>
> I'd be curious to see what you came up with.
>
It was the emulation of a handset, on screen, driving an interface
adapter that communicated digitally with a small PABX.  I can post the
ancient Inferno code as is on my web site, but to update the code will
take a while, which seems to dovetail with your own requirements.

> My thoughts we around using a modified version of the plumber to
> drive the routing logic, but it's all very hypothetical right now.
> I had no intention of doing media conversion or any of that sort of
> thing.
>
I hadn't thought of that, it does sound useful as a general solution.

> As to the volume of SIP RFCs, the only way to make this work is to
> implement just the bare minimum of SIP required to do the job. A
> friend of mine has done a couple of from-scratch SIP proxies and has
> been a wealth of information about how not to do this ;-)
>
I do wish programmers were more keen to document exactly this type of
understanding and save others repeating their mistakes.  But it's good
to know where to look.

++L