Hey Rob

I'm really interested on see what they answer on this one.

i've tried before to do that but since the service is only used during the login and logout just a restart wouldn't do the trick

once the phones are pushed the EM profile they do not use the service until the automatic log-out timer expires

you're right on the other post, if you change any parameter like simultaneous login, logout max time, etc you need to logout and login for they to work

i know for a fact that in order to perform the logout a specific url string needs to be sent to the EM server so the service receives the request and performs all the process of pushing the log-out profile the phone has configured

i had once a cu who did a batch job using the MACs from the phones and told me it worked just fine

i'd really want to know what Jordi says if he tries the tomcat restart

HTH

javalenc

if this helps, please rate

Hi all,

As we did the upgrade off-hours, the most part of the phones were already logged out due to timeout. Just around 50 phones were still logged in and we decided to log them out manually.

Anyway it will be interesting to find something to do it automatically in case it's necessary.

I'm sorry but I finally didn't test the restart of the tomcat service.

Thanks anyway,

Jordi.

Hi All,

I've just done an upgrade from 4.2 to 6.1.3 However as this was done during office hours I was unable to log out any phones. I ran the DMA utility on the publisher without any errors. Once the new 6.1.3 publisher was built and brought online and the sub turned off all phones moved over seamlessly. However there were no services listed this was fixed after resetting all phones. I did experience tapi issues which was resolved by users logging out of their phones and back in.

Hope this helps.

Brett

yeah, we have done a 5000+ phones cluster as well, you need to reset the phones as the url's are different in 6.1

we did bulk logoff all users on the staged publisher, and bulk logged them in once the system was up, no issues at all