Messages

1

Mitel MiVoice Business/MCD/3300 / Re: RCS error, dhcp addresses in use that do not show in viewer

« on: April 05, 2017, 05:48:48 PM »

Problem has been solved by only allowing Mitel devices to connect although I still have a number of System Reserved addresses showing up.

2

Mitel MiVoice Business/MCD/3300 / Re: RCS error, dhcp addresses in use that do not show in viewer

« on: April 05, 2017, 05:05:06 AM »

You can make the dhcp server only serve Mitel ip sets. From what I see, you might have bigger issues.

Using a post on the forum, I redid the DHCP IP address range to allow only Mitel devices to get a DHCP lease last night.  Currently I have five phones out of order.  I will be going in this morning to reset them and see if the error changes.

  A new error started to appear in the DHCP lease viewer, "Server Reserved" and "IP in use" on the same line for multiple IP addresses.  Deleting these has proved to be unhelpful as well.

You should thank your controller that it is not handing out IP addresses that are already in use to phones, because otherwise you would be having all sorts of problems.
 
Basically, your problem is not your DHCP server or scope.
Your problem is your network is broken. Get whoever is in charge of that to fix it - you should not be getting any devices on the Data VLAN contacting your 3300 for DHCP. Either they've put an IP helper on the Data VLAN interface pointing at the controller, or they've somehow bridged the VLANs. Or maybe the 3300 is on the Data subnet, which would be very lame. Or maybe the Data VLAN has been added to the switchport the controller is patched to (although "IP in use" hints this isn't the issue).
 
Having said that - why is your DHCP scope restricted to 209 entries? Just make it bigger.
 
If you have access to the switch infrastructure, get on your "core" switch and run a "show mac-address table". Find all the MAC addresses that aren't phones and that are occupying a DHCP lease on the 3300 and look at what switchport they are on. If it's an uplink, get on the relevant switch and run the command on it.
pull the cable out of each port these devices are on (in order to kill their network cards), then delete those leases in DHCP, and make sure the network is fixed otherwise it will just happen again.

I just gained access to the switches yesterday afternoon.  The configuration has the VoIP and Data networks completely separate.  I did check the switches and found several suspect ports I will be going in shortly to check that were not getting PoE but had a connection.  I have expanded the scope several times, but the moment I do, the IPs are taken up almost immediately before a phone can even get one, so I reduced it back down to the number of licenses I have for the time being. 

3

Mitel MiVoice Business/MCD/3300 / RCS error, dhcp addresses in use that do not show in viewer

« on: April 04, 2017, 06:33:28 PM »

Good evening, for the past 4 days, I have been having trouble with one of my 3300's.  New phones installed got the RCS error, until I expanded the DHCP scope by 5 more addresses.  After that, I started to notice that some of the MAC addresses in the DHCP Lease Viewer were not phones, even after deleting the lease, the device would still hold onto that address making it unusable for a phone.  This led into phones not being able to get DHCP addresses, we saw there was a data crossover and removed it.  This solved our random MAC addresses appearing in the DHCP lease viewer, however some addresses still were unavailable, and even addresses that were not taken could not be used to static a phone.  A new error started to appear in the DHCP lease viewer, "Server Reserved" and "IP in use" on the same line for multiple IP addresses.  Deleting these has proved to be unhelpful as well.

Currently, I have 204 phones at this site, licenses for 209.  I have 209 IP addresses reserved in my DHCP IP Address Range, however in the DHCP viewer I only have 174 IP addresses showing, and when I check to see which phones are out of service, I see anywhere between 4 to 9 phones.  The numbers and situation is not making sense to me at all.

Does anyone have any suggestions for me or have encountered this problem before?

4

Mitel MiVoice Business/MCD/3300 / Re: Night Service Generic Message instead of Recorded

« on: February 23, 2016, 05:08:10 AM »

The voicemail has been changed for box 0, but how do I go about what tjcurcio suggested?

5

Mitel MiVoice Business/MCD/3300 / Re: Night Service Generic Message instead of Recorded

« on: February 22, 2016, 01:27:05 PM »

6700 is a hunt group which goes to 3 lines.  The Voicemail box is set to 0 (not by me), if the system is in Night Mode, it does redirect to 0.  However as this is also the operators mailbox, and we setup the mailbox thro 9999 (admin console), that message is not getting played. 

6

Mitel MiVoice Business/MCD/3300 / Re: Night Service Generic Message instead of Recorded

« on: February 22, 2016, 08:02:18 AM »

Four digits, 6700.  The voicemail goes to this mailbox, however the greetings do not match up with what was set for Night Service using the admin console.  You'll have to forgive me, but I am not familiar with what a RAD message means

7

Mitel MiVoice Business/MCD/3300 / Re: Night Service Generic Message instead of Recorded

« on: February 22, 2016, 05:07:30 AM »

The call does not go to voicemail during day mode, only night mode.  The problem being is it is not the recording for Night Mode which was configured, it is a just a generic "no one here to answer your call please leave a message"

8

Mitel MiVoice Business/MCD/3300 / Re: Night Service Generic Message instead of Recorded

« on: February 21, 2016, 05:55:16 AM »

Yes the system follows a schedule for Night Mode, which I have confirmed to be working.  If the system is not in Night mode, the phone doesn't go to a voicemail, instead it just rings indefinitely. 

9

Mitel MiVoice Business/MCD/3300 / Night Service Generic Message instead of Recorded

« on: February 20, 2016, 07:56:46 PM »

Good evening,

I have been trying to figure this out for days, and have compared 10 systems to this one and can't find a difference between them.

My problem is, I went into the admin mailbox and set the day/night1/2 messages, however when you call the building it rings once and goes to a generic voicemail.  The voicemail is still accessible and does record, however the powers at be would like something different than the generic voicemail and I cannot figure out why it does not go to those messages we recorded.  I do know the messages exist because if I hit * quickly on the generic it goes to that message.

The scheduling is set and working, but still generic.

Any help is appreciated, thank you in advance.

10

Mitel SX200, SX2000, and older SX platforms / Re: Cannot get Anolog Lines off of locked out

« on: December 18, 2015, 07:34:18 AM »

Thank you for the advice, I had already checked the first three things you had listed but rechecked them and power cycled the card and it did the trick.  Thank you very much.

11

Mitel SX200, SX2000, and older SX platforms / Cannot get Anolog Lines off of locked out

« on: December 17, 2015, 01:20:25 PM »

Good afternoon,

I was hoping to get a little advice as to approaching the "Locked Out" analog lines I have.  I have two extensions like this, before they were not receiving power or dial tone, so I replaced the plate and re-punched the wires.  Now sadly my analog phones get power but still no dial tone.  When doing a status check on them it shows them "Locked Out" which is different from before, they showed idle but obviously did not work.  I've tried RTS and a few other things, but to no avail.  When clearing the sets I have to Force it due to circuit activity. 

Sadly, I also do not normally work on the telephones physically diagnosing them so I do not have tools such as a butt set so testing the line is a bit difficult.

Any suggestions would be appreciated.  Thank you.

Update:
So the statuswent to idle after removing and resetting, however I still get no dial tone and no one can call in.  I have attached a screenshot of what happens when you try to call the number.  After calling in, it goes to busy and then back to locked out.