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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

advice on directory synchronisation

Status
Not open for further replies.

doubledrat

IS-IT--Management
Apr 30, 2010
6
GB
Starting a new thread because I now think schedmac may not be what I need.

We have a SQL database that holds all our staff info including their phone numbers. We want to be able to make sure our mitel system is in synch with this dataset. I don't want to make changes to phones with this, just the people associated with them.

from the little detailed information I can find, I think this is what I need to do and would appreciate some informed commentary!

Run a scheduled export of the phone directory

Determine the differences between that and our corporate directory then

Use mitel "telephone directory import" to add new people to phone extensions. If any deletion of a person means there would be nobody associated with it, also add "spare" to that extension before

Using mitel "schedMAC" to perform deletes of people with DELETE,sname,fname,extension

Then use mitel "schedMAC" to perform changes such as turning on/off voicemail


does this sound line the right approach?
are there any gotchas I might encounter? e.g. can I go straight from a directory import to a schedmac for deletes or do I have to synchronise the controllers between steps?

is this sort of thing properly documented anywhere?

 
Not an expert in SQL but would not setting up LDAP sync from Opsman to your SQL server be the way to go?
 
Ditto LDAP.

But OPS needs to be licensed for it.

BTW, Are you aware that OPS is no longer supported at the latest release to do set changes? Don't waste too much time developing a solution that you can't use in the near future.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
LDAP supposed to be directly in release 5 of the 3300 so if doubledrat focuses in that direction it might be helpful. Would have to skip MCD 4.1 as it will not.
 
thanks for the pointers. Unfortunately, LDAP is such a poor sync method when you have most people with multiple phones that you end up programmatically simulating your database in the LDAP directory by creating dummy users. that then becomes a nightmare in itself to keep relevant. :-(
 
This is a off topic but...
kwbMitel (TechnicalUser)
30 Apr 10 19:12
Ditto LDAP.

But OPS needs to be licensed for it.

BTW, Are you aware that OPS is no longer supported at the latest release to do set changes? Don't waste too much time developing a solution that you can't use in the near future.

Do you have any further info or an announcement on that ?
 
NLConz.

The 4.1 certification Course is very clear.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
could you elaborate on OPS no longer supported to do "set changes" not being supported? do you mean schedmac in it's entirety or just certain functions?
 
Anything that modifies set programming is out.

What remains is virtually useless.

Set time - No longer required - Built in
Set Night mode - No longer required - Built in
Scheduled Backups - Only real useful item left.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
so how do they expect people to automatically update? Using the awful active directory "integration"?
 
Realistically, I've always managed my systems manually. Good Record keeping pays off over time.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top