How to find what numbers are in use on a Mitel 3300

“Locate Number 6300″




If the number is in use, you will get a result to that effect in the “System Response” window. In this example the number 6300 is already allocated to a system speedcall. If the directory number is free, you will get a “number not in use” message.


“LOCATE ALL FREE DN 6300 to 6399″

This will give you alll available directory numbers between 6300 & 6399.
For the user that wants a specific number, you can tell him : “Well, these are the numbers available in the 6300 range.
Please note that this command will not work for any number that starts in the “8XXX” range. (Last number being 7999…)

How to Reset or Shutdown a Mitel 3300 Controller

Fairly basic thing right? Right! Open a web browser and point it to the IP Address of your Mitel 3300. Depending on the version you are running (because this route has change a few times between the MCD versions you want to find “Maintenance Commands”.

To issue a reboot (otherwise know as a warm reset) enter the following command and press “Submit”

reset system

Now this options does not restart the controller, only the callserver. To reboot the APC you will need to do this via the server manager (not covered in this topic)

To issue a shutdown of the controller, enter the following command and press “Submit”

shutdown

I like to have a raw session on port 2002 open at the same time so I can see what the VM is doing as it shutsdown. The display tells you that you can cycle the power button after 60seconds – I like to leave it a few minutes just to make sure the shutdown has completed fully and cleanly.
Flip your power button/s on the back of the controller off for 10seconds and then flick them back on again. If you have a large estate give the system at least 15mins to come up before you start to panic, all the handsets need to check back in again and this is alot of IP traffic to deal with for a poor 3300 that has just been switched on from cold.

Mitel Maintenance Commands

Locate Feature Extension <number>
with this command you can see de active  features  of a extension and other settings


example: locate feature extension 957

result:

IP Device ID:   72                                                             
Circuit Location : 1 3 1 72 1                                                 
Extension : 957                                                               
Active Features :                                                             
Message Waiting Lamp On                                                       
Dialed Message Waiting.                                                       
Phone Lock: UnLocked                                                           
MAC Address : 08:00:0F:4B:F8:21

SDS Form Sharing

Purpose:

The SDS Form Sharing form manages the data-sharing scope of a given shareable form. For a list of shareable forms on systems that have been migrated to RDN Synchronization, see What Data Can Be Shared?

• Note: To migrate a network with pre-MCD Release 4.1 software to RDN synchronization, refer to Mitel Knowledge Base article 09-3070-00008, "Migrating to RDN Synchronization via SDS," on Mitel Online.  

Use this configuration form before you start sharing the local network element with the members of its data-sharing network or cluster. It allows you to

• define the data-sharing scope of a given form (see the "Share Form With" field described in the table below)
• identify which records to include or exclude during a synchronization (see the  "Share Records" field in the table below).

For example, if you wish to share the Class of Service (COS) form between all members of a cluster, specify "All Cluster Members" in the "Share Form With" field. However, if you also want to restrict COS records 1 through 10 within the scope, define the "Share Records" field as "All Records with Exceptions" to exclude only those records from the synchronization.

For more information:

• About System Data Synchronization
• What Data Can Be Shared?
• System Data Synchronization Programming Overview
• About the SDS Forms
• Specifying the Shared Data
• SDS Start Sharing Data
• SDS Form Comparison

For instructions on how to configure sharable data, see Identifying the Shared Data. Then, to begin sharing the specified data with selected elements, see Sharing Data.

Conditions

• The SDS Form Sharing form can only be modified by a Root Administrator (see Assigning Administrators).
• The data-sharing scope of the 3300 Network Element Properties, Network Elements, Cluster Definition, and Cluster Member forms cannot be changed, because the default scope settings of these forms are required to support SDS.
• If you share the SDS Form Sharing form among elements that have different releases of software,
• systems with 3300 ICP Release 6.1 UR2 and later will display any new sharing criteria that is not supported as "Not supported in this Release".
• systems with software prior to 3300 ICP Release 6.1 UR2 will display any new sharing criteria that is not supported as "Account Code".
• If you share the SDS Form Sharing form from a 3300 ICP Release 7.0 controller to a controller that has an earlier software version (from Release 6.1 UR2 to pre-Release 7.0) any new Release 7.0 fields that are not supported by the older software are displayed as "Not supported in this Release" on the controller with the older software.
• If you share the SDS Form Sharing form from a 3300 ICP Release 7.0 or later controller among controllers that have pre-Release 6.1 UR2 software, restrictions in the Feature Access Codes form may appear incorrectly. If you restrict sharing of the Call Park and Call Park Retrieve fields from the Release 7.0 system, these restrictions are incorrectly displayed as "Account Code" on the controllers with pre- 3300 ICP Release 6.1 UR2 software. If you then save this Account Code restriction from the controller with the pre-Release 6.1 UR2 software, SDS changes the Call Park or Call Park Retrieve restriction to Account Code on the other controllers in the cluster.
• When implementing a new SDS network, enable data-sharing for a limited number of forms in order to prevent data from being overwritten in error. Once the SDS network is operational, enable data-sharing for other forms.

Field Descriptions

Parameter	Description
Form Categories	Lists the forms by category. Note: Dimmed (grayed out) form names denote forms that are always shared. You cannot turn off sharing on these forms.
Share Form With	Identifies the data-sharing scope of the form. Configure a form with one of the following data-sharing scopes: All Network Elements: distributes updates to all network elements that support SDS. All Cluster Members: distribute updates to all 3300 ICP cluster elements. All 3300 ICP: distribute updates only to the MCDs in the network. This encompasses all MCD and MICD elements, including 3300 ICP controllers. Network Group Members: this option is for future use. Admin Group Members: distribute updates to all elements that belong to an administrative group. Use administrative groups to share data among groups of elements within a network group. Resilient Pair: distribute resilient user and device data between a primary and secondary controller. Member Hosts: distribute group information and group member data (for example, cluster pickup groups information and cluster pickup group members) between all the elements on which the group members reside. This sharing scope does not apply to network hunt groups or resilient ACD hunt groups. Hospitality Gateway and Guest Room Host: distribute updates to all 3300 ICP elements in the hospitality cluster. Hospitality Gateway and Suite Host: distribute updates to all 3300 ICP elements in the hospitality cluster. Application Group: distribute updates to all elements that belong to an application group. An application group is a group of elements that have been configured to share licenses with each other on the Application Management Center (AMC). None: do not distribute the form data.
Share Records	Specifies the shared status of individual form records. All Records - All records are shared. All Records with Exceptions - Only select records are shared. Note: When sharing user and device data across resilient pairs, you cannot restrict the sharing of specific records.

Shared Icon

The icon identifies a shared form or record.

• Forms that you have configured as shared are identified in the System Administration forms menu (left-hand browser frame) by the shared icon the next time that you log into the System Administration Tool. Note that the shared icon indicates that the form data is shared; however, you must initiate data sharing from Network Elements form before the data will actually be shared with the designated elements.
• A form that you have configured as shared will also display the icon in the top-left hand corner of the form window. If you place your mouse arrow over the icon, the sharing scope of that form is displayed in a pop-up.
• Shared records within a form are also identified as being shared by the icon. The element must actually be sharing with another element before the icons will be displayed beside the shared records.

If another administrator enables sharing for a record, the system will not change the state of the sharing icon for the record in your instance of the System Administration Tool until you refresh your browser. You can refresh you browser by clicking the Refresh icon.

In the following example, the Admin Group Management, Admin Groups, and Admin Policies forms are identified as forms that contain shared data.  

The following example shows how shared records are identified. In the ARS Route Plans form shown below, Route 5 is not shared. Routes 1 to 4 and Route 6 are shared, so they are marked with a shared icon.

In the Zone Plan frame, Day Zone 1 is not shared. Day Zone 2 and 3 are shared.

SDS applies the shared data icon to devices and groups as follows:

• A hunt group is marked as shared if its pilot DN is resilient. If a hunt group is shared, all of its members are also shared. The same applies to ring groups.

• A pickup group is marked as shared if it is a networked group. If a pickup group is shared, all of its members are also shared, even if the member is otherwise shown as local.
• An ACD group is marked as shared if its Skill Group ID Number is a resilient DN.
• The members of an ACD group are marked as shared if their DN numbers are resilient on the same pair of nodes as the group ID.

• User devices are listed in many forms, such as the Multiline IP Sets form, Single-Line IP Sets form, and the Wireless IP Sets form. In all forms that list user devices, a record is marked as shared if
• the DN for the record is resilient,
• the record is sharing at the device level, and
• the resilient peer for the device has 3300 ICP Release 6.0 or later software.
• The telephone directory form is also marked as shared if it contains resilient devices. A shared icon appears beside each resilient device entry.
• All Call Coverage Services records are shared. Record exceptions are not permitted.

In a shared form, you can display the sharing scope of the form by placing the mouse pointer over the sharing icon in the title bar of the form.

SDS Form Comparison

Purpose:

This form allows you to compare the data from a specified, shareable form on both the local network element and any member of its data-sharing network or cluster. Before starting a synchronization, compare forms to identify discrepancies. You can then choose to synchronize only the forms that contain discrepancies, or to manually correct the individual form records causing the discrepancy.

Use this form when performing the following tasks:

• Comparing Forms
• SDS Form Sharing

Conditions

• You can only compare forms that are shareable. For a list of shareable forms, see What Data Can Be Shared?.
• Before you can compare forms, SDS must be enabled on the elements.
• If the network or cluster supports RDN Synchronization, the SDS Form Comparison form does not list the User Authorization Profiles form for comparison. Instead, the following sub-sections of the User Authorization Profiles form are listed:
• Admin Application Access Policy
• Admin ID to Policy ID map
• Contact Info Type
• Language
• User
• User Application Access
• User Authentication.

Field Descriptions

Form Compare
Parameter	Description
Form to Compare	Select a form entry from the list of local element forms available to be compared.
Network Element	Network elements that have been defined in the Network Elements form appear in the drop down list. Select a network element to compare with.