[Discussion moved here from #sipx] Hello,
I am putting together a library for third party call control in sipx commons. That library can either be used stand alone or be incorporated into a process (henceforth called the SipXCallController ). Lets say we are agreed on a stand alone process to which you can send REST commands to make calls. This process needs to be able to access the SIP password of the calling party so it can effective "impersonate" that caller when it launches the third party call setup. For this, I assume that the REST method will have the SIP password of the user as one if its parameters. The other option is for the SipXCallController to read the database that stores all the clear text passwords. In that case, I can make the assumption that the caller is trusted (will use authenticated HTTPS to make the call) and hence SipXCallController will just trust the caller, retrieve the SIP passwords from the database and make the call on the callers behalf. The caller in this case would just provide its own SIP user name and the called party user name and domain. A third approach would be to just provide a java library that can be imbedded into any trusted process that supplies user credentials drop the notion of a stand alone SipXCallController. Which would be the preferred way to proceed on this? Thanks Ranga. -- M. Ranganathan _______________________________________________ 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/
