________________________________________ 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/
