After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337775 - "Error while starting the listener for the SIP protocol"
"Error while starting the listener for the SIP protocol"
Status: RESOLVED INCOMPLETE
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: Normal minor
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-09 08:05 UTC by Mario Vukelic
Modified: 2006-04-20 14:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Mario Vukelic 2006-04-09 08:05:39 UTC 
Please describe the problem:
When I start Ekiga, I sometimes get the message:

"Title: Error while starting the listener for the SIP protocol
You will not be able to recieve incoming SIP calls. Please check that no other
program is already running on the port used by Ekiga"

At times I get only this, and at others, afterwards the same for H.323.

Sometimes after I get the message the login to ekiga.net failed as per the
status bar message, but at other times the login works nevertheless.

If Ekiga is started with the session, I seem to get it everytime, otherwise only
sporadically.

Ekiga 2.0.1-0ubuntu3 on Dapper.

Steps to reproduce:
1. Start Ekiga, run in the notification area
2. Save session and logout
3. Login

Maybe have to try a few times to trigger it


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Mario Vukelic 2006-04-09 08:06:25 UTC 
Grrr, forgot: this is also reported as https://launchpad.net/distros/ubuntu/+source/ekiga/+bug/37406
Comment 2 Snark 2006-04-09 08:14:43 UTC 
Hmmmm... if ekiga is running and you logout, then it may not shut down properly. Hence the SIP and/or H.323 port will still be busy, until some timeout.

Until the port is free, ekiga won't be able to bind to it, and hence the error message.

Try to shut ekiga down properly before logout.
Comment 3 Snark 2006-04-20 14:31:45 UTC 
I close it as INCOMPLETE, since the report doesn't really make it clear it's really a bug in ekiga, as explained in my previous comment.