M. Ranganathan wrote: [...]
>> I guess I just did not understand the URL. Do you mind publishing an >> example (curl call or something similar) of what the client would have to >> send to establish the call. > > We have three entities : agent, caller and callee. > > If you want the call controller to masquerade as 201 from sipxconfig > and establish a call from 201 to 202 here is the syntax. > > echo "Initiating a call between 201 and 202 as 201" > curl -k -T curlcommand.sh > https://sipxtest.sipxtest.net:6666/callcontroller/refer/201/201/202 > sleep 20 > echo "Query call setup progress for call between 201 and 202 as 201" > curl -k https://sipxtest.sipxtest.net:6666/callcontroller/refer/201/201/202 > > > The refer is there because I am not sure if we want to support other > things (such as INVITE initiated third party call control ) > Based on my (limited) experience with coming up with REST URI schemes: 'method' (refer vs. invite) should be an optional parameter and not the part of the URI (especially since only REFER is supported) 'agent' should be a parameter as well - if you use principal based authentication (BASIC, DIGEST), agent will be determined by it. If you use "location" based authentication then the caller does need to specify it, but since it becomes optional it just fits better as a parameter. Those changes would make the API easier to explain and use. I guess we talked about it before on this list: I am really not sure what to think about 'caller' - is there any restriction on what can be passed here? What stops a user from initiating calls from anyone to anyone if both caller and callee can be specified? 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/
