Bug#325456: centericq: Cannot connect to AIM

2005-12-22 Thread Andy Stanford
On Thu, Dec 22, 2005 at 04:47:49PM +0100, Julien Lemoine wrote:
> Hello Andy,
> 
>I think you have done a confusion between icq and aim since gaim 
> chose automaticaly the good
> protocol associed with name. Can you try to connect to your account with 
> icq protocol instead of aim
> protocol in centericq ?
>
I'm unable to do this since the icq account section of centericq will not allow
a name as a UIN. Unless there is an alternative way of forcing centericq to use
a particular protocol?

The server address I listed in my previous email is the server that gaim uses
to connect to the aim network. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#325456: centericq: Cannot connect to AIM

2005-12-15 Thread Andy Stanford
Package: centericq
Version: 4.21.0-6.0etch1
Followup-For: Bug #325456

For some time (since approx Aug 23), I have been unable to connect to AIM with 
centericq. I've tested
other clients with on the same machine which have connected fine, to eliminate
any network problems.

I have also performed a fresh install of the centericq packages, after making
backups of my previously working configuration.

The error message I obtain when attempting to connect is:

"aim connection failed: Connection failed, Connection timed out"

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.8-2-386
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages centericq depends on:
ii  centericq-common 4.21.0-6.0etch1 A text-mode multi-protocol instant
ii  libc62.3.5-8 GNU C Library: Shared libraries an
ii  libcomerr2   1.38-2  common error description library
ii  libcurl3 7.15.0-4Multi-protocol file transfer libra
ii  libgcc1  1:4.0.2-5   GCC support library
ii  libgnutls11  1.0.16-14   GNU TLS library - runtime library
ii  libgpg-error01.1-4   library for common error values an
ii  libgpgme11   1.1.0-1 GPGME - GnuPG Made Easy
ii  libidn11 0.5.18-1GNU libidn library, implementation
ii  libjpeg626b-10   The Independent JPEG Group's JPEG 
ii  libkrb53 1.3.6-5 MIT Kerberos runtime libraries
ii  libncurses5  5.5-1   Shared libraries for terminal hand
ii  libssl0.9.8  0.9.8a-3SSL shared libraries
ii  libstdc++6   4.0.2-5 The GNU Standard C++ Library v3
ii  zlib1g   1:1.2.3-8   compression library - runtime

Versions of packages centericq recommends:
ii  lynx [www-browser] 2.8.5-2sarge1 Text-mode WWW Browser
pn  sox(no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#325456: centericq: Cannot connect to AIM

2005-12-18 Thread Andy Stanford
On Sat, Dec 17, 2005 at 10:19:35AM +0100, Julien Lemoine wrote:
> Hello Andy,
> 
>Maybe centericq is not using the correct server name for you, can 
> you tcpdump centericq and
> other clients to see if there are using the same network address ?
>I am not using AIM and I only found this thread on mailing list 
> where one user seems to have the same problem as you and other users are 
> able to use aim with centericq :
> http://article.gmane.org/gmane.network.centericq/3859
> 
I've checked the network settings, and it would appear that the defaults for
centericq's aim connections are out of date, which should probably be opened as
a separate bug. the correct settings should be login.oscar.aol.com:5190.

Having changed this, I no longer get the error listed below, and in fact,
nothing is added to the centericq log to even indicate a connection.
In the status window within centericq I now get:

[aim] connecting to the server
[aim] password sent
[aim] disconnected

I have confirmed that the other clients are able to connect on the same network
address.

> Best Regards.
> Julien Lemoine
> 
> Andy Stanford wrote:
> 
> >Package: centericq
> >Version: 4.21.0-6.0etch1
> >Followup-For: Bug #325456
> >
> >For some time (since approx Aug 23), I have been unable to connect to AIM 
> >with centericq. I've tested
> >other clients with on the same machine which have connected fine, to 
> >eliminate
> >any network problems.
> >
> >I have also performed a fresh install of the centericq packages, after 
> >making
> >backups of my previously working configuration.
> >
> >The error message I obtain when attempting to connect is:
> >
> >"aim connection failed: Connection failed, Connection timed out"
> >
> >-- System Information:
> >Debian Release: testing/unstable
> > APT prefers testing
> > APT policy: (500, 'testing'), (500, 'stable')
> >Architecture: i386 (i686)
> >Shell:  /bin/sh linked to /bin/dash
> >Kernel: Linux 2.6.8-2-386
> >Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
> >
> >Versions of packages centericq depends on:
> >ii  centericq-common 4.21.0-6.0etch1 A text-mode multi-protocol 
> >instant
> >ii  libc62.3.5-8 GNU C Library: Shared 
> >libraries an
> >ii  libcomerr2   1.38-2  common error description 
> >library
> >ii  libcurl3 7.15.0-4Multi-protocol file transfer 
> >libra
> >ii  libgcc1  1:4.0.2-5   GCC support library
> >ii  libgnutls11  1.0.16-14   GNU TLS library - runtime 
> >library
> >ii  libgpg-error01.1-4   library for common error 
> >values an
> >ii  libgpgme11   1.1.0-1 GPGME - GnuPG Made Easy
> >ii  libidn11 0.5.18-1GNU libidn library, 
> >implementation
> >ii  libjpeg626b-10   The Independent JPEG Group's 
> >JPEG ii  libkrb53 1.3.6-5 MIT Kerberos runtime 
> >libraries
> >ii  libncurses5  5.5-1   Shared libraries for terminal 
> >hand
> >ii  libssl0.9.8  0.9.8a-3SSL shared libraries
> >ii  libstdc++6   4.0.2-5 The GNU Standard C++ Library 
> >v3
> >ii  zlib1g   1:1.2.3-8   compression library - runtime
> >
> >Versions of packages centericq recommends:
> >ii  lynx [www-browser] 2.8.5-2sarge1 Text-mode WWW Browser
> >pn  sox(no description available)
> >
> >-- no debconf information
> >
> > 
> >


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]