Bogdan Brezoi wrote: > 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.
Which test fails? Existing one or the one that you just added? > 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. [...] I guess you can have some kind of "trigger discovery service" UI, but then you need to know which of the services are discovery services. Maybe a better approach is to invest some time in a discovery service that can detect new devices quickly (as opposed to the current service that does a good job with existing devices) - if we have something that monitors dhcp logs newly added phones would be discovered rather quickly. Both solutions are probably better tackled independently from the issue at hand. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
