From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20110630074533.GK2315@fangle.proxima.alt.za> References: <20110626051734.GA2315@fangle.proxima.alt.za> <20110630074533.GK2315@fangle.proxima.alt.za> Date: Thu, 30 Jun 2011 18:54:04 +1000 Message-ID: From: Bruce Ellis To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] SIP Topicbox-Message-UUID: f7d98042-ead6-11e9-9d60-3106f5b1d025 I wrote a SIP proxy in Limbo, a decade and a bit apast. Can't find it off-hand. Maybe it's in VNI or discarded by the the IBU mafia. brucee On Thu, Jun 30, 2011 at 5:45 PM, Lucio De Re wrote: > 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. =A0I 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. =A0But it's good > to know where to look. > > ++L > >