What to do if MiCollab Conference System by Mitel can call 933 but the location is not sent?
If MiCollab can call 933 but the location isn't sent, it might be because 933 is not configured in the MiCollab user configuration-Location service. Ensure that the MiCollab client emergency location is configured and that the Mitel Network helper is running.
What to do if emergency calls on Mitel Conference System do not trigger E911 local notification?
E911 local notification will not be activated if an emergency hunt group is not fully programmed and a call is placed on a designated “emergency” route. Refer to Mitel Knowledge Base article 04-1000-00020 for programming instructions.
What to do if MiCollab Conference System by Mitel cannot dial 933?
If MiCollab cannot dial 933, the Redsky API may not be configured correctly. Test the connection from MiCollab.
General| Type | IP PBX |
|---|---|
| VoIP support | Yes |
| Conference Capability | Yes |
| Model | MiVoice Business |
| Protocols | SIP, H.323, MGCP |
| Codecs Supported | G.711, G.729, G.722 |
| Deployment | On-premise |
| Integration | CRM, Unified Messaging, Collaboration Applications |
| Operating Temperature | 32°F to 104°F (0°C to 40°C) |
| Humidity | 10% to 90% non-condensing |
| Dimensions | Varies by model |
| Weight | Varies by model |
Flowchart and steps to troubleshoot technical issues with the system.
Steps and required information before contacting Mitel Technical Support for product issues.
Procedures for returning faulty Field Replaceable Units (FRUs) with required information.
Troubleshooting steps for licensing and option selection errors in the system.
Troubleshooting common hardware alarms such as ICP Comms, E2T card, DSP status, and Fan.
Troubleshooting common issues with MXe III/MXe III-L controllers, including E2T and RTC.
Troubleshooting general phone issues like no calls received, unable to make calls, or calls being cut off.
Troubleshooting system failures, log collection, and system diagnostics for software issues.
Procedure to resolve error code 22 during manual ICP3300 controller software installation.
Steps to recover the system when the MiVoice Business software fails to boot.
Troubleshooting common issues related to system database backups and restores, including FTP file transfer.
Troubleshooting for features A through B, including Add Held and Alpha Tagging.
Troubleshooting for features D through G, focusing on DID Service and its associated issues.
Troubleshooting for features L through O, covering Loudspeaker Paging and Message Waiting Indication.
Troubleshooting for features S through V, addressing Telephone Directory and Transfer functionality.
Troubleshooting common issues with analog trunks, including call reception and quality.
Troubleshooting common digital trunk issues like excessive bit errors, slips, and call reception.
Troubleshooting issues related to IP trunks, including router crashes and cluster connectivity.
Troubleshooting common issues with SIP trunks, particularly related to SMDR records.
Resolving issues with logging into and using the System Administration Tool, including browser compatibility.
Troubleshooting E911 local notification failures and PSAP accurate information delivery.
Troubleshooting issues with embedded voice mail, including startup failures and notification problems.
Troubleshooting bandwidth statistics and reporting issues related to CAC rejections.
Overview of resiliency concepts and troubleshooting for IP device and trunk resiliency.
Diagnosing issues where resilient devices do not function or fail over correctly after primary ICP failure.
Troubleshooting PC network connectivity issues related to IP phones and physical network problems.
Understanding and using Layer 2 Ethernet traffic counters for debugging LAN problems.
Using MSP Log Viewer to view, filter, and manage system logs for troubleshooting.
Diagnosing CPU slowdowns and overloads using shell commands and resource history files.
Diagnosing phone problems like no dial tone, busy status, and incorrect network parameters.
Understanding the IP phone boot sequence and common error displays during the process.
Interpreting T1/E1 Combo MMC indicators and alarms for primary and secondary controller status.
To Next Page
