Search results for query: *

it is possible that your outgoing callerID (DID Servce Number) is not allowed by the carrier. Are you using a MBG in the SIP trunk connection?

In Maintenance use the State command, i.e.State Extension xxxx, etc.

Did you create a COS for the RADs and set the timers correctly? if not then the RAD will fail ad go out of service.

What happens when attempting an outgoing call? Fast busy, etc? What appears on the screen of the pone making the call?

Look for MS Teams Solution Guide and Mitel Assistant User Guide. Also, Mitel Assistant 1.1.1 Configuration and Troubleshooting Guide and Mitel Assistant Release Notes.

Go to Maintenance commands and run the State command on each of those PLIDs. Look for something Out of Service etc.

Here is a list of supported hones from a MiVB release 10.1 system.

Login and celect trunks. Then select Analog trunks>Trunk Assignment to see if you have analog trunks. Do the same for E&M Trunks.

It appears that you have PRI and SIP trunks. Are there any other type of trunks connected to the controller - E&M or LS/GS?

can you issue the SIP LINK STATE ALL command in maintenance to see wha SIP link is down?

What type of trunks does your system have connected - PRI, SIP. Analog LS/GS. E&M?

Create a notification fr each building/property. Then add the security person(s) to that notification.

Is it possible the phone is in SIP mode, not Minet mode?

Maintenance and Diagnostics>IP Telephone Inventory>All IP Telephones will list the device type

When you connect with Putty use admin as the username, not root. This will bring up the admin menu. Select 2 to configure the server.

Using Putty login to the MSL interface as admin. From there you can configure the server NIC settings in step 2 - Configure this server.

The MXe III-L does require release 9.1 or higher. Fro the Help file: MiVoice Business Release 9.1 New Hardware and Tools A new controller, MXe III-L (where L stands for LAN), is added to the family of 3300 ICP controllers. The MXe III-L controller is a functional replacement for the MXe III...

No issues with MiVB 10.0 in any installs/upgrades here.

Check the COS for the paging trunks. SMDR Internal and External should be set to Yes.

Try using LOGSYS READ SMDR ALL MATCH T(and the paging trunk number - i.e. T01).