Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Handset volume

« on: August 04, 2016, 03:47:09 PM »

Increase volume to highest, then step back one.
It will not save the highest possible volume.

2

Mitel MiVoice Business/MCD/3300 / Re: transport or codec mismatch

« on: July 13, 2016, 10:13:44 AM »

The codec is negotiated during the call setup over SIP. the MCD works on that principle and does support G.729 as it does G.711 and both A or U (mu) law.

To run packet capture in a newer releases lookup maintenance command SIP Tcpdump On/Off in the built in help system.

3

Mitel MiVoice Business/MCD/3300 / Re: RESILIENCY and SDS errors

« on: July 13, 2016, 10:09:22 AM »

Call forward and other resiliency features are shared on the Resilient pair level.
This simply means that no other system needs updating than the secondary controller.
- we assume that the resiliency is working and no fault in configuration
The only question is the forward destination: Is it a valid call forward destination in the secondary system?
- my favorite command: Locate Number <DN>

Note:
- if the SDS errors (for this specific scenario) refer to anything else than the secondary controller, then the question is totally different
- if the COS for example is not shared and no forward allowed on the secondary system, or the destination is not valid because of the COS configuration of that DN, then that has to be corrected

PS: understand that you are more familiar with SDS than most others, but they might read these post as well.

4

Mitel MiVoice Business/MCD/3300 / Re: Employee phone change

« on: July 06, 2016, 08:41:56 AM »

Answer to the invalid service level error:
Not allowed.
You can go higher in service levels but not downgrade.
- i.e.: Ip Device only -> Multidevice -> Full

Under the new User and Services form:
- locate the user by last name
- change the directory number of the old service to free it up
- add the new service with the right number
- make that the primary phone service
- disassociate the old device and do whatever you would like with it
This is not so simple if you have MiCollab with SDS enabled, because it is recommended to do this in MiCollab.

Dialing issue with MiCollab client.
- back to basics, dial another extension number
- COS: Trunks- Public Network Access via DPNSS

5

Mitel MiVoice Business/MCD/3300 / Re: RESILIENCY and SDS errors

« on: July 06, 2016, 08:28:13 AM »

Welcome to the world of data sharing networks.
Just to avoid simple causes, please verify that your cluster elements are programmed with the necessary Feature DNs.
- also verify that the Feature access codes are programmed and shared
After that it is a simple chase of logic.
Note where the phone is programmed and resilient to.
Note the destination of the call forward.
The SDS error specifies the system that can not update to that data, so go into that system and start at the maintenance command 'Locate number DN'
- does it exist, can it be a forward destination, why would this system has to know about that call forward to begin with
Always remember the 'SDS form sharing' form that defines what is shared and how.
- for resiliency it is always (almost) the resilient pair

In later releases SDS errors are retried automatically, still suggest checking the top box and Retry.
- once you solved the cause of the errors they will resolve and update

6

Mitel MiVoice Business/MCD/3300 / Re: ARS digits dialed sharing

« on: June 28, 2016, 02:12:22 PM »

Sorry, I missed the point. Was concentrating on ARS, but your question is about SDS.

You can share the ARS digits dialed form, but be very careful with the route assignments.
The real answer to your question is in the SDS Form sharing exception list.
- exclude the CeID digit strings from the sharing scope
The rest of the digit strings like outside access will be shared and work just fine.
- one dangerous aspect of this is during troubleshooting, you change the destination route in one system and if lucky it will not update the other ones, just generate SDS errors

7

MiVoice Office 250/Mitel 5000 / Re: Hot Desk Voicemail Issue when Logged out

« on: June 28, 2016, 01:51:35 PM »

Missing something from the story.

First make sure there is no mistake of the HD User state and features
Maintenance command:
- state extension <DN>, should be out of service when logged off
- locate features extension <DN>, shell be no active forward features if using reroute
Either call forwarding or rerouting must have the Busy option in it, since the HD user is considered busy when out of service.
- use reroute first alternative reroute Busy/No Answer options or setup Call Forward on Busy

8

Mitel MiVoice Business/MCD/3300 / Re: How to hand out DHCP Leases to Mitel Devices Only

« on: June 28, 2016, 01:35:15 PM »

Not to be blunt, but argumentative.

Consider the scenario of wireless access points handling Spectralink phones that do not support security settings in the AP.
- any iPhone user walking by the building would get an IP address if there phone is allowed to access 'unknown networks'
- now that they have an IP address they know that there is a network and they can try to access it
- another problem is that you just ran out of IP addresses of your scope and none of the 'new' Spectralink phones want to work
The suggested configuration can prevent these problems.

9

Mitel MiVoice Business/MCD/3300 / Re: ARS digits dialed sharing

« on: June 28, 2016, 01:27:15 PM »

Not sure if I understand your question correctly, no criticism intended.

There is only one ARS entry per system is necessary, that is for the CeID Digits of the destination systems.
- in some sense you are correct, the software could generate that entry, but the routing medium (either IP/XNET or Direct IP) must be assigned in a route first, and that is your choice

The simplest example, assuming that your systems are in an SDS cluster and sharing is established and working.
The RDN form includes the remote numbers and their hosting system.

As part of the cluster configuration you must complete the ICP/PBX Networking form under Trunks - IP/XNET.
- ensure the 'Local" system assignment is correct (Yes)
- the second tab, IP Networking must have the correct IP addresses (also used/required for resiliency)
- the third tab, unless you are really setting up ISDN must be blank
Completion of the rest of the IP/XNET forms is required for systems with no Direct IP route option.
- older software loads
IP/XNET can also be used for inter-cluster call routing for sharing PSTN trunks.

To reach those RDN numbers program a route using Direct IP with the PBX number of the destination system.
- in complex scenarios it might won't be a direct route to the destination system. it could be an intermediary that will reach the final destination interpreting the call by it's own ARS
Assign the destination system's CeID number in ARS digits dialed and point it to the route above.
- the number of digits to follow can be fixed and can act as a safety barrier or set to Unknown
- !! Do not set to anything else !! - the system will wait for the specified exact number of digits

Done! Dial the remote extensions in the destination system.

10

Mitel MiVoice Business/MCD/3300 / Re: ARS digits dialed sharing

« on: June 24, 2016, 01:41:26 PM »

Too many fields.
Cluster definition form:
- PBX number is just a PBX number and you can not use the same twice in a cluster
not to be confused with
- Cluster Element ID Digits: this is a dial number to reach the specific system, not to conflict with any other dial number such as ARS or extension numbers, Feature access codes . . .
- Feature DN: used to access features on specific controller by background processes, some features will not work without this, and is shall not conflict with other Dial numbers, similar to other FAC

When you assign the CeID Digits a warning will pop for ARS configuration you must do.
- program either IP Trunks in the IP/XNET section or in newer release just use Direct IP route medium
Direct IP makes routing based on the RDN (Remote Directory Number) list.
- looks up the number and the system it belongs to, then searches the CeID digits of that system in ARS and sends the call to the PBX specified in the route (not necessarily the same one)

If you want to create a loop-back pick another than the local CeID number for ARS, whatever you want to loop, and send it to a route pointing to the local system.
- blocking the local CeID digits in ARS digits dialed is intentional: it would create a dialing loop and bring down the system

PS: The local loop is used in advanced emergency call handling, review documentation for more details.

11

Mitel MiVoice Business/MCD/3300 / Re: How to hand out DHCP Leases to Mitel Devices Only

« on: June 24, 2016, 11:54:55 AM »

This is a very old thread but it is still valid, and would like to make it clear that the previous post is incorrect.
You do not have to change this option when adding new phones.
The option Client Class ID must match is valid since all Mitel IP phones use the same Class ID string 'ipphone.mitel.com'.

The real drawback is connecting to the system with your computer on that VLAN, since that is not a Mitel device it will not get an IP address.
Suggest implementing this feature for security and performance if you have wireless devices on the voice VLAN.
- by adding static reservations to your wireless devices in combination with this option you can lock down your DHCP server

12

Mitel MiVoice Business/MCD/3300 / Re: Caller ID for incoming calls showing Trunk Label

« on: April 11, 2014, 10:47:47 PM »

The trunk label is displayed if caller ID is not available.
Sarond is right, check with the system or call your provider.

13

Mitel SX200, SX2000, and older SX platforms / Re: Mitel SX200 EL system evaluation

« on: April 11, 2014, 10:42:11 PM »

Check the device forms, one is nine the other I can;t remember, but you will see it in the menu.
Make sure you have nothing programmed in that slot.
When you want to delete an extension you will forced to delete all related programming first (system will prompt for it.
Now go to form one and delete the card in that slot.

The display should clear.

14

Mitel SX200, SX2000, and older SX platforms / Re: IP phones lose voice path every 2 days

« on: April 11, 2014, 10:33:45 PM »

DSP is the only thing makes sense!
The busy signal is an indication that there is no resource to process a call.
Most likely it has a flow that locks them up one after another, till finally there is nothing left.

15

Mitel SX200, SX2000, and older SX platforms / Re: Replace a CX controller with a CXi

« on: April 11, 2014, 10:27:37 PM »

It isn't all that simple.
If you backup the database and restore it into a different system, the hardware that is not there in the new one but was there in the old one get restored, but can not be changed, because it is not there, or different.
Had issues with dual vs single framer and embedded analog boards this way.
You better off deprogramming those units before the backup!