On Fri, 2010-01-22 at 15:26 -0500, Peter Fowler wrote: > > Sometimes I have thoughts on Friday afternoons .. not too often. > Sometimes the thoughts > are good and sometimes not so much. > > Here is one: > > There is no standard governing the profile mechanism used by the > various SIP phones. It would be > nice to indicate in a profile that a key is to be programmed with a > label and an http URL. > > The URL would correspond to one of our REST APIs. When the user > presses the button the phone > Sends the request via HTTP along with the sip username and password > for (digest) authentication. > > SipX would process the request and send back a (short) response XML > document that the phone would > present on the LCD display. Would be displayed transiently or with a > softkey based on the markup > In the document. > > Examples of use cases would be > - Call center agent login/logout > - pickup call from voicemail .. ran to your desk just as the caller > got transferred to voicemail :( > - others? > > Avaya SIP firmware could be modified to support this mechanism to > provide competitive differentiation.
There is, however, a proposal for something very much like this at the IETF. There's a problem statement/analysis draft: http://tools.ietf.org/html/draft-ietf-bliss-ach-analysis-05 and some discussion of addressing the problem through a set of RESTful APIs. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
