Bug 314987 - account manager lock wrong 5223 talk.google.com port instead 5222
Summary: account manager lock wrong 5223 talk.google.com port instead 5222
Status: RESOLVED NOT A BUG
Alias: None
Product: telepathy
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.5.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-12 11:41 UTC by Pavel Nedrigailov
Modified: 2013-03-13 10:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Nedrigailov 2013-02-12 11:41:28 UTC 
Account manager choose port to connect to talk.google.com as 5223, but that port reports authenticacion error to correct password. Need to change connect port to 5222. With same password connect to talk.google.com establishes good.

Reproducible: Always
Comment 1 Martin Klapetek 2013-02-17 15:24:06 UTC 
Thanks for the report. I've checked the ports at Google help, there are both ports used.

In Google's Developer docs [1] it says 5222. In Google's support for setting up clients [2], they always use 5223. So I assume they are both correct. I myself am currently connected via 5223. 

I didn't find any relevant info about the difference between these ports. Might be just your firewall. Sorry.

[1] - https://developers.google.com/talk/open_communications#developer
[2] - http://support.google.com/talk/topic/1415?hl=en&ref_topic=12175
Comment 2 Pavel Nedrigailov 2013-03-12 10:31:34 UTC 
OK, after update to next version I'll check it.
Comment 3 Pavel Nedrigailov 2013-03-13 05:40:05 UTC 
Martin,
today I'm updated ktp to 0.5.3, remove and create google talk account, and all works fine!
Comment 4 Martin Klapetek 2013-03-13 10:49:46 UTC 
Glad to hear :)