Faux Pas (Fox Paws) - now online, the newspaper-style comic strip featuring Randy the fox and...
Since Microsoft introduced Skype's cloud-based group chats which replaced the previous peer-to-peer group chats, you may sometimes find yourself in a situation where you are unable to send messages to those cloud-based group chats.
Typing in the command
/dumpmsnp will most likely return a line
Status: LoggedOut which indicates that your client is not actually connected to the servers responsible for handling the cloud-based group chats.
The source of the problem remains unknown but it appears to be limited to the cloud server that your Skype client is configured to use. Luckily, this can be changed.
Identify Skype configuration file
Locate the configuration file for the Skype account you are having trouble with. It should be located at
Check MSNP home server
The MSNP home server your client uses can be found in the
<MSNPCore> <HomeServer>BAYMSGR2013521.gateway.messenger.live.com</HomeServer> <NewThreadAllowed>1</NewThreadAllowed> <P2PMigrationAllowed>0</P2PMigrationAllowed> <ProtocolToUse>24</ProtocolToUse> </MSNPCore>
You can test this HomeServer's host name with the traceroute command (e.g.
traceroute BAYMSGR2013521.gateway.messenger.live.com) which might provide some insights why your client has issues connecting to it.
Maybe you didn't use your account in quite a while (e.g. due to prolonged vacation) and the server simply ceased to exist.
Switch to a different MSNP home server
Although it is clearly an issue with the Skype client that it doesn't appear to have reliable fallback mechanisms for broken cloud servers, the solution is just a few keystrokes away:
config.xmland save the file.
config.xmlfile again. The
<HomeServer>tags should have been updated with a new cloud server host name.
traceroutecheck with the new cloud server host name which will hopefully not indicate any problems.
As an alternative, just stop using Skype already, switch to Slack and start being productive. ;)