Panchanka

Hmmm, Rick, I was looking for the same info as you. Does nobody have it yet? I have ordered the software and plan to have it done within the next month. I will let you know how it goes.

aswipay

Follow the conversion procedure to the letter. Make sure that you understand LDAP. Make sure that you under stand the ramifications of the synchronization utilities. For certain you cannot rely on the documentation as a guide. Nortel has failed miserably in documenting this product. With that being said I will give you a short story of my migration experience.
First make sure that you have a good copy of your Corporate directory in CSV. Then make sure you run an OTM report that includes all station, location data etc. These will come in handy when repopulating TM 3.0.
ONE THING TO BE SURE OF. DO NOT LAUNCH TM 3.0 AFTER THE UPGRADE FROM 2.2 TO 3.0 AS A CONVERSION UTILITY WILL RUN! LAUNCHING THE WINDOWS ADMIN WILL SCREW UP THE CONVERSION! That being said I will relax.

If you are using TBS you will notice that all of you organization hierarchy is still in tact but there are no employees. You have to syncronize your station data with TBS then put all of your employees into the proper departments. Also make sure that if you use web TBS that you have a profile in the employee directory that allows for full web reporting or the site will not show up in the web browser.
If you are synchronizing the CND with an external Active Directory I have found it is best to populate the CND then synch the station data by matching the usernames. This parses your CPND data in the correct CND entry. As always GIGO (garbage in garbage out). If the information in your companies directory is not reliable you do not have to use the external synch. Just sych the station data with CND. I am still cutting my teeth on this product as of this writing and by no means am I an expert. How I yearn for the pink beauty of an ATT 620A panel at this moment. Oh well, you can find sympathy between shXt and syphillis in the dictionary. If you have any more questions PM me and I will help if I can.

JEHartmann

Hi

I have just got an upgrade fra 2.2 to 3.0
No problems used about 1 hour.

The niciest thing for mee is that i now can use other PC's to work on the TM I dont have to go to the PABC room.

Regrds

Jan

rixride

dag, I just noticed that...

__________________
-=Welcome to PBXInfo=-
-FREE HOW TO NORTEL& MORE Video's
-Add yourself to Pbxinfo's Frappr
-Find Nortel Software

telecomatt

Hey guys.. I dont understand.. Nortel had things working well with OTM 2.2 why do they have to go and ruin it with TM 3.0

Some issues you will come across (these are known Nortel issues BTW)

1) If you have any m3000, or m2317 sets (not common but do still exist)
If you do a retrieve all. They will show up in station admin. however you cannot view, out, new or modify them in ANY way.. only way to get rid of them is to out your site and re-retrieve

2) Adding a phone to a new previously unprogrammed TN

If you go to add ANY kind of set to a new card in the system.. TM will hang up during transmit on the CDEN prompt.. it things it the DES and tries that. and of course.. fails.. one work around that i have found. change the DES field on your sets to the proper CDEN (4d, 8d) whichever and it will work

aswipay

I could not agree more. 2.2 had some limitations but was far and away better than this POS. I think that Nortel has lost track of the purpose of the product.
For example: Why is it better to have to run separate "synchronization" tasks (CND and TBS) every time you add a telephone? The purpose pf the original OTM was to provide an easy, single point of admin and billing. The documentation makes the assumption that the end user is some sort of uber database admin. If I had even mediocre database admin skills why would I need this product? Nortel seems to have the attitude of "We make it so it has to be good". This product is a train wreck. We are actively seeking replacements for TM and TBS. What a shame after using OTM for 5 years. End of rant.

Panchanka

Aswipay,
I also found TM 3.0 worst than 2.2. OTM 2.2 was a solid software that is why I have reverted back to OTM 2.2. However, it you only have TM never using OTM, you won't find it that bad. (you don't know what you have until it is gone)

The way I heard it is that Cisco and every other IP Telephony entrepreneur has a fully Web-based management system, and by not having one, Nortel looks like they are not up to speed. So unfortunately, they came out with TM 3.0 which lacks much of the functionality that made OTM a good tool to use. With more release of TM, I am sure the product will improve, however until that time, I am holding off upgrading.

(BTW when I upgraded to TM3.0 ****** support was not a great help. I don't think they were trained, it is learn as you go with them). Helpful hint: If/when you upgrade, make sure your sever is off the domain.

aswipay

****** is a joke anyway. I had a "support contract" with them about 5 years ago. The people there could not even support the TBS module. I have been looking at MerAssist with RSI call accounting but it might be a hard sell with the management. Panchanka, how did you go about regressin to 2.2?

boylerman

TM3.0 is a POS! I was lucky and received a free TM 3.0. I have at least 6 cases at design. I would not recomend this to any customer.