Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Mitel Reboot issue

« on: July 16, 2012, 02:18:50 PM »

The version of the Mitel Communications Director is: 4.1 SP1.

I have 4 other devices plugged into the backup battery that were not affected at the same time the Mitel controller rebooted. 

Maybe upgrade to another version?

2

Mitel MiVoice Business/MCD/3300 / Re: Mitel Reboot issue

« on: July 13, 2012, 10:22:00 PM »

The 5 controllers are clustered and are at separate facilities.  Originally I thought all went down, but only three of the five went down.  Still odd.  They are not on the same UPS.  We have been experiencing echo at all of our facilities lately, and our Mitel vendor was looking into it today.  It may have been a coincidence that they were looking into the echo issue and the controller restarts.  We experienced a power glitch on Thursday at three of our facilities, but the controller locations don't match up with the restart today.  All facilities lost their phones, but one of the facilities was where one of our PRI's exists.

bobcheese, yes, I agree with you.  I should have looked at that line to see "UNKNOWN".

3

Mitel MiVoice Business/MCD/3300 / Mitel Reboot issue

« on: July 13, 2012, 04:37:14 PM »

All of my controllers rebooted at the same time this morning and I'm not sure why.  I was wondering if someone could help me with some of this log information.

Also, what is this "slowpoke was not set to run"?



Here are some of the log messages from one of the controllers:


EntryBlock - Enable Block State VM Not Ready with Mask 0x10
TerminateService: for client 2, disconnected. Mitai server not ready
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
TerminateService: for client 2, disconnected. Mitai server not ready
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
The link from MCECAAA MN3300 Controller at location 01 1 01 Active         to   MC266AA Communication Proc at location 01 1 10 Activeis now OPEN.
MC266AA Communication Proc at location 01 1 10 installed
TerminateService: for client 2, disconnected. Mitai server not ready
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
EntryBlock - Disable Block State Resume Restore in progress with Mask 0x8
EntryBlock - Enable Block State Resume Restore in progress with Mask 0x8
EntryBlock - Disable Block State Resume Restore in progress with Mask 0x8
EntryBlock - Enable Block State Resume Restore in progress with Mask 0x8
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
TerminateService: for client 0, disconnected. Mitai server not ready
Mitai Server is not ready to process OpenPBX : server state = MITAI_SERVER_WAITING
MiTAI Server socket-listener started successfully
INFO: SSO Enabled.
INFO: SSO About to startup.
slowpoke was not set to run
Local date/time reset to 2012-JUL-13 11:44:39.00    FRI by ESM User.
The link from MCECAAx MN3300 Controller at location 01 1 01 Active         to   MC270Ax Universal T1 at location 03 1 02  is now in SCANNING mode.
The link from MCECAAx MN3300 Controller at location 01 1 01 Active         to   MC266Ax Communication Proc at location 01 1 13  is now in SCANNING mode.
The link from MCECAAx MN3300 Controller at location 01 1 01 Active         to   MCSTHAx ICP Communications at location 01 1 11  is now in SCANNING mode.
The link from MCECAAx MN3300 Controller at location 01 1 01 Active         to   MC266Ax Communication Proc at location 01 1 10  is now in SCANNING mode.
Restart information from hardware status register was  power up
LOGSYSRTR is ready to route entries Log name: maintenance
Local date/time reset to 2012-JUL-13 11:44:38.00    FRI by ESM User.
LOGSYSRTR is ready to route entries Log name: xxxxxx
LOGSYSRTR is ready to route entries Log name: xxxxxx
GPAGEMGR: Initializing data structures                                                                                                                                                                                                               
DBMS Status flag set.  DB Download Complete..
DBASRV created: PID = ($0005,$0034)
DBASRV created: PID = ($0004,$0033)
DBASRV created: PID = ($0003,$0032)
DBASRV created: PID = ($0002,$0031)
DBASRV created: PID = ($0001,$0030)
DBASRV created: PID = ($0008,$002F)
DBASRV created: PID = ($0007,$002E)
DBASRV created: PID = ($0006,$002D)
nvs_BerkConvert: Recovering existing IP Networking database.
NotifyTimeChangeTime Change Could not be Notified
memory audit started succesfully
Progress Monitor->ResourceAlarmStartupResourceAlarmStartup ready
Progress Monitor->ProcessorCoordinator::ProcessorCoordinatorProcessor Coordinator source Logs initialized.
Progress Monitor->SysServices::appStartupPart2 (10.10.60.120)Boot Device: ata=0Host Name: Target Name: Target IP address: 10.10.60.120:ffffff00Host IP address: 10.10.60.1Gateway IP address: 10.10.60.1Boot File: /partition4/RTC8260Boot Flag: 0x0
Unexpected Result->SysServices::appStartupPart2 (10.10.60.120)Abnormal reset, cause: (0x0) UNKNOWN
Progress Monitor->SysServices::appStartupPart2CXII Platform (10.10.60.120) Booting Software version: 10.1.1.11_2System Relink: No relink has been applied.Call Control Relink: No relink has been applied.Abnormal reset, cause: (0x0) UNKNOWN
JavaLayerLifecycleListener::handleNotification()->Received Startup notification for JavaLayer.
JavaLayer_PPC_StartUp->JavaLayer startup has been initiated.
InitSystemTimeZone()->Current Timezone is  US/Central
Progress Monitor - SubscribeNewLogSubscribed to * for Error
Progress Monitor - SubscribeNewLogSubscribed to * for Warning

---------------+--------+-------+-------+-------+---------+---------+---------- ICP Comms Card |     5  |     1 |  20 % | Minor |   > 0 % |    25 % |   100 % | ---------------+--------+-------+-------+-------+---------+---------+----------
---------------+--------+-------+-------+-------+---------+---------+----------                |Total In|      Unavailable      | Alarm Threshold Percentages    Category    | System | Total |    %  | Alarm |  MINOR  |  MAJOR  | CRITICAL
                                ------------ Current System Alarm :          |  MINOR   |       viewed from Active                                 ------------
IP Trunk link to icp 004 Building1 failed and link dropped.
IP trunk to 10.10.64.120:1067 has failed.
ICP has lost contact with (10.10.64.120:1067), network driver cluster pool free: 2965 and low water mark: 2853
TRAFORM: Traffic report for period 46 of session 1 completed.
TRAFORM: Traffic report for period 46 of session 1 begins.
TRAFORM: Traffic report for period 45 of session 1 completed.

4

Mitel MiVoice Business/MCD/3300 / Re: Handling call forwarding over extensions from two different PRIs

« on: June 26, 2012, 06:53:37 PM »

I can dial any one of our 4 digit numbers (no problems with any extensions).  I'll look into the Personal Ring Group option.

5

Mitel MiVoice Business/MCD/3300 / Re: Handling call forwarding over extensions from two different PRIs

« on: June 21, 2012, 01:00:27 AM »

All I want to do is either call forward from one extension to another through two different Mitel controllers or add a button on each phone that will flash when a call is coming in to the other phone.  If the phones reside in the same building, and on the same controller, I can do this.  For some reason, it does not work when trying to do this through another controller that's at another one of our facilities.  We have 5 Mitel Controllers (each at a different facility) and all are clustered. 

For instance:

Building #1: has extension: 4231 (full number DID: 234-634-4231) - resides on PRI #1
Building #2: has extension: 7342 (full number DID: 423-323-7342) - resides on PRI #2

If 4231 is ringing, I want to have 7342's phone able to receive the call forwarding or see the ringing flash on the phone.
If 7342 is ringing, I want to have 4231's phone able to receive the call forwarding or see the ringing flash on the phone.

if both of these extensions were located in the same building, I can make it work.  Right now, since these extensions are at different facilities and are plugged into different controllers, it does not work.  But, if I'm at either building location, I can dial either extension to reach the other phone.  I just can't call forward.

I'm not sure if I'm making sense about what I'm trying to do, so I need a little direction.  I did not set these controllers up, so my knowledge is limited.

I'm not sure if they are connected to the same PBX, but I don't think they are.

Where do I check to see if the trunks are under a different tenant and how do I check interconnect restrictions?

Mattmayn, I'm not sure how to get the answer to your questions.  Could you tell me where to look?

Thanks,
Shawn

6

Mitel MiVoice Business/MCD/3300 / Re: Handling call forwarding over extensions from two different PRIs

« on: June 19, 2012, 04:50:50 PM »

The PRIs are coming into two different facilities and connected to two different Mitel 3300 controllers.

I did a test by calling my Mitel 5330 from my cell phone and was able to forward the call to an extension on another PRI (in the same building).

I also setup call forwarding from my phone to a phone that is programmed to a number on a different PRI and it worked.  So, I can setup call forwarding to a phone with PRI #1 number to another phone with PRI #2 number as long as they are in the same building.  If I try forwarding a call with the same situation, across buildings and between two different Mitel 3300 controllers, it does not work.  So, the clustered Mitel Controllers must be the issue.  If that's the case, how would I go around that or what would be your recommendations?

I'll see if I can test the following:
"An easy test here is to set up a system speed dial to the remote number - be sure to check 'over ride toll control' - and then forward to the system speed dial.   That will tell you if you have a COR issue."

Thanks,
Shawn

7

Mitel MiVoice Business/MCD/3300 / Handling call forwarding over extensions from two different PRIs

« on: June 19, 2012, 03:17:28 PM »

We have two PRI blocks, with two sets of numbers.  When I try setting up call forwarding from an extension that exist on one PRI to forward to an extension on one of our other PRIs, it does not work.  I think I understand why it doesn't work, but need some direction. 

Example of phone numbers:
PRI #1: 535-334-6132
PRI #2: 774-224-6602

Each, of the two phones, are at separate facilities.  There is one user for both phones.  What would be the best way to handle calls to one phone?  The phone call handling would have to change based on the day the person is at each facility.  Both phones are Mitel 5330.

What would be a good way of configuring the call handling.

Thanks in advance.

8

Mitel MiVoice Business/MCD/3300 / Re: key deleted on phone, phantom voicemail number not working

« on: October 19, 2011, 09:32:07 AM »

I talked to the vendor about re-syncing and he said that it would screw things up even more.  He said that there are no syncronization issues.  He also said that the phantom number 6650 exists behind the scenes and that he would have to consult with Mitel to fix the database.

The phone and extension is back up and running, but I didn't get an explanation yet on how it was fixed.  He said that every extension must exist somewhere.  If it is not a hunt group, email port, ring group, or ACD path, then it must exist as a single line extension.  And the only way to create a single line extension, he said, is to tie it to a phone.  He believes that the proper way of setting up this phantom number, 6650, is to tie it to a phone.  The question I have is, if this phone was unplugged or blew up, for some reason, the phantom line would be affected.

Now, when I do a trace on 6650, it's coming back as a "Non Prime Broadcast Group", so it changed from the original setting of "The number refers to a remote directory number".  He said that Mitel had to dial in with Putty to fix the issue.  I still need an explanation on how they fixed it though, so I understand for future reference.  Can you make anything of this?

Once again, thanks Ralph for all your help on this.

9

Mitel MiVoice Business/MCD/3300 / Re: key deleted on phone, phantom voicemail number not working

« on: October 15, 2011, 10:02:47 PM »

Well, under System Feature Settings --> System Options, "System Data Synchronization" is enabled.  We are running 5 controllers with 4.1 SP1.  Each controller is clustered.  There is a little yellow/green arrow icon that says SDS Share at the top left.  I don't see where the SDS logs are.  Under Software --> Errors, I see a lot of CAVH_WEBSET errors since yesterday, but not sure what that is.

CAVH_WEBSET error reads (not sure if it's related):
updateTuple()->Failed to update Hosted User Service: Need to rollback MLSKA update  The value entered for the following field already exists as a key : 'Service Alias Primary Host Network Element Guid Ref"

Where do I look for resyncing?  I would just like to know where this is at.

Also, it may be an issue.  When the vendor was troubleshooting, he ended up deleting the extension that the key was on.  He discovered that he couldn't delete the extension in the Remote Directory.  I was thinking the same thing, because even though you change it to a 9 key, I thought I remember the values of the buttons still being there if you change the it back to the 48 key (keys 10-48).  I could be wrong, but I thought I saw that before.

I appreciate your help on this...

10

Mitel MiVoice Business/MCD/3300 / Re: key deleted on phone, phantom voicemail number not working

« on: October 15, 2011, 04:01:29 PM »

When you were referring to, "This phone is expected to never be used as a real station.".  Is it that we need to make sure that this is not on a live phone that someone uses?  Because right now, the phone that caused this issue was at our front desk(which also has the main line on it).  Just want to know best practices.

Also, the phone was a 5340.  The extension was programmed on button 41.  It wasn't needed anymore, so the facility decided to have the extension moved to another room and a 5304 phone.  So, I think you are absolutely correct on how it happened (with above 9 keys). 

11

Mitel MiVoice Business/MCD/3300 / Re: key deleted on phone, phantom voicemail number not working

« on: October 15, 2011, 03:46:48 PM »

I'm looking into to this right now.  Ralph, thanks for your reply.  I also got a lot of help from another post of yours:
http://mitelforums.com/forum/index.php?topic=1732.0

Out of 5 controllers, after running the locate command, 4 out of 5 came back with this:
- LOCATE NUMBER 6650
- LOCATE FEATURE EXTENSION 6650
The number refers to a remoate directory number.
Remote DN to CEID 3, routing digits 1113

The controller that the phone was attached to, came back with this after running the command:
- LOCATE NUMBER 6650
- LOCATE FEATURE EXTENSION 6650
The number is not in use.
LOCATE: Invalid or nonexistent extension number or id number.

On the same controller with the problem, I went to ARS Digits Dialed, and 1113 was not displaying.  If you try to manually add 1113 to Digits Dialed, it says "The digits already exist." after hitting submit.  So, something is definitely messed up.


Do you think a restore of the controller would fix the issue?  Also, this extension is connected to our external phantom mailbox number.  People call from home to xxx-xxx-6650.  So, we are not even using it internally, but it still needs to know where to go.  We've already got a button for internal voicemail, which is setup as a CDE Speedcall to number #69999, which is separate from the external phantom number 6650 (that is not working).

The vendor is telling us that he is going to have to call Mitel on Monday for the issue, because he can't fix it.  Do you think this is true? 

So, you are saying that a hunt group setup would fix this issue?

Thanks,

12

Mitel MiVoice Business/MCD/3300 / key deleted on phone, phantom voicemail number not working

« on: October 15, 2011, 09:07:15 AM »

We have a phantom voicemail number not working since a phone was changed out from a 48 key to a 9 key phone.  We have 5 controllers that are clustered, which the phantom extension can be seen on except for the controller that the phone was changed out on.

Any idea of where to start to look for a solution before contacting Mitel support.  I'm hoping some Mitel guru on here can share some good tips.

Thanks