[Rtcomm] [Rtcomm] [Bug 3626] incoming call to my gizmo5 account now fails
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Mon Aug 25 15:10:09 EEST 2008
- Previous message: [Rtcomm] [Bug 3626] incoming call to my gizmo5 account now fails
- Next message: [Rtcomm] [Bug 3626] incoming call to my gizmo5 account now fails
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=3626 ------- Comment #4 from mikhail.zabaluev at nokia.com 2008-08-25 15:10 GMT+3 ------- (In reply to comment #2) > Could you also provide a syslog? > To do so, start a terminal window. Now export TPORT_LOG=1 and export > SOFIASIP_DEBUG=all in the environment (e.g. by editing > /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Launch > /usr/lib/telepathy/telepathy-sofiasip standalone from the terminal. Now SIP > traffic logs get dumped into syslog. There is some confusion in these guidelines. These environment variables will cause output to syslog as well as to process' stderr descriptor. Launching the process in a terminal will give you that output on the terminal. Doing this way, it also helps to set SOFIASIP_PERSIST=1 environment variable to prevent telepathy-sofiasip from exiting due to no connections being requested: SOFIASIP_PERSIST=1 run-standalone.sh /usr/lib/telepathy/telepathy-sofiasip -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=3626 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
- Previous message: [Rtcomm] [Bug 3626] incoming call to my gizmo5 account now fails
- Next message: [Rtcomm] [Bug 3626] incoming call to my gizmo5 account now fails
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]