You are right in your statements below. A proxy server is a service (albiet a specialized one). Indeed we deployed a test service at
http://www.antd.nist.gov/sip-wit
which relies on a proxy and a xml based service container. It has some warts and wrinkles but appeared to be a reasonable thing to do.
In general I am suggesting a customizable user aget that takes an xml script as an input. potentially this can work in conjunction with a proxy server (there are several good server side solutions already) or on a client and serve as a vehicle to quicky deploy extensions.
I think it is possible to do this on the client side and especially when combined with other client side technologies like plugins and html browsers, you can quickly specify and deploy powerful extensions.
Regards
Ranga.
[EMAIL PROTECTED] wrote:
ok--
i agree... it would be nice to have a way to quickly
deploy a service (principaly sip extensions) on the client!!!
your proposal i so interesting!!!
what standardization body do you have in mind?
Maybe i've mis-understood the use of the word service
"Any sip application is service - including a softphone"
.. you are right. But sip server is a service as well!!!
And i'm interested to the implications of XML scripts on Server.
will SIP-XML scripting be able to modify server call flow as well?
Sal
-----Original Message-----
From: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> on behalf of "M. Ranganathan"
<[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 6:55 PM To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Cc: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> Subject: Re: [Sip-implementors] Re: [Sipping] Standardizing the
representation of SIP call flows using XML.
Yes. I think it would be nice to have a way to quickly deploy services
on the client (user agent). Perhaps you are mis-understanding the use of
the word service. Any sip application is service - including a
softphone.
Regards
Ranga.
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> wrote:
Hi
i'm not understanding your proposal very well
You propose the use of CPL on the SERVER SIP (and for you, this is the best solution?) and XML to extend quickly and easily services on User Agent
side!!!
sal
-----Original Message-----
From: "[EMAIL PROTECTED]"
<mailto:[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> on behalf of "M.
Ranganathan" <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 5:46 PM
To: "[EMAIL PROTECTED]" <mailto:[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> Cc: "[EMAIL PROTECTED]"
<mailto:[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> Subject: [Sip-implementors] Re: [Sipping] Standardizing
the representation of SIP call flows using XML.
Good question. CPL is a way to build services in a safe fashion
(mostly for proxy servers the way I understand it). CPL ensures safety
by constraining the programming model. If you have a new SIP
extension for which you want to define a signaling behavior then CPL would not
do the trick. CPL is meant to run essentially on Proxy servers where a
CPL script sees all the signaling and can intervene in the
signaling.
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] <mailto:[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]
<mailto:[EMAIL PROTECTED]>
work mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: "[EMAIL PROTECTED]"
<mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> on behalf of "M. Ranganathan"
<[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 2:40 PM
To: "[EMAIL PROTECTED]"
<mailto:[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> , "[EMAIL PROTECTED]"
<mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <mailto:[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
<http://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
