Thanks for your answer. I was really looking for some kind of generic CTI API. I agree that this would be a lot of work for such a rare case and as this would be code that would not really be useful for the general release code I can understand why you would not want to merge it in. What have other people done when making customer specific changes to the code?
-----Original Message----- From: Scott Lawrence [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 8:57 AM To: Simon Shaw Cc: Subject: Re: [sipX-dev] Extending functionality for sipx from newbie On Wed, 2008-07-30 at 03:16 +0300, Simon Shaw wrote: > The scenario I am thinking about is the case where Joe works in open > space and normally run's a SIP soft-phone from his PC that is registered > to the proxy. > Joe is currently in Bob's office and is not aware that his PC has been > shut down by a virus/windows update/IT maintenance. > Tina works in the next cubicle to Joe. > Joe, who is currently in Bob's office, hears Tina's phone ring, but > mistakes it for his own. > Joe attempts to pickup the ringing phone from Bob's office by dialing > *78<Joe's extension> > Pickup fails and somehow triggers my custom code. Well, you could extend the pickup module to do something special if it fails to find an early dialog to pick up... Seems like a lot of work for a rare case... -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
