Hi, Regarding this issue, i have a patch with the client-side prepared. I still have to write some more tests ( test for the web service - in ruby i think ) before I'll put the patch but for now, on my machine , the precommit operation fails at integration tests because of the jain-sip related code i suppose. Meanwhile, i would like to mention few questions/observations about the server-side that Paul McDaid and I came with: - what happens when let's say an user adds some phones to the network and wants the discovery facility to run immediately so he will see the devices on sipXconfig UI ? The discovery operation will probably depend on the schedule. Do you think that the schedules for the discovery should/will be configurable from the UI ? . I think the main idea is how to make an user to trigger the running of the discovery facility after he added a new device to the network. - if the sipXconfig will be temporary out of function but the discovery facility still works and sends a list of devices, i think then it should store this list somewhere/somehow and retry to send it until sipXconfig is up and running again. This will probably the case if discovery facility sends only the latest devices found. However, if the discovery will send a list with all the devices on the net, then this problem will disappear.
Please share your thought/comments on this. Thanks, Bogdan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
