M. Ranganathan wrote: > Hello > > After the scrum this morning and further discussions with Robert, I am > revising some things with the call controller ( already): > > 1. http PUT will create the call. The URL format will be > https://domain:6666/callcontroller/method/agent/caller/callee?pin=xxxx >
If this is to feel like RESTful interface the URL should suggest that you have a virtual collection of calls with PUT or POST adding a call and GET retrieving its status. PUT something/something/something/call GET something/something/something/call This URLs look like you have a matrix of callers and callees. Is it really needed? > (The CallController, like any good superbeast, will run on port 6666 > and I am not giving up that port - sorry Woof! ) It's not like I am jealous or anything but I hope that call controller will run on whatever port sipXconfig will tell it to run. > > 2. http GET will query about the call setup status. The URL format will be > > https://domain:6666/callcontroller/caller/callee?pin=xxxx > > The status will only be returned for the call setup. This is a "fire > and forget" type of call controller. It uses REFER. The status will > be kept around only for the call setup time. i.e. it will disappear > when the Dialog that created the status is terminated. If that's the case it would be better if you used POST to create a call. POST can return a unique URL for a call that people can use to GET the call setup status. I am not sure how: https://domain:6666/callcontroller/caller/callee?pin=xxxx can be made unique enough to check for the call setup status. > > Any comments? Ask for changes now before I code it all up. > The PIN as a parameter is rather unconventional. Is this a user PIN? If so why do we need to pass it at all? Authorization (whatever method you choose) should be done independently from parameters. D. _______________________________________________ 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/
