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!

UCA 4.0 - User Accounts and PRG problem

Status
Not open for further replies.

vlevalois

IS-IT--Management
Jun 30, 2009
181
US
In UCA 4.0 server config (on MCD 4.2), the user accounts now show if they have a PRG associated with the lead ext number and it places a "PRG" yes/no in a column where the accounts are listed.

Problem is, I have a user that indeed has a PRG with his cell phone as a member (as well as his default extension, same # as the PRG) yet when I create the user in the UC server it does not show him as having a PRG. Others I've created do show correctly yet this one user does not...

What gives??

Thanks!
 
Any differences in the COS?

The single biggest problem with communications is the illusion that it has taken place.
 
The UCA has to synchronoize the EHDU's from the PBX to know about them, there is an option on the PBX sync page to sync dynamic extensions only, then once it has successfully sync'ed it should show up under the account as an EHDU, it must be configured 10 digits as well.
 
Indeed, and have tried that several times, but I have a feeling it's not sync'ing even though it's showing success. I've tried a full sync and it's not bringing in more entries to the users that I had deleted before. I think there may be something wrong with that specifically but with it showing success I'm not sure where too look from here...
 
was gonna suggest the sync too but it seems there is something a miss.

let us know how you get on. I've been busy with a UCA configuration too and must say not impressed as it seems temparemental.
 
OK, problem resolved.

Turns out that the alphanumneric of the PRG cannot be identical to another DN in the system and in the same department. This user also had a home TW extension with the same name that was higher than his office DN, so the UC server takes the HIGHER number and tries to associate it to the user account.

Changing the other extension to a dif department or giving it a dif name resolved the issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top