I am suggesting a way to define a template of a call flow which is input to a customizable user agent to define the expected signaling behavior of the user agent when it participates in a call flow. I envision this being the basis for defining new extensions. Essentially, the extension proposer can define the signaling behavior for the user agent and make it available as a SIP XML file, Your device has a SIP XML browser that can read the XML defining the behavior of the extension and can interact with a service script that runs on your device through event bindings that essentially bind a named fragment of code with a string in the SIP XML script. Thus extensions can be quickly proposed and deployed. If browser plugins for SIP XML become available then the extension can run in your SIP XML enabled browser in much the same way that HTML runs today.
Indeed, one can imagine combining SIP XML and HTML to quickly script HTML + SIP enabled clients.
Hope this answers your question.
Ranga.
[EMAIL PROTECTED] wrote:
Hi--
i'm not read your paper and presentation yet...
But i've a simple question:
which are the difference between the use of XML scripts to build SIP services
and the use of CPL ... ?
CPL is not considered in 3GPP for the develop of services (if I remember well !!!)
and maybe the use of OSA, considered in 3GPP, for this use it not so userfriendly.
my doubt about your proposal is that it seems to be a replied CPL, isn't it?
Sal
personal mail: [EMAIL PROTECTED]
work mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
-----Original Message-----
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> on behalf of "M. Ranganathan" <[EMAIL PROTECTED]>
Sent: Wednesday, November 27, 2002 2:40 PM
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: [Sipping] Standardizing the representation of SIP call flows using XML.
Dear SIP enthusiats:
I am working on a project which involves defining XML scripts to describe interactions between communicating SIP endpoints (user-agents). These scripts are used as an input to a customizable user agent to build build SIP services and may be an interesting way to web host newly proposed SIP extensions in a standardized way. It may also be a nice way of quickly bringing new extensions to market without having to go through the long API standardization process.
Here is a pointer to a talk I presented on the subject:
http://www.antd.nist.gov/proj/iptel/ssp.ppt
and a paper we submitted :
http://www.antd.nist.gov/proj/iptel/src/nist-sip/nist-sip-1.1/docs/white-paper/whitepaper.pdf
The paper is in the written in the context of testing SIP call flows but I think it can be extended to build services.
Our web tester which you can also access by visiting our project page at www.antd.nist.gov/proj/iptel incorporates these ideas for a working demonstration.
I invite your participation in an interest group on the topic if you have an interest in firming up these ideas and (provided there is sufficient interest) jointly submitting a proposal to some (as yet undetermined) standardization body. If you are interested, please send me mail and if there is sufficient interest I will form a mailing list for disussing these ideas.
I am posting both the sip-implementors and the sipping mailing list in the hope that there will be some interest in being able to standardize the representation of call flows for SIP extensions. Please forgive possible duplication of this mail in your already crowded mailboxes.
I look forward to hearing from you on the topic.
Regards
Ranga.
M. Ranganathan
N.I.S.T. Advanced Networking Technologies Division 100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899
tel:301-975-3664 fax:301-590-0932
http://w3.antd.nist.gov/index.html mailto:[EMAIL PROTECTED]
Advanced Networking Technologies for the people!
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
