Re: [splices] SIP INVOKE method v1

["Hutton, Andrew" <[e-mail]>]

Hi Dale,

I think the problem is that we don't have any specified requirements so we don't know what the boundaries are. 

What has been specified so far already looks like it is trying to do CTI type things and for that we know the list of possible services is endless. The most relevant standards would probably be ECMA-269 and ECMA-323 (http://www.ecma-international.org/publications/standards/Ecma-323.htm) if you want to see the XML for this.

I don't see how it is really possibly to limit this to a small set of actions as once the mechanism is implemented there will always be requirements to add more actions.

Regards
Andy


> -----Original Message-----
> From: Worley, Dale R (Dale) [mailto:[e-mail]]
> Sent: 14 June 2011 18:33
> To: Hutton, Andrew; Shekh-Yusef, Rifaat (Rifaat); Paul Kyzivat;
> [e-mail]
> Subject: RE: [splices] SIP INVOKE method v1
> 
> > From: Hutton, Andrew [[e-mail]]
> >
> > The list of potential actions and associated parameters is huge and
> > for this kind of problem I believe that an XML body would be a much
> > better solution. I guess I much prefer XML to BNF.
> 
> I'd feel much more comfortable if we settled on either:
> 
> 1) a small number of actions
> 
> 2) to use an appropriate subset of an existing CTI standard
> 
> In the latter case, could someone provide a pointer to the standard?
> 
> Essentially, INVOKE is to provide an interface to a command set, and
> we need to have some idea what the outer limits of the command set
> will be.  Only then can we choose a good way to represent the commands
> within a SIP request.
> 
> Dale