Search results for query: *

Access Cisco Unified Serviceability and go to the Tools menu. Select Control Center - Network Services, then CDR Services; Restart the Cisco CDR Repository Manager.

Someone turned on the AXID field in the Customer Data Block. This puts the terminal number in the CDR record for multiple DN appearances. If there is no multiple appearance, the space is blank.

Would anyone have any information about why, in a multiple line appearance situation, all abandoned calls from any of the line appearances would be assigned to one device in the Cisco CDR? Is that programmable some how or is that just the way it is? Thanks

Do you have BDI set to yes in the customer data block? Don't need to program CTY on the PTY port either.

http://www.isi-info.com/solutions/Keeping_Connected/KCFall05/corpdirupdate.pdf Works with TM too................

It would be based on the number of seat licenses that you have for the Windows 2003 server. Normally they come with five, but you can add more.

If you are on Release 5.0 or higher, you can use the new classes of service...see: http://www.tek-tips.com/viewthread.cfm?qid=1564951

Don't do that....SP 2 is supported.......page 18, TM 3.2 Product Bulletin

There were two new classes of service added with Release 5.0 for CDR. One allows the CDR record to report from Keys other than Key 0. OKCH = Originating ID field of the N record will contain the actual originating DN regardless of Key PKCH = Originating ID field of the N record will contain...

Right, if you do not have TM 4.0 or don't want to upgrade to it, you can always use the TBS import utility. From the TBS main screen, choose the File menu. Then select Import, then click on the down-arrow to choose Corporate Directory Import. Then create a case for importing an Excel csv file...

TM 4.0 will now synch all the extensions on an ACD set over to the Employee database in the TBS module. However, keep in mind that for PBX versions lower than 5.0, all calls made on an ACD set, regardless of Key, will report to the ACD position ID number of the set so having all those other...

Those files reside in the Station Admin folder. Rename the whole folder to Station AdminOld and start fresh. Next time you open Station Admin it will create a new folder with all the files.

I think you need to read the Installation & Commissioning NTP....the part about DEP, on page 122-123, might work then

change the synch status of all the stations to "New". Then remove them from TM. Then make sure to remove the cards in the Hardware View.....Then re-do the downloads........

The Windows Task Scheduler is not running. Go to Administrative Tools - Services. Looks like you did not run the Security Configuration Wizard as outlined in the NTP.

I found that the entries that you want to exclude must all be in the main file that is created by Corp Dir. If even one does not, the exclude thing won't work. Plus, watch the headers in both the main and exclude files. They are not the same. The Exclude file has 6 column headers while the main...

Use the Options tab to exclude the DN values in the original file, then create an "include" file with the DN values you want.

You want OAN = NO so that an N record will get generated on an authorization call that is unanswered so the two can tie together. Otherwise, the trunk/member number of the solo A record will tie together with another unrelated N record down the road when it would use the same trunk/member.

If you have the TM 3.1 Installation CD, the Product Bulletin is included, P-2007-0151 in pdf.

Per the Nortel 3.1 Product Bulletin, Windows Server 2003 can use SP1 or SP2.