Ip virtual office problems

[dasan64]

We have a CS1000E with 20 SMG (geo redundancy). Virtual Office login is high frequently used by the customer. At times a person will logout from the remote location and come back to their office and the phone displays LOGGED OUT. I stat the phone and it is unregisted. The easy solution is to have them unplug and and plugin the phone to get registered but this is not the way how it should work.
Normaly the home set should be register automatically. We are using the automatic logout feature for virtual office. This means every morning at 01 am all virtual office logins will be canceled. The sets
should reregister with the home TN, but this doesn´t work correctly. Most of the sets are loged out. Any ideas to solve this problem.???
rgds
Andreas

 

[fritzthecat]

Hello Andreas,
what is your system type and release, there are a lot of problems known on Virtual office feature and there are patches available, I do have issues on Rel 5.5 and 6.0 so there are patches available for some issues
regards
Fritz

 

[dasan64]

Hi Fritz

System is on rel. 5.5 and has a follower signalling server
at the main site. I have seen in the sigserver (isetShowByTN) that the sets after automatic logout (vo alog) staying in the lockout state. User must press then the home button for reregister. Could this be a problem with the loadbalancing between the sigservers??? I have seen a bulletin in the nortel knowledge base in which is described that the follower signalling server must have the same host name as the leader. In our configuration we are using different hostnames. So now i am a little bit confused.

 

[dasan64]

Sigserver and callserver are cppm.

 

[fritzthecat]

That should be ok, as far as I remember, only user logged into the same SS are logout and the set goes back to its normal TN DN user originaly log into different SS do have this behaviour
try to look for users housing on the same ss they should be logged out normaly

regards
Fritz

 

[dasan64]

i have done some tests on site. Virtual office login and logout , when it is performed manually works fine. This means the home set is reregisted automatically after logout.
No matter if the two sets are on the same or on different
signallingservers.
With the alog Feature the home set returns only automatically if both sets are on the same signallingserver.
If the sets are on different signallingservers (load balancing) after logout the home set stil remains with the logout screen. User must press the home key to reregister the set. But when the user is still on the remote side he is not able to do this. And this is our biggest problem.




oam> 06/09/2010 14:00:01 LOG0006 SET: 10.20.130.32 TN 104-00-04-29 Terminal offline
06/09/2010 14:00:01 LOG0005 VTM: 10.20.130.32 Unregistered, terminal = 0x2e10296c, device = 0x2e20d4fc
06/09/2010 14:00:12 LOG0006 SET: 10.20.130.32 TN 108-00-02-10 Registered with CS

104-00-04-29 stays in logout (screen with home button) because this tn is on the other signallingserver.

We have also a lot of error messages on both signallingservers:

06/09/2010 14:04:10 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:04:11 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:04:12 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:04:12 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)
06/09/2010 14:09:06 LOG0003 VTM: ITG3006 Unexpected state encountered: vtmE2Driver.c, 2371, 21 (84)


And sometimes when the user presses the home button, the set
get in undefined state and must be resetet completely.