Messages

3841

Mitel MiVoice Business/MCD/3300 / Re: Analog lines sounding 'Fuzzy' on Mitel 3300

« on: October 10, 2012, 02:49:22 PM »

Have you ran the LS Line Quality Measurement Test and set balance and trunk category accordingly? Typically when I have issues where LS trunks sound good ahead of the system then have audio issues inside the system, this is the issue.

3842

Mitel MiVoice Business/MCD/3300 / Re: High-End Set Handset Config errors?

« on: October 10, 2012, 02:42:02 PM »

Yeah, pretty much gave up on this... Everything works and there are no sync errors, it still shows some forms are out of sync if I do a manual compare of the two forms, but even if the phones fail over then back everything is working correctly.

3843

Mitel MiVoice Business/MCD/3300 / Re: SDS Sharing

« on: October 10, 2012, 02:39:35 PM »

Actually, if you get basic Sharing to be working and share the "Shared Forms" form, you can make the changes on one controller and it will be pushed out via SDS to all controllers.

I actually recommend trying to share as much data as possible, it will eliminate future issues with Local Directory Numbers, if they are in use and you want to start sharing some of them, you have to delete every instance in every controller prior to doing that. The more you share (and is in sync) the less problems you have later. Also remember with resiliency, all aspects of the device need to be resilient... for example, if you have a hunt group that is resilient, it is best practice to have all members be resilient to the same controllers, and all keys be uniform. This also leads into sharing feature access codes, system speed calls, class of service, class of restriction, etc... everything on a station level should be shared if any resiliency is going to be implemented.

3844

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 to Exchange 2012

« on: October 08, 2012, 05:12:44 PM »

I think UM in the 5000 just uses IMAP integration, that is why you have to enter the username and password in each mailbox... it is not like BBES or Nupoint UM Exchange integration, so nothing special really, just have your exchange tech enable IMAP and should be good to go!

3845

Mitel MiVoice Business/MCD/3300 / Re: Mitel 5312 IP Telephones - reboots when pressing 3 key to delete a VM

« on: October 08, 2012, 10:36:05 AM »

Can't say I've ever heard of this.   This is a new one on me.   
Are you using the embedded VM?

I've seen something similar with 5330/5340 phones when trying to transfer a call.   A wireshark sniff showed an ICMP redirect.   
Turning off ICMP redirect in the cisco switches resolved.

Ralph

This is why I like this forum... where else would you get knowledge like this. 

3846

MiVoice Office 250/Mitel 5000 / Re: Mitel 5000 BRM-2 Card

« on: October 08, 2012, 10:32:45 AM »

Hmmm... I see no mention of a BRM-2 card in any system documentation prior to Release 5.1, any reference to BRM before that was to a BRM-S card.

My best guess is that 5.1 is required to support it, but I cannot find anything to confirm that.

3847

Mitel MiVoice Business/MCD/3300 / Re: 5312 IP Telephones

« on: October 08, 2012, 01:11:33 AM »

Can't say I have heard of this one either, I can tell you that I have thousands of these sets out there on varied systems and software releases and if it was happening customers would report it...

What system and software release? Only 5312's?

3848

Non-Mitel Chatter / Re: MitelForums IRC Channel?

« on: October 08, 2012, 01:08:05 AM »

No... it is actually on my "to-do" list, but with the way things are right now it might be a couple weeks until I can get it all setup, work has been a killer recently with some really huge projects going on.

3849

Mitel MiVoice Business/MCD/3300 / Re: High-End Set Handset Config errors?

« on: October 07, 2012, 11:49:49 AM »

Tried all that stuff... All sites are up to MCD 4.2 and the sync now completes with no errors, but if you do a manual form comparison it still shows the forms are different, but there is really no place to fix it.

Very odd. So far all is good though, even if the phones are forced to their resilient pair everything works as normal.

Guess that is a problem for another day, should it arise... Don't really want to keep messing with these phones, 4 of the 5 are 5235's with at least one PKM and are "main" phones for various emergency services like fire and PD.

3850

Mitel MiVoice Business/MCD/3300 / Re: High-End Set Handset Config errors?

« on: October 06, 2012, 01:14:58 PM »

Hmmm... very odd but it seems after the upgrade of system to MCD 4.2 the errors just went away, all syncing is working and it is showing no errors at all. Perhaps it was just a minor database corruption and during the upgrade(s) it was cleaned out, hoping so anyways...

One site left to upgrade to 4.2 but can't do it until tomorrow at 7:30am, then it is just clean-up and tweak... So there is finally a light at the end of the tunnel on my most dreaded project of the last two years, which turned out to be much less problematic than I thought. 

3851

Mitel MiVoice Business/MCD/3300 / Re: Clicking noise on some calls

« on: October 06, 2012, 01:11:19 PM »

I have to agree with ralph on this one, this is almost always a PRI or T1 issue, often related to clocking. Verify your clocking source is set correctly and if the problem continues I would contact your PRI vendor.

3852

MiVoice Office 250/Mitel 5000 / Re: Adding waiting call to conference?

« on: October 05, 2012, 08:09:06 PM »

Press Conference, then dial the Reverse Transfer code (typically 4) plus the extension where the call is on hold, then Conference again twice.

3853

Mitel MiVoice Business/MCD/3300 / Re: High-End Set Handset Config errors?

« on: October 05, 2012, 05:05:35 PM »

Well, we removed the resiliency on these phones, then did a compare and things looked fine, redid the resiliency and the COMPARE errors are back, but no erros in sync... very strange. We are still awaiting engineering from Mitel to give us a resolution but since there are no errors in teh sync, we are going to go ahead with the DB conversion to RDN tonight at 5 and start the next round of updates to MCD 4.2. The highest we can go with the current 6510 VM that the customer has.

If the problem still exists after an upgrade (and thus reload of database) we are just supposed to delete and remove the sets completely. Tech support had no further information on what this really was, they just got that answer from engineering.

3854

Mitel MiVoice Business/MCD/3300 / High-End Set Handset Config errors?

« on: October 04, 2012, 05:33:14 PM »

Doing a migration of a cluster from 9.0/OPSMAN to MCD4.0, getting things all in sync getting ready to convert to RDN and go up again... getting a weird error I can't find...

Forms Comparison:

Comparing High-End Set Handset Config between Cityhall and Policedp

Detail:
Record (DN:1405, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1424, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1594, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1860, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1937, Handset Mode:1, Left Handset Type:1) only exists on Cityhall

Summary:
147 records compared
147 records match
5 records only exist on Cityhall

Everything else is in sync between 11 nodes except this... This one is new to me... any ideas on how to correct this?

EDIT: All of these devices exist as primary in Policedp and resilient in Cityhall, we removed the resiliency, verified they were gone from Cityhall, then put the resiliency back in place and the problem still exists. Weird.

3855

Mitel MiVoice Business/MCD/3300 / Re: ICP has Lost Contact...

« on: September 28, 2012, 09:27:24 AM »

Heartbeat Server is kind of a misnomer... it is a service in the 3300 that periodically "checks" its connection to various devices and services, when there is no response or a message is expected within a certain time frame, then it generates this message. My guess is the 1915 is the port it is using, 172.16.2.2:1915 would indicate it is trying to talk to a device at 172.16.2.2 on TCP (or UDP) port 1915.

It sounds like for some reason the link to a remove 3300 is being lost for a few moments, this could be the result of any number of network or hardware issues, from as simple as a bad cable to too many kids in the apartment building next door are streaming Crackle videos at 9PM and bogging out the area's bandwidth. Or this could be your IT department imaging mass numbers of computers after hours, totally bogging down the network momentarily. My point is that it's just an indication the 3300 sees something, but that in itself isn't much to go on, although you mention an IP Trunk Link is returned to service shortly after, look at that link (pings, traceroutes, etc) for anything unusual and check the logs in the remote equipment for indications of the issue.

That being said, sometimes the 3300 is a bit over zealous in it's logging, and you need to just ignore some stuff. If this does not seem to be service effecting, not getting worse, and not consistent, I would monitor it but unless something changes I probably wouldn't do anything at this point.