I also have had no problems with this file....weird.
Announcement
Collapse
No announcement yet.
Instant Messenging Connector for Live Messenger and Google Talk (Jabber)
Collapse
This topic is closed.
X
This is a sticky topic.
X
X
-
I just tried to download and unzip on an other computer, and had no problem.
On this secondary computer there is another Unzipper called ZipGenius that had no problem to dezip the file.
You may want to download & install free ZipGenius from http://www.zipgenius.com/--
stipus
Comment
-
Guest
the problem must be with my service provider, as the genius zip file that i downloaded was also currupted.
thanks for you help and patience anyway
Comment
-
Display Picture
Hi Everyone,
Great product - works like a charm Just wondering if there's anyway to change the display picture? My house (Vicki) is personified by by the iRobot character Sonny and I was hoping to put a picture as the display picture for MSN convos.
Thanks in advance
Edit: I originally logged into the MSN account dna changed it that way, but it just took a while to appear on my account during convos.
Comment
-
Hi
I have an issue that is similar to post 215 above but I don't think it is the same solution to the problem.
I have just purchased the IM connector from the HomeSeer Store. I've installed the plug-in and I've then copied the files in the post "Instant Messenging Connector for Live Messenger & Google Talk - Last Version" on this forum for the latest version of the IM connector, marked 4.83.2.4 on the "connector configuration" screen in HS. I've then applied the licence key I bought from the HS Store. I run XP SP3 32 Bit on HSPro v2.5.0.21. I upgraded to HS Pro a few months ago from HS. I run HS from a batch file in the start-up group, not as a service. After XP boots the startup group batch file waits for 30 seconds before starting HS to make sure ip etc are up and running ok. The HS PC is connected to the internet by Ethernet to an always on internet connection. The account that runs HS has admin rights and the box is patched up to date.
I've set up a new MSN account for HS and I've entered the settings for the username and password. I've also told the IM connector about the two IM users from other MSN accounts who can access the IM Connector. With the IM Connector's debug mode turned on I can see that the IM connector starts up ok and I can talk to the IM connector from other PCs via MSN while they are logged in the the 'approved' MSN accounts.
If I stop and start HS (but not the PC) the IM Connector goes down with HS and comes back up with no problems. I can restart HS on its own and the IM connector works ok. Here is the logfile output when I reload the IM config from HS:
09/09/2011 08:39:21 - IM Debug - MsnClient Connection Closed event received
09/09/2011 08:39:21 - IM Debug - MsnClient Connection Closed event received
09/09/2011 08:39:21 - IM Debug - IM Connector : MsnClient Disconnected from MSN server
09/09/2011 08:39:21 - IM Debug - MsnClient Connection Closed event received
09/09/2011 08:39:21 - IM Debug - IM Connector : MsnClient Disconnected from MSN server
09/09/2011 08:39:21 - IM Debug - MsnClient Connection Closed event received
09/09/2011 08:39:24 - IM Debug - IM Connector : Debug Mode activated. Waiting 0 secs...
09/09/2011 08:39:29 - IM Debug - Loaded MSN User xxxxx@xxxxx.com - Access Level ADMIN
09/09/2011 08:39:29 - IM Debug - Loaded MSN User xxxxxx@xxxxxxxx.com - Access Level ADMIN
09/09/2011 08:39:29 - IM Debug - MSN settings loaded - User: yyyyyyyy@live.co.uk
09/09/2011 08:39:29 - IM Debug - IM Connector : Found MSN IO device ^2 - Name= MSN - Location= IM Network
09/09/2011 08:39:29 - IM Debug - IM Connector : MsnClient connecting to MSN server...
09/09/2011 08:39:29 - IM Debug - IM Connector : MsnClient Connected to MSN server
09/09/2011 08:39:30 - IM Debug - MsnClient Connection Closed event received
09/09/2011 08:39:30 - IM Debug - IM Connector : MsnClient Connected to MSN server
09/09/2011 08:39:35 - IM Debug - IM Connector : MsnClient Authenticated user yyyyyyyy@live.co.uk as zzzzz
09/09/2011 08:39:36 - IM Debug - MsnClient PingAnswer() event. Timeout=46
However if I stop HS manually, wait for it to close and then reboot the PC gracefully when the PC comes back up and starts the IM Connector I see the following in the HS log:
09/09/2011 08:46:53 - Plug-In - Initializing Plug-in: IM Connector
09/09/2011 08:46:53 - IM Debug - IM Connector : Debug Mode activated. Waiting 0 secs...
09/09/2011 08:46:53 - IM Debug - Error : Error loading AIML settings: Unable to find the specified file.
09/09/2011 08:46:53 - IM Debug - IM Connector : LoadConfig() failed. Aborting
09/09/2011 08:46:53 - Error - Initializing interface: IM Connector->1
09/09/2011 08:46:53 - Plug-In - Finished initializing plug-in IM Connector
Now if I restart HS again (but not XP) just after the PC has rebooted I get the errors above. However if I leave the PC running for a few minutes and restart HS the IM connector works fine! It is as if the IM connector is relying on something in HS during startup that HS hasn't quite started yet. The PC I'm running HS on has a 3.8GHz dual core CPU with 4Gb of RAM and lots of free disk space so I don't believe I have a performance issue. During the XP reboots no other errors are seen in the HS log or in the Windows event log. As soon as XP boots if I launch a cmd prompt I can ping www.google.com and so I know the Ethernet connection is up, as is the internet connection.
I've checked my IM config directory, as mentioned in post 215 above, and it is set to the text below. I have not had to changed this since installation as I believe the latest version I have of the IM connector does not need a change.
In the file Config\hspi_im.ini there is an entry called DebugWait which was originally set to 0 seconds. I tried setting this to 30 and then 300 seconds to see if an extra delay would help the IM connector wait for HS to finish starting up but the issue remained. The problem here might be that even though the IM Connector waits 300 seconds before starting it delays everything else that starts after the IM Connector by 300 seconds too and I presume the IM Connector is waiting for something that starts after this time. For example the webserver service starts after the IM Connector, does the IM Connector need this service to function?
My HSLog with DebugWait set to 300 seconds after XP has been booted and HS automatically started is shown below:
09/09/2011 10:11:16 - Startup -
09/09/2011 10:11:16 - Startup - ************************************************************ ********************
09/09/2011 10:11:16 - Startup - HomeSeer version 2.5.0.21 Starting Now (PRO Build)
09/09/2011 10:11:16 - Startup - ************************************************************ ********************
09/09/2011 10:11:16 - Startup -
09/09/2011 10:11:16 - Startup - Using system's regional settings
09/09/2011 10:11:16 - Startup - Creating Class Objects...
09/09/2011 10:11:16 - Startup - COM port classes started.
09/09/2011 10:11:16 - Startup - Application interface class started.
09/09/2011 10:11:16 - Startup - Web server class started.
09/09/2011 10:11:16 - Startup - E-Mail SEND class started.
09/09/2011 10:11:16 - Startup - E-Mail RECEIVE class started.
09/09/2011 10:11:16 - Startup - Z-Wave class started.
09/09/2011 10:11:16 - Startup - Plug-In Interface class started.
09/09/2011 10:11:16 - Startup - Speech recognition class started.
09/09/2011 10:11:16 - Startup - HSPhone dialer class started.
09/09/2011 10:11:16 - Startup - Loading Settings
09/09/2011 10:11:16 - Startup - Settings Loaded.
09/09/2011 10:11:16 - Startup - Current sunrise/sunset values calculated.
09/09/2011 10:11:16 - Startup - HSPhone external interface class started.
09/09/2011 10:11:16 - Startup - Local voice recognition class started.
09/09/2011 10:11:16 - Startup - Database SAVE process started.
09/09/2011 10:11:16 - Startup - Loading configuration file ...
09/09/2011 10:11:16 - System - Loading device types file...
09/09/2011 10:11:16 - Database - Opening (Mode=Read) up HomeSeer database: C:\Program Files\HomeSeer HS2\Config\sample.mdb
09/09/2011 10:11:16 - Database - Loading Devices...
09/09/2011 10:11:17 - Load Config - 221 total devices loaded.
09/09/2011 10:11:17 - Load Config - Checking device type settings for all devices...
09/09/2011 10:11:17 - Load Config - Finished checking device type settings.
09/09/2011 10:11:17 - Load Config - Loading Events...
09/09/2011 10:11:19 - Load Config - 305 total events loaded.
09/09/2011 10:11:19 - Database - HomeSeer configuration database C:\Program Files\HomeSeer HS2\Config\sample.mdb has been closed.
09/09/2011 10:11:19 - Startup - HomeSeer version is: 2.5.0.21
09/09/2011 10:11:19 - Startup - Starting remoting (Remote client connection monitor)
09/09/2011 10:11:20 - Startup - Creating Speaker Client Interface Object...
09/09/2011 10:11:20 - Startup - Initializing phone interface...
09/09/2011 10:11:21 - HSPhone - HomeSeer Phone Web Interface initializing.
09/09/2011 10:11:21 - HSPhone - Adding phone line 2, Name: Default Line, Modem: Way2Call Hi-Phone Desktop
09/09/2011 10:11:21 - HSPhone - HomeSeer Phone Web Interface initializing.
09/09/2011 10:11:21 - Phone Line 2 - Initializing Hi-Phone device...
09/09/2011 10:11:21 - HSPhone - Resetting line: Default Line
09/09/2011 10:11:24 - HSPhone - Wave OUT id: 0
09/09/2011 10:11:24 - HSPhone - Found Hi-Phone audio device: Hi-Phone Desktop USB
09/09/2011 10:11:24 - HSPhone - Wave IN id: 2
09/09/2011 10:11:24 - HSPhone - Voice Recognition Language ID: 1033
09/09/2011 10:11:25 - HSPhone - Calling hangup for line: Default Line
09/09/2011 10:11:25 - HSPhone - Enter OpenLine, line: Default Line
09/09/2011 10:11:25 - HSPhone - Enter WaitForCall, modem: 2
09/09/2011 10:11:25 - HSPhone - Muting rings disabled
09/09/2011 10:11:28 - HSPhone - Finished Resetting line: Default Line
09/09/2011 10:11:28 - Startup - Checking for pending updates to be installed...
09/09/2011 10:11:28 - Startup - Restoring Device Status...
09/09/2011 10:11:29 - Startup - Checking for available plug-ins
09/09/2011 10:11:29 - Plug-In - Found plug-in: BLBackup, version: 1.0.29.0
09/09/2011 10:11:29 - Plug-In - Found plug-in: X10 CM11A/CM12U, version: 2.2.0.4
09/09/2011 10:11:29 - Plug-In - Found plug-in: HSTouch Server, version: 1.0.0.42
09/09/2011 10:11:29 - Plug-In - Found plug-in: HSTouch Android, version: 1.0.0.0
09/09/2011 10:11:29 - Plug-In - Found plug-in: HSTouch iPhone, version: 1.0.0.0
09/09/2011 10:11:29 - Plug-In - Found plug-in: HSTouch Server Unlimited, version: 1.0.0.1
09/09/2011 10:11:30 - Plug-In - Found plug-in: IM Connector, version: 4.83.2.4
09/09/2011 10:11:30 - Plug-In - Found plug-in: IRTrans, version: 1.2.15.0
09/09/2011 10:11:30 - Plug-In - Found plug-in: MytMyk Phidgets, version: 1.0.0.1
09/09/2011 10:11:31 - Plug-In - Found plug-in: SIP Connector, version: 2.56.2.4
09/09/2011 10:11:31 - Plug-In - Found plug-in: UltraMon, version: 1.1.4246.36196
09/09/2011 10:11:31 - Startup - Initializing Plug-Ins
09/09/2011 10:11:31 - BLBackup start - Register Callback completed
09/09/2011 10:11:31 - BLBackup start - BLBackup version is: 1.0.29.0
09/09/2011 10:11:31 - Plug-In - Initializing Plug-in: BLBackup
09/09/2011 10:11:31 - BLBackup start - Initializing BLBackup...
09/09/2011 10:11:31 - BLBackup start - Loaded configuration successfully
09/09/2011 10:11:32 - BLBackup start - Backup Folders have been loaded.
09/09/2011 10:11:32 - BLBackup start - BLBackup plugin has been initialized
09/09/2011 10:11:32 - Plug-In - Finished initializing plug-in BLBackup
09/09/2011 10:11:32 - Plug-In - Initializing Plug-in: MytMyk Phidgets
09/09/2011 10:11:32 - MytMyk Phidgets - Looking for Phidget Interface on Local...
09/09/2011 10:11:32 - Plug-In - Finished initializing plug-in MytMyk Phidgets
09/09/2011 10:11:33 - MytMyk Phidgets - CONNECTED TO PHIDGET (local) - [Phidget InterfaceKit 8/8/8 , Serial: 126328 , Version: 901]
09/09/2011 10:11:33 - MytMyk Phidgets - 24 Phidget devices found in HS
09/09/2011 10:11:33 - UltraMon Info - UltraMon version 1.1.4246.36196 starting ...
09/09/2011 10:11:33 - Plug-In - Initializing Plug-in: UltraMon
09/09/2011 10:11:33 - UltraMon Info - UltraMon - initializing I/O ...
09/09/2011 10:11:33 - Plug-In - Finished initializing plug-in UltraMon
09/09/2011 10:11:33 - HSTouch Server Unl - Register callback completed
09/09/2011 10:11:33 - Plug-In - Initializing Plug-in: HSTouch Server Unlimited
09/09/2011 10:11:33 - HSTouch Server Unl - HSTouch Server Unlimited plugin initialized.
09/09/2011 10:11:33 - Plug-In - Finished initializing plug-in HSTouch Server Unlimited
09/09/2011 10:11:33 - HSTouch Server - Register callback completed
09/09/2011 10:11:33 - Plug-In - Initializing Plug-in: HSTouch Server
09/09/2011 10:11:33 - UltraMon Info - Monitoring IP addresses in 192.168.2.0/24.
09/09/2011 10:11:33 - HSTouch Server - Registered for STATUS CHANGE callback.
09/09/2011 10:11:33 - HSTouch Server - Registered for STRING CHANGE callback.
09/09/2011 10:11:33 - HSTouch Server - Registered for CONFIG CHANGE callback.
09/09/2011 10:11:33 - HSTouch Server - Registered for CALLER-ID callback.
09/09/2011 10:11:33 - HSTouch Server - Registered for VALUE CHANGE callback.
09/09/2011 10:11:33 - HSTouch Server - Registered for GENERIC EVENT callback.
09/09/2011 10:11:33 - Plug-In - Finished initializing plug-in HSTouch Server
09/09/2011 10:11:33 - HSTouch iPhone - Register callback completed
09/09/2011 10:11:33 - Plug-In - Initializing Plug-in: HSTouch iPhone
09/09/2011 10:11:33 - HSTouch iPhone - HSTouch iPhone plugin initialized.
09/09/2011 10:11:33 - Plug-In - Finished initializing plug-in HSTouch iPhone
09/09/2011 10:11:33 - IM Connector - IM Connector 4.83.2.4 Copyright 2005-2009 stipus@stipus.com
09/09/2011 10:11:33 - Plug-In - Initializing Plug-in: IM Connector
09/09/2011 10:11:34 - IM Debug - IM Connector : Debug Mode activated. Waiting 300 secs...
09/09/2011 10:16:34 - IM Debug - Error : Error loading AIML settings: Unable to find the specified file.
09/09/2011 10:16:34 - IM Debug - IM Connector : LoadConfig() failed. Aborting
09/09/2011 10:16:34 - Error - Initializing interface: IM Connector->1
09/09/2011 10:16:34 - Plug-In - Finished initializing plug-in IM Connector
09/09/2011 10:16:34 - Plug-In - Initializing X10 Plug-in: X10 CM11A/CM12U On COM Port 1
09/09/2011 10:16:34 - Plug-In - Initializing Plug-in: X10 CM11A/CM12U
09/09/2011 10:16:34 - Info - Initializing CM11A/12U on COM port 1
09/09/2011 10:16:34 - Plug-In - Finished initializing X10 interface X10 CM11A/CM12U
09/09/2011 10:16:34 - IRTrans - IRTrans Plugin Version 1.2.15.0
09/09/2011 10:16:34 - Plug-In - Initializing Infrared interface IRTrans on COM 2
09/09/2011 10:16:34 - IRTrans - Connection to 127.0.0.1 was successful.
09/09/2011 10:16:34 - Plug-In - Finished initializing infrared interface IRTrans
09/09/2011 10:16:34 - HSPhone - HomeSeer Phone Web Interface initializing.
09/09/2011 10:16:35 - Web Server - Local IP address (subnet) is: 192.168.2.83 (255.255.255.0)
09/09/2011 10:16:35 - Web Server - Web Server started on port 80
09/09/2011 10:16:35 - Startup - Creating ASP.NET application host...
09/09/2011 10:16:41 - Startup - ASP.NET application host created
09/09/2011 10:16:41 - Startup - Start automation engine...
09/09/2011 10:16:41 - Startup - This version of HomeSeer is registered.
09/09/2011 10:16:41 - Startup - Initializing Speaker Client Interface
09/09/2011 10:16:41 - Speech - Listening for remote speaker connections on port 8742
09/09/2011 10:16:41 - Startup - HS2Sentry is disabled in Setup, sentry will not be started.
09/09/2011 10:16:41 - Startup - Starting Event Scheduler...
09/09/2011 10:16:41 - Startup - Checking HTTP connection...
09/09/2011 10:16:43 - Web Server - Web Server authorized local login successful from: 127.0.0.1 User: default
09/09/2011 10:16:43 - Startup - Updater services starting...
09/09/2011 10:16:43 - Startup - Starting DDNS service...
09/09/2011 10:16:43 - Startup - Running the Startup.txt Script
09/09/2011 10:16:43 - HSTouch Server - HomeSeer has started
09/09/2011 10:16:43 - HSTouch Server - Server is enabled for unlimited connections.
09/09/2011 10:16:43 - HSTouch Server - Server is enabled for iPhone/iPod HSTouch connections.
09/09/2011 10:16:43 - HSTouch Server - Server started on port 10200
09/09/2011 10:16:43 - Script Startup - Scripting is OK, running startup scripts...
09/09/2011 10:16:48 - Script Startup - Finished running startup scripts
09/09/2011 10:16:48 - Startup - Start up complete.
I removed the start-up entry that starts HS from XP and rebooted the PC. I left the PC running for 10 minutes (which is normally enough time to wait after XP boots to restart HS to stop the IM Connector issue) and then started HS. HS and the IM connector now start up fine. It appears as if the IM connector is waiting for something on the PC to start before the IM Connector can start successfully. In the Windows event log the only entries mentioned as starting after HS is started (on a 30 second delay post boot) on a clean boot are "Telephony Service" and "Remote Access Connection Manager". I changed the HS delay to start HS after XP boots in my script from 30 seconds to 360 seconds and restarted XP. but the IM connector still fails as above. If I stop and start the IM connector it comes up fine still though. I changed the delay after a boot to start HS to 600 seconds and after a reboot the IM connector fault still remains.
I then checked what processes are running when XP boots, when HS is started and also when HS it started and shutdown to see if anything was being left running when HS was shutdown that means the IM connector is happy on the second run of HS. There are no differences in the processes running from when XP boost and XP boots, run HS and then HS is shutdown. The extra processes running when HS is started, as reported by task manager, are homeseer.exe, hs_compatibility.exe and hsrecord2.exe.
This means I can only start HS with the IM Connector working if:
1) I disable automatic starting of HS and after XP has booted start HS myself after a few minutes delay. Incidentally my start-up group batch file that starts HS just calls the HS executable directly.
2) I let XP boot and start HS automatically. I then stop HS and restart it after a few minutes.
One thing I should mention is that I have had issues in the past with long file names. When I started to use HSPhone I couldn't get it to work. After contacting support and seeing a code snippet in HSPhone I could see they did not enclose filenames in quotes. This code worked fine on some systems without quotes around config files but it would not work on mine. HS support sent me an updated exe file that had quotes around the full path and filename to the HSPhone config file and HSPone then worked ok on my system. HS then rolled this update out with other fixes via the updater. Is it possible that long file names are the cause of the issue here? You would of thought that a file name issue would not be intermittent but you never know!
I'm now not sure what the next step is to try and get the IM connector to start with HS reliably. Any assistance would be appreciated.
Many thanksLast edited by Bert.Twildge; September 9, 2011, 08:22 AM. Reason: Long file name comments missed out
Comment
-
If you are not using the AIML BOT feature, you can disable it by editing the config file.
Config/hspi_im.ini
[Settings]
AimlBotEnable=False
If you are using the AIML BOT, I need some time to find this weird bug. It's occuring in a third party DLL, and I'm not sure if I can work around this bug.--
stipus
Comment
-
Hi Stipus
Thanks for your reply.
I'm not using the AIML Bot feature, I'd just like to use MSN. I added the line you mentioned in hspi_im.ini but it doesn't seem to have taken any affect and I get the same error in HSLog. Do you think the IM Connector/AIMLBot can see the ini file to process its entries? The main section of my hspi_im.ini is shown below:
[Settings]
MsnNetwork=True
JabberNetwork=False
AimlBotEnable=False
Debug=False
DebugWait=0
[MSN Login]
User=zzzzzzz@live.co.uk
Password=*************
IncomingFileDirectory=C:\Shared_Files
;User=My_HomeSeer_MSN_Account
;Password=My_HomeSeer_MSN_Account_Password
[MSN Users]
yyyyyyyy@yyyyyyyy=ADMIN
xxxxxxxxx@xxxxxxxxxx=ADMIN
The HSLog after the file above was changed is show below after a clean boot:
09/09/2011 17:36:26 - Plug-In - Initializing Plug-in: IM Connector
09/09/2011 17:36:26 - Error - Error loading AIML settings: Unable to find the specified file.
09/09/2011 17:36:26 - IM Connector - LoadConfig() failed. Aborting
09/09/2011 17:36:26 - Error - Initializing interface: IM Connector->1
09/09/2011 17:36:26 - Plug-In - Finished initializing plug-in IM Connector
For reference the path entries in my settings.xml, which I have not modified, are shown below:
<item name="aimldirectory" value="data\aimlbot\aiml"/>
<item name="configdirectory" value="data\aimlbot\config_im_connector\"/>
Are there any other details I can provide that might assist?
Thanks
Comment
-
I found an updated version of the plugin post #7 of the following thread:
http://board.homeseer.com/showthread.php?t=144345
Try it. I don't remember when I added the AimlBotEnable setting.
Regards,
stipus--
stipus
Comment
-
Hi
Thanks for your message.
I updated the hspi_im.dll file from the zip file, rebooted the PC and the error has stopped. You were right, I needed an updated dll to take notice of the ini file change. Thanks for your help!
I also couldn't get the HSlog to appear in MSN before the change. I got other text back ok but not the log. This changes has fixed that too!
Thanks
Comment
-
IM Connector Not working on MSN
Hi,
My connector has stopped working on MSN.
I am running the following connector version: 4.86.2.4
It seems to go online/offline etc:
Code:02/10/2011 12:18:45 Device Control Device: IM Network MSN (_2) Value set to 4 02/10/2011 12:19:02 Device Control Device: IM Network MSN (_2) Value set to 2 02/10/2011 12:21:28 IM Debug IM Connector : Debug Mode activated. Waiting 0 secs... 02/10/2011 12:21:28 IM Debug Loaded MSN User liz@mccarthyuk.net - Access Level Users 02/10/2011 12:21:28 IM Debug Loaded MSN User masterbed@mccarthyuk.net - Access Level ADMIN 02/10/2011 12:21:28 IM Debug Loaded MSN User chris@mccarthyuk.net - Access Level Users 02/10/2011 12:21:28 IM Debug Loaded MSN User frank@mccarthyuk.net - Access Level Users 02/10/2011 12:21:28 IM Debug Loaded MSN User kieran@mccarthyuk.net - Access Level Users 02/10/2011 12:21:28 IM Debug Loaded MSN User darren@mccarthyuk.net - Access Level ADMIN 02/10/2011 12:21:28 IM Debug MSN settings loaded - User: homeauto@mccarthyuk.net 02/10/2011 12:21:28 IM Debug IM Connector : Found MSN IO device _2 - Name= MSN - Location= IM Network 02/10/2011 12:21:28 IM Debug IM Connector : MsnClient connecting to MSN server... 02/10/2011 12:21:31 IM Debug IM Connector : MsnClient Connected to MSN server 02/10/2011 12:21:38 IM Debug MsnClient Connection Closed event received 02/10/2011 12:21:43 IM Debug IM Connector : MsnClient Connected to MSN server
but in reality it never goes online.
Any ideas?
Comment
-
Hi
I really struggle to connect with IM/MSNfrom the IM connecotr now. Other PCs at home can connect to IM ok. If I turn on debug mode on the IM Connector the log is filled with these messages:
IM Debug MsnClient msnPingAnswer() event. Timeout=41
IM Debug MsnClient msnTimer Elapsed
IM Debug MsnClient msnPingAnswer() event. Timeout=47
IM Debug MsnClient msnTimer Elapsed
THe HS PC has access to the internet ok and there is no firewall on the PC either.
Any ideas? I've had a look in my router's log and there is nothing being blocked from the HS server.
Thanks
Comment
Comment