On 09/30/2010 05:09 PM, [email protected] wrote:
> Trying to make a call between two qutecom instances (build version:
> /build/buildd/qutecom-2.2~rc3.hg396~dfsg1, ie. the one that comes with
> the intrepid ubuntu deb packages -- thanks Ludovico!), I noticed the
> following messages passing by:
I have updated the qutecom packages in my ppa [1] for jaunty, karmic and
lucid, if you want to try with a more recent snapshot. Sorry, building
for intrepid is no longer supported, as it is too old.
> Although both instances have enabled call encryption, the crypto setup
> fails (and no padlock is shown). Any ideas how to enable more
> debugging output, or where to look for clues about this failure?
More logging can be obtained by setting environment variable
OWLOGGER_DEFAULT=debug.
E.g. start qutecom with
OWLOGGER_DEFAULT=debug qutecom
Unfortunately I am not able to help with your specific issue...
HTH,
Ludovico
[1] https://launchpad.net/~cavedon/+archive/qutecom/
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
