I agree sipxconfig is not the right resting place (only slight pun intended). If more generally SipX supported A variety of REST APIs then even a freeswitch based Application would make use of them. The APIs may be telephony related but also telephony presence, things that Freeswitch itself or JAIN-SIP cannot do or cannot do easily.
Peter -----Original Message----- From: Andy Spitzer [mailto:[email protected]] Sent: Wednesday, July 15, 2009 11:58 AM To: Fowler, Peter (CAR:9D10); [email protected] Subject: Re: [sipX-dev] Click to Call REST API generalization Woof! On Wed, 15 Jul 2009 11:41:04 -0400, Peter Fowler <[email protected]> wrote: > I would like to generalize/extend this URL in a backwards compatible > way as follows > https://username:password@<domain_name:8443/sipxconfig/rest/call/<targ > et>?source=<source> Not a bad suggestion, for the general case. I personally think the terms "target" and "source" are poor choices, but the idea is sound no matter what the words used. However: > As part of my Personal Assistant work I need the ability to initiate a > call between two parties. Please don't tell me you want sipXconfig to do that for you! That makes no sense in the general scheme of things. Either make the call using FS, or using JAIN-SIP (which is what sipXconfig does). Adding yet another dependency on yet another process (and let's not forget that sipXconfig was never supposed to HAVE to be part of an installation, or even running at all times, even though at the moment it seems more and more is required of it), is not good architecture. The current dependencies of sipXivr on sipXconfig (changing user PINs and AA "special" mode via REST) are already more than there should be. Please let's not add more. --Woof! _______________________________________________ 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/
