Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Re :3300 Mobile hotdesking

Status
Not open for further replies.

mitelgear

Technical User
Oct 23, 2007
46
GB
Ive got a fault on a network whereby hotdesk users from site A can login to sets on site B. But hotdesk users from site B cannot login on sets at site A. I have been through all of the programming on both 3300's following the embedded help file on clustered/nodal hotdesking. The sets display logging in and it just hangs.

Any help would be greatly appreciated
 
In the Cluster Element forms have you got a feaure DN for both Controller A and B entries? Is the details the same on both controllers?

 
yes the feature dn's match up to the both switches. The ip trunks are fine as well. Ccs traces show details when the users login and here are the traces :

user logging in at dublin with a hotdesk user login from london (not working)


17:41:01 VOX DPN PBX1 278 340 D** B** 1E ISRM_I
;10;*7#*58B*CU*1*189*7323#*19*Z#
17:41:01 VOX DPN PBX1 278 340 D** B** 29 SSRM_C
*58*CW*@@@@@@@@@@@@@@#*58*CQ*06#29917323
17:41:01 VIX DPN PBX0 278 340 D** B** 9 CRM/CIM ;14;*244*1#




user in london logging in with hotdesk id from dublin(working)


17:43:29 RIX DPN PBX3 101 213 D** B1029 5 EEM_C *61#
17:43:31 VOX DPN PBX4 316 281 D** B** 1E ISRM_I
;10;*7#*58B*CU*1*189*7712#*19*Z#
17:43:31 VOX DPN PBX4 316 281 D** B** 29 SSRM_C
*58*CW*@@@@@@@@@@@@@@#*58*CQ*06#29947712
17:43:31 VIX DPN PBX0 316 281 D** B** 9 CRM/CIM ;14;*244*1#

the *61# at the end of the first line of the second paragraph, indicates the feature access code for hotdesk login which isnt present in the first paragraph
but im not sure why that is. The 2991 and 2994 are the feature dn'sin the cluster element assignment i hope this info sheds more light on this fault!
 
Is the FAC programmed on the node that's not working? Check the Feature Access code form in System Options

If i remember right you need to have some FAC programmed for it to work (hence you see it in the trace)
 
ive checked the fac and both are the same on the controllers. they were already in. yes they are on the same version of software 7.1 ur something but both software version are exactly the same.
 
What I notice from your CCS trace is that the PBX #'s dont seem to match

The working version shows PBX 3 and 4 talking to each other and the non working shows PBX 1.

Your description seem to indication that you are only testing from 2 sites but 3 are represented in the trace.

I suspect that your ICP #'s and cluster element #'s dont match.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Double check your ICP PBX and cluster programming it will be in this area. Check both pbx and post
 
check both extns are in directory assignment of each controller?. check logs on each controller to see what the error is?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top