Configuration of static IP address for 5550 console on Mitel 3300 rel 5.0

[melabum]

Please, any idea on how to program static IP address for 5550 console with the Mitel DHCP disabled?

Again, any possible idea why a functional console (goes off intermittently) is generating false ringing repeatedly without incoming calls?

[martyn]

The console must use DHCP, so not really too many options there.

As for the problem, can you expand any further on the issue, software release, etc?

[melabum]

It is really difficult having 5550 console on DHCP as at every IP address expiration, it can easily go ff. I wonder if there is a way out of this.
 
Curiously, rather than the 5550 console keypad receiving its own IP address , is sharing IP address with the PC. The PC is plugged at the back of the keypad.

On the reported false ringer tone, the ringing tone frequently repeats as if calls are incoming into the console but no calls at all. The ringing tone repeats at an interval of 60 seconds. The software version of the 5550 application is 4.2.0.28 while that of the keypad is 9.7.0.3

[MitelUK2010]

Does the system have an alarm? I believe the console gets a notification of a particular alarm status.

[martyn]

Yes that does sound like a system alarm that is generating the beep. Does the console software show a green tick or a red cross?

The other reason that you must use DHCP is so that the keypad can get option 125 so that it knows where to go for TFTP and registration. Without this it would just sit there with the red light on constantly.

I'm not quite following what you mean by the console going off every time it renews it's IP address via dhcp. Does it reboot? Does it drop the call? If it does either then it's a faulty keypad, as this shouldn't happen. What is the lease time on the DHCP server?
Basically when a device gets an IP address via DHCP it leases it for x amount of time (default is 8 days unless changed). At half of the lease time the device then requests again and renews, so if the lease was 8 days then after 4 the keypad renews the lease again. If the address isn't renewed by the end of the lease time then the address is removed from the lease table and made available for another device to receive.

Two devices cannot share the same IP address on the same network. If they do there is now way for ARP to resolve the IP address to a MAC address as it wouldn't know which device to send the packet to.

[ralph]

Curiously, rather than the 5550 console keypad receiving its own IP address , is sharing IP address with the PC.

As martyn pointed out - this isn't supposed to happen.  If it does things won't work.
See if you can set a reserved IP in your DHCP server based on the MAC address of the keypad.

Ralph

[LoopyLou]

Typically you setup a static entry in the 3300 DHCP server for the keypad. If you are not using the 3300 for DHCP ( won't ask why not ) then can you duplicate the static entry ( against the MAC address ) in your corporate DHCP server? The PC should definately not use the same IP address as the keypad even if plugged into the keypad. Something is really amise if that is happening.

The repeating ringing could be cause by your weird setup but as other users have suggested the console can alarm and produce a sound on system alarms or if it is setup as a 911 reporting desitination .

Why you lose connectivity? It could be the keypad, the RJ45 cable, the layer 2 port, routing on your network. Should I continue?