> > Lee Davis wrote: > > I'm trying to track down some comprehensive documentation > on the Web > > Services offered by sipX/sipconfig. > > > > Of particular interest are the services used for ACD live call > > statistics and also the User and Phone administration. > > I've never used this myself, but... > > The ACD statistics are available from a separate SOAP service, see: > https://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXconfig/age > nt/lib/sip > xconfig-agent.wsdl > > I think the default port is 8110. > > Hope that helps. > > -Paul
Hi All, I thought I'd post a message with the findings I have made with Paul's help. By default the ACD statistics service runs on port 8120 and can be found at http://<switch_address>:8120/sipXconfigAgent This provides the services as described in the WSDL at https://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXconfig/agent/lib/sip xconfig-agent.wsdl As far as I can tell the service wont respond to requests for the WSDL directly, though I could be wrong. The information is the same as seen via the sipxconfig web interface for Agent/Queue/Call stats, though I think there are a few extra fields available via SOAP. Visual Studio 2005 seems unable to consume the services. It appears to have problems dealing with the complex data types (arrays of records) coming back from the service, though Wireshark traces show that the data is good. Furthermore VS2005 on 64bit XP has the addition problem of importing the WSDL expecting 64 bit integers but then interpreting the data as 32 bit integers (or possible the other way around) either way some manual adjustment was necessary after importing the WSDL. (change declarations of "long" to "Int32") I'll try my hand at some ruby and soap4r. Hopefully that will be a bit more successful. On the switch side, the ruby script is located at /usr/bin/sipxconfig-agent Find the right process etc by doing: # netstat -ap | grep 8120 to get the PID then # ps ax | grep <PID FOUND ABOVE> Should return something like <PID AS ABOVE>? Sl 1:55 /usr/bin/ruby /usr/bin/sipxconfig-agent (there's probably a more efficient way but I'm not a Linux guru) Regards, Lee. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
