Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: glennmitel on August 09, 2010, 06:39:49 AM
-
Hello
i am having problems getting a 5550 working on Windows 7 with 3300 running 4.1 sp2
i have connected a phone to the same port and the phone boots fine
i have giving the console a static ip which i can ping from the pc but when ever i try and run the 5550 software it tries to config the key pad but will never connect to it
all firewalls are off
i have setup the 5550 in chained mode and dual port and i get the same thing
also it enters a default ICP address of 192.168.1.2 which it seems to look for first
anyone had any problems like this ?
regards
glennmitel
-
What I always do to rule out any hardware problems is to plug the console in the front of the 3300 to see if it can download its firmware (ie the red light goes out). If this works, then put the console back on the network and see if it works
-
hello
i have done this and the red light does go out just will never connect to the pc
-
What version of the IP console program have you installed?
-
latest software
4.0.0.17
-
I've seen something similar when the console software trys to connect to the wrong ICP.
It's been about 3 years to I don't remember the exact fix but look for the config file on the PC and see if the wrong IP is in there.
Also, another thing I'm not sure of, is the 5500 software Win 7 complient?
Ralph
-
I have one running in XP compat mode and it works fine for me.
Do you have any VLANs set up? I have had issues with them not accessing the correct VLAN before but an access port will fix that.
-
please see above
i have tested using phone and the console connected to the front of the 3300 and both work ok
-
Just remembered this....
If you're using LLDP it will not work.
the 5550 is not compatible with LLDP. You'll need to set up options in your DHCP native vlan scope to work.
Ralph
-
so let me get this correct:
You have plugged the keypad into the front of the Mitel 3300 and the PC connects to it?
If you plug it in at the desk the PC cannot connect to it?
-
yes thats correct its setup as an access port on the switch for the voice vlan
-
Can you confirm that when you plug the console keypad on the desk the red light goes out? if so, it is just that the software cannot communicate with the keypad?
Thanks
-
yes please see above
the red light does go out when its connected via the desk
it will attempt to connect to the keypad but never does
-
Something that jumps out at me is that the keypad is plugged into a switch port programmed as an access port.
If I read you right, the PC is plugged into the keypad.
Did you set the PC IP address staticly?
My concern is (or my out loud thought processing) is that the keypad is getting VLAN info and not passing the data through to the PC?
A way to test this is to put a small data switch between the keypad and the data switch, staticly set the PC with an IP address on the voice VLAN and plug it into the new dataswitch. If I'm correct, this will now work. A simpler way, if your not counting on LLDP, is to change the switch port to a trunk port.
Ralph
-
just for testing both the key pad and the pc are on the voice vlan and will not speak but i can ping between them fine
-
Open this file win wordpad and check that the IP address for the controller is correct, if not then change the address and save:
C:\Program Files\Mitel\5550 IP\config\SystemSettings.cfg
-
[System Settings]
# This file contains the system settings for the console application.
# PLEASE DO NOT EDIT THIS FILE!
# consoleType - the "type" of this console, whether it is DNIC or IP
# Possible values: IP, DNIC
consoleType=IP
# codecType - the keypad codec setting
# Possible values: A_LAW, U_LAW
codecType=U_LAW
# Locale information for the languages that this application is available in
# applicationLocale - the locale to be used by the application.
applicationLocale=en
# IPPBXaddress - the IP address or hostname of the IP PBX that this console is connected to.
IPPBXaddress=172.23.34.240
# numberOfDisplayedIPPBXaddresses - the number of additional IPPBXes to display in the Configuration Utility tool
numberOfDisplayedIPPBXaddresses=4
# otherIPPBXaddresses - a list of other addresses IPPBXs that could potentially participate in the discovery process;
otherIPPBXaddresses=
# Ports used to stablish connection between IP PBX and PC - Regular Channel
# IPPBXportForRegularChannel - this is the port that the IP PBX's IP Phone Service Provider (IPSP) listens on. Defined by the IPSP.
IPPBXportForRegularChannel=6800
# PCportForRegularChannel - this is the port that the PC listens on. It is used by the PC for setting socket options. Defined by the SC2000 application software.
PCportForRegularChannel=6900
# Port used to stablish connection between IP-TKB and PC - Control Channel
# PCportForControlChannel - PC listens on this port for messages from the IP-TKB. Defined by SC2000 application and firmware.
# the SC2000 application software and firmware.
PCportForControlChannel=10000
# IPTKBMACaddress - the MAC address of the console's IP telephone keyboard (IP-TKB)
IPTKBMACaddress=08000f242338
# IPPBXRedirectionList - an ordered list of MN3300 IPPBX's to connect to. Defined by IPPBX and received/updated via a redirection message at the PC.
ippbxRedirectionList=192.168.1.2;
# PersonalIdentificationNumber - the last validated PersonalIdentification number entered by the end user (encoded format). The IPPBX will request this during the registration process.
personalIdentificationNumber=
# The number of columns in the BLF tile view
BlfTileColumns=
# The folder path that contains BLF shared lists
BlfPublicFolder=C:\\Program Files\\Mitel\\5550 IP\\config\\
# The folder path that contains BLF private lists
BlfPrivateFolder=
# BusyLampField Development flag to allow BLF to be turned on or off
BlfEnabled=true
# ADF DataFile Path
ADFDirectoryData=
# ADF MappingFile Path
ADFDirectoryMapping=
# ADF CommentsFile Path
ADFDirectoryComments=
# Settings for Instant Messaging presence and Email
PredefinedMsgFolder=
LCSSignInName=
LCSPassword=
LCSAddress=
# Multiple Company Directory Information file
TenantInfoDirectoryMapping=
# Call History
DatabasePanelPassword=
DatabasePanelServerName=
DatabasePanelCallHistoryEnable=
ConsoleDN=
# Teleworker
TunnelIniFileName=
TKBIpAddress=
TKBsubnet=192.168.251.0/24
TeleworkerEnabled=false
-
red is the 3300 RTC address
-
Did it install the software here
C:\Program Files\Mitel\5550 IP\config\SystemSettings.cfg
or here
C:\Program Files (x86)\Mitel\5550 IP\config\SystemSettings.cfg
Try changing the default install path to something like c:\mitel and see what happens
-
Have you tried installing the software on your laptop?
This is really starting to look familiar.
# IPPBXRedirectionList - an ordered list of MN3300 IPPBX's to connect to. Defined by IPPBX and received/updated via a redirection message at the PC.
ippbxRedirectionList=192.168.1.2;
have you tried changing this IP? For some reason I seem to remember that the PC will change this if it can't get to the 3300. Try editing it then restart it. check it again to see if it was overwritten.
Ralph
-
Yeah, I have just checked my config file and this is blank.
-
I just wanted to update this post since I've had several calls within the last month about issues when installing a 5550 console on a Windows 7 PC.
The 5550 console is NOT compatible with the 64 bit version of Windows.
I've also posted a bit more here: www.mitelforums.com/articles/5550-cosole-win-7.php (http://www.mitelforums.com/articles/5550-cosole-win-7.php)
Ralph
-
Stumbled across something on how to make 32 bit apps (read that as Mitel 5550 console) run in 64 bit mode.
www.pcpro.co.uk/blogs/2009/08/06/when-32-bit-apps-dont-work-on-64-bit-windows/#ixzz1ps3XF2nn (http://www.pcpro.co.uk/blogs/2009/08/06/when-32-bit-apps-dont-work-on-64-bit-windows/#ixzz1ps3XF2nn)
Looks pretty simple to try. I just don't have time or an available machine to try in on.
Any volunteers?
Ralph
-
I have the 5550 running in compatability mode at several sites on 64bit machines and it works fine. Disclaimer - I didn't follow the link, I am only guessing that is what it said to do.
-
Have you added the old DHCP options into the server (Option 128 etc)?