Please describe the problem:
Ekiga has problems making SIP and H.323 if a network connection (such as NetworkManager handles) is created _after_ Ekiga starts up. In other words, Ekiga cannot recognize any network interfaces brought up after its own initialization.

Steps to reproduce:
1. Disable your network connections
2. Start Ekiga
3. Close the SIP and H.323 error messages that appear
4. Enable a network connection
5. Attempt to connect to your ekiga.net or other similar account

Actual results:
When my computer first starts up, Ekiga launches automatically before NetworkManager has established a network connection. Because of this, I receive this message:
"Error while starting the listener for the SIP protocol
"You will not be able to receive incoming SIP calls. Please check that no other program is already running on the port used by Ekiga."
and another one almost identical but referring to H.323.
Once I have entered my password into NetworkManager's keyring request and it succeeds in establishing a network connection, Ekiga continues to fail connecting to my ekiga.net account. It can be seen in the network preferences that the list of network interfaces to listen on is still empty. Quitting and restarting Ekiga causes the new interface to be recognize and a connection to be established.

Expected results:
I would expect Ekiga to be notified of any interfaces brought up, or for Ekiga to rescan for available interfaces on its own. It is reasonable to see errors before I've brought my network interface up, but not after.

Does this happen every time?
Yes

Other information:
Something to think about long-term would be coordinating between Ekiga and NetworkManager to allow Ekiga to see that a connection is in process of being established, and then wait before trying to create a SIP or H.323 connection. But I know that's much more involved!

Thanks!