I think he meant, the need to bounce RIS, not the existence of RIS, when it comes to fixing these types of issues. And I agree. The fact that it's still broken in 12.x is sad. Especially considering the new enhancements to registration visibility in 12.x.
On Fri, Aug 3, 2018 at 2:31 PM Ryan Huff <[email protected]> wrote: > Ya sorta have to have something like the RIS data collector if you think > about it. > > You wouldn’t want the GUI making individual direct calls to the database > for each device’s status every time you did something like display the list > of devices; the server would almost be unusable unless it had like 10 or 15 > cores, especially on large systems or if someone cranked up the pagination > from 50 to 250 .. etc. > > Thanks, > > Ryan > > On Aug 3, 2018, at 15:06, Jonathan Charles <[email protected]> wrote: > > RIS Data Collector restart fixed... seriously, I thought that went away in > CCM 4.3... > > > Jonathan > > On Fri, Aug 3, 2018 at 12:45 PM, Ryan Huff <[email protected]> wrote: > >> Odd. >> >> - Can one of those phones actually register to the publisher? >> >> - Maybe bounce the RIS DB service? >> >> Sent from my iPhone >> >> > On Aug 3, 2018, at 13:41, Jonathan Charles <[email protected]> wrote: >> > >> > So, in CUCM12, we are seeing devices rejistered fine to their primary >> CCM, but if you log into the Publisher, we are showing those same devices >> rejected... >> > >> > Checked dbreplication runtimestate, everything looks awesome.. >> > >> > Any ideas? >> > >> > >> > Jonathan >> > _______________________________________________ >> > cisco-voip mailing list >> > [email protected] >> > https://puck.nether.net/mailman/listinfo/cisco-voip >> > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
