> Revision 17066 introduces the infrastructure for a new feature in > sipXecs: All of the line appearances (registrations) made by each > phone > are identifiable as a group. We will be sending information about how > to use this feature in the future. But installing the infrastructure > required changing the "credentials" database table, and the result is > that when you revise your development system across the revision > 17065/17066 boundary, you have to go to the Servers page and send > profiles. If you don't do that, no operation requiring authentication > of an originating phone will work -- that includes registering and > making calls. > > Phones configurations do not need to be sent for the phones to work, > but > until a new configuration is generated, the phone's registrations will > not be identified. > > Phone identifications of registrations can be seen on the Diagnostics - > > > Registrations page. > > Dale >
Dale very nice addition. At some point I am guessing we could then control reboots of phones that share users. > > _______________________________________________ > 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/ _______________________________________________ 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/
