helpshaniqua
Technical User
Team,
I just completed a installation for an older Nortel Telephony Manager 3.2 system. The install was standard, but we did run into some interesting issues that I wanted to note so that others who encounter the product and have to support it (even though it is discontinued).
1) Virtualization: Don't bother. We could not get the virtualized machine to read the dongle (Keycode).
2) Before configuring remotes site connectivity via modem do the following:
Make sure you use an external modem. TM doesn't support soft modems. You will be able to dial out via hyperterminal but TM will not be able to open the communications profile you create for the site.
Make sure the user can dial out using Hyperterminal before you start.
Make sure you create a dial-up connection in Networking and that it works.
Follow the OS installation manual guidelines - all of them.
When creating a script, you cannot enter a time of 0 but if you leave the wait time entry blank it will insert a zero
When creating a script for the modem, the ^M is used for Enter Key.
It works with a NetPath SEB
If there is an error in the script the Event log will log an error that the communications profile failed to open. You will also see an error that the script failed. If you don't get a script failed error, it is still struggling with the communications profile
Be patient when executing the command. We experienced a significant delay before the commands began to show in the Terminal Logging window.
I just completed a installation for an older Nortel Telephony Manager 3.2 system. The install was standard, but we did run into some interesting issues that I wanted to note so that others who encounter the product and have to support it (even though it is discontinued).
1) Virtualization: Don't bother. We could not get the virtualized machine to read the dongle (Keycode).
2) Before configuring remotes site connectivity via modem do the following:
Make sure you use an external modem. TM doesn't support soft modems. You will be able to dial out via hyperterminal but TM will not be able to open the communications profile you create for the site.
Make sure the user can dial out using Hyperterminal before you start.
Make sure you create a dial-up connection in Networking and that it works.
Follow the OS installation manual guidelines - all of them.
When creating a script, you cannot enter a time of 0 but if you leave the wait time entry blank it will insert a zero
When creating a script for the modem, the ^M is used for Enter Key.
It works with a NetPath SEB
If there is an error in the script the Event log will log an error that the communications profile failed to open. You will also see an error that the script failed. If you don't get a script failed error, it is still struggling with the communications profile
Be patient when executing the command. We experienced a significant delay before the commands began to show in the Terminal Logging window.
