On Wed, Jul 14, 2010 at 1:39 PM, paul gore <[email protected]> wrote:
> ---------- Forwarded message ---------- > From: paul gore <[email protected]> > Date: Wed, 14 Jul 2010 11:45:53 -0400 > Subject: Re: Call events and call control command API? > To: "WORLEY, Dale R (Dale)" <[email protected]> > > Based on what I have seen in the wiki it seems like call resolver has > most information about all calls since it able to generate real time > cdrs. So based on that all I need is to be able to subscribe to call > resolver data. Can't be that difficult can it? > And I need to be able to cancel a call in progress, I guess sip proxy > service should have abilty to cancel a call, it just needs to be > exposed as web service. > My 2 cents... a superadmin should be able to cancel any call in progress from the active calls screen, but this has never been made available. The real question is how to inject the BYE into a call from the proxy without either UA or gateway/trunk being accessed. So while oyu might remove the call from the CDR screen, it needs to be messaged in a way that all involved parties (conference server, UA's, gateways and sbc's) can recognize. I'm not so sure it is as simple as exposing a web service. It needs to be constructed. In some gateways I can cancel ALL calls, but not specific ones. It probably means it is not as simple as anyone might think. > > On 7/13/10, WORLEY, Dale R (Dale) <[email protected]> wrote: > > ________________________________________ > > From: [email protected] > > [[email protected]] On Behalf Of paul gore > > [[email protected]] > > > > how difficult it is to add API which would allow receiving call events > > and sending call control commands via a socket or a web service > > similar to what Freeswitch does? > > Can anybody point me into the right direction which modules, code I > > should look at? > > _______________________________________________ > > > > sipXecs is not architected so that the central server processes know what > > calls are happening at any given time; the philosophy is that smart > > endpoints know and manage their own state. So there isn't such an API > and > > it would be difficult to build one. > > > > However, an external process that wanted to know the status of a given > > device can monitor the device itself (using the dialog event package) and > > perform a considerable number of call-control operations via SIP > operations > > using the information it obtains in that way. In SIP, this is called > > "third-party call control" (I don't know if that term has wider use), and > is > > often abbreviated "3PCC". See for example, RFC 3725, RFC 5850, and > search > > for "3pcc" at http://datatracker.ietf.org/doc/search/ . > > > > Dale > > > _______________________________________________ > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
