Remember, the telephone data in the database used by Telephony Manager is a copy of that on the Meridian switch.
Keep the TM data up to date by scheduling a regular job (overnight?) to refresh it.
Changes made in TM need to be manually transferred to the switch before they take effect on the phones.
Starting the TM software
This has to be done on the TM server itself, connecting through mstsc will not do. Use ILO. Just signing onto Telephony Manager Navigator will do it.
To connect to the Meridian Switch
- Connect to the TM server. MSTSC will do.
- Start Telephony Manager Navigator, if it is not already started.
- Expand Sites, Telereal and 140 London Wall
- Right click on System Window and select OPEN
- The System Terminal is one of the icons in the tool bar
Or physically attach a laptop to the switch via the cables under the cabinet and use software like Teraterm
To connect to Telephony Manager (TM)
URL http://{tm server name}/Login/Eng/default.asp
To connect to Call Pilot (Voice Mail)
URL http://{cp server name}/cpmgr/login.asp"
- Enter mailbox number
- Password:
- Server: as in URL (this will be remembered)
- Location: blank
To refresh TM database from the Meridian Switch
- In TM, do a basic telephone search of some sort
- In ‘
’, select ‘Retrieve; - Select ‘Retrieve All’
- In ‘Task Details’, enter the schedule required.
- Click, ‘Submit’
To send changes to the Meridian switch
- Make the change required.
- Search where ‘Sync Status’ is ‘Changed’, ‘New’ or ‘Deleted’, depending upon the type of change made.
- Select all the changes to be transferred and click Transmit
- Enter something for the task name and click Submit then Close
- This will start a Windows task on the TM server to do the transfer
- The log file can be found through Telephones - Sync Logs
To enable a telephone
- Signon to TM
- System Navigator
- Expand site, then system (Telereal and 140 London Wall)
- Expand System Applications
- Double click ‘Web Maintenance Pages’
- Select ‘Find PE Units (PBX) and click Go
- Enter the telephone number in the DN box and hit enter
- Select the DN to be enabled.
Or
- Find the DN through normal Telephone Search
- Click ‘Troubleshoot Problems’
Either way
- Select ‘Enable’ from the command drop down list and click ‘Go’
- Close the two Maintenance Page windows
Or through TTY
- LOGI
- LD 11
- REQ CHG
- TYPE 3904
- TN
- ECHG YES
- ITEM
- REQ END
Global Speed Call List – List manager on TM server
Group Hunt Lists – List manager on TM server
Add a telephone
- Signon to TM
- Telephones – Add
- Select Template Type – M3904 for main digital phones.
- Click Add
- Search for Terminal Number, without entering any criteria
- Once a list has been returned, select unused from ‘Show’ drop down list. Select one and click assign
- Search for Employees. Choose the correct one and click Assign
- For Key No. 0, search for DN, in the same way as the search for Terminal Number. Select one and click Assign
- Select Multiple Appearance Redirection Prime(MARP)
- Click Copy Name From Directory. Ensure Display Format is Last, First
- Go to the top or bottom of the form and Click Finish
- Transmit the change
Change a telephone
- Signon to TM
- Telephones – Search
- Search for Prime DN of telephone number
- Select the correct phone
- Make the changes required, for example, change the employee assigned to the phone
- Go to the top or bottom of the form and Click Finish
- Transmit the change
Change Call Pilot password
- Signon to Call Pilot
- Click Change Password
- Enter Mailbox Number
- Click Save. You will be taken to the main menu
- The password will be set to 12
Directory synchronisation
The system uses the Nortel Common Network Directory (CND) to find employee details, which in turn gets its data from the Telereal Active Directory. There are two stages in the synchronisation.
AD / CND Synchronisation
- On the Telephony Manager server, TLONAPPS030, login to CND.
- Go to Tools -> LDAP subscriber synchronisation
- Create a new job or open an existing one
- In the left hand panel, enter the details required to connect to the LDAP server
- In the right hand panel choose the column mapping options
- Click Save, Close and Close
- Schedule the job through Windows scheduler. The task to run is
javaw -jar runSyncJob.jar -jobName "LDAP synchronisation"
on the setting tab, set the job to end after running for 5 minutes. There is a dialog box presented at the end of the job that needs some input and would otherwise remain open for ever. - From the LDAP subscriber synchronisation screen, the summary log can be viewed via View -> Summary Log. The detail logs for each synchronisation are listed in there.
CND / TM Synchronisation
- On the Telephony Manager server, login to TM.
- Under Utilities -> Common Network Directory find Server Setup. These values are probably OK from installation.
- Under Utilities -> Common Network Directory find Synchronisation. Select the site to be synchronised and click Set Schedule. The job appears in the TM Scheduler.
International Dialling
This is controlled by the phone feature, Network Class Of Service (NCOS). There are 7 or 8 classes that control what numbers can be dialled from phones in that class. The default is 5 which is OK for most people, but denies international dialling. Giving a phone class 6 will allow this.
There is no interface in the TM web application to view NCOS settings and they can’t be amended. Viewing has to be done though TTY, either in TM on the server or Virtual System Terminal in System Navigator on the Web
Log into TTY, load overlay 49 and request the Flexible Code Restrictions table
- LOGI
- LD 49
- REQ PRT
- TYPE FCR
- CUST 0
- CRNO 0 (or Carriage return for all trees)
- LOGI
Meridian Switch Default Gateway
The network configuration for the Meridian switch needs to be set through the System Terminal, probably when physically attached to the server. It is done through overlay 117.
- ld 117
- prt route
- new route 0.0.0.0 172.24.11.14
- stat route
- enl route
- ping
- ****
Feature Codes
These allow or deny features on a TN and therefore a DN.
DDGA Allow the calling DN to be displayed on the called handset. Also withholds the number for external calls.
NAMA Works the same as DDGA, except for the name rather than DN. No effect for external calls.
CFXA Allows calls to be forwarded to an external number
CNDA Allows the other call party’s name to be displayed.
NCOS See International dialling above
Corporate Directory
Calls can be made to names, rather than numbers. This relies on the Corporate Directory being up to date. An update job can be scheduled in Telephony Manager Navigator. This works by generating a report and then uploading it to the TM server.
- Under Utilities, select Corporate Directory
- Right click the M1 Corporate Directory report
- Select Generate Report and Schedule
- Select Generate report only, click schedule to define a schedule. Click OK
- Double click the M1 Corporate Directory report
- The General, Data Fields, Output, Options and Get Files tabs are all configured
- On the Upload tab, ensure the Disable automatic upload and schedule upload time option is unchecked. This will load the data onto the TM server whenever the report is re-generated.
- A CD Daily update job can be seen in the Scheduler
To use Corporate Directory on a handset, press the button with a terminal on it and then select Corporate Directory.
Flexible Feature Codes
Are not feature codes. They are codes that can be entered on a handset to invoke a feature. For example #1 is generally set to set and unset CFWA – Call Forward All Calls. The current setting can be found using Overlay 57, with a Type of FFC and Code of All. All can be set or changed also using Overlay 57.
Printing TN details
All the details of a TN can be printed through TTY, Overlay 20. The output can be captured to a file by clicking File -> Capture.
User Group Access
User Groups are created on the Telephony Manager server. On the main navigator window, choose User Groups from the Security menu. To allow a User Group to access a feature in a Web Browser, they need access to that feature under the Navigator -> Web branch and then also access to the relevant system under the Sites branch. Web Station Admin. seems enough.
Read Only access seems to not be enough for anything.
Monitoring Outside lines
- Log into TM and load overlay 80
- To list each of the routes and their status
TRAC 0 1610 0 customer number, 1610 access code
- To get details of a particular route
TRAD n r n some number, 1 in our case, r route number
The extension DN and TN are shown, either as ORIG for outgoing calls, or TERM for incoming. For outgoing, the dialled number is shown in the DIAL DN. For incoming calls, the dialling number is not shown
