Please describe the problem:
The Edit -> Accounts -> Add menu does not allow SIP accounts to be configured in
all ways seen in the wild.
First of all let me explain how things could work:

A) The DNS based approach

If an ISP offers SIP it's supposed to add a DNS SRV record to its domain which
points to the SIP server/registrar, i.e.
  $ dig _sip._udp.freenet.de srv +short
  0 0 5060 iphone.freenet.de.
  $

for the UDP SIP server for freenet.de. The DNS response might already yield an
IP for iphone.freenet. If not the client is supposed to do an A record lookup
and eventually gains a port (5060 in this case) and an IP to connect to.

On the GUI setup side all you have to fill in is a 'SIP domain' and the client
could then try to lookup information.

B) manual approach

You could enter a SIP domain/REGISTRAR plus an outbound proxy. The SIP
domain/REGISTRAR should be used for authentication and usernames whereas the
outbound proxy should not appear within signaling. It's only your outbound proxy.

So what's wrong with Ekiga?

First the SIP outbound proxy setting is not on a per-account basis which it
should be.
Secondly Ekiga does an A DNS lookup to determine the SIP server IP address.
For freenet.de (and many other ISPs!) this fails since the A record is usually
the IP the webserver is running on but not necessarily the SIP server.

Steps to reproduce:
1. Set up an account within the freenet.de domain
2. use tcpdump or ngrep (ngrep -W byline port 5060) to watch SIP traffic
3. activate account and observe Ekiga connecting to 62.104.23.42 (which is
'freenet.de') but not 194.97.54.97 (as in 'iphone.freenet.de').
4. no SIP message is received on the SIP server side.


Actual results:
SIP messages don't make it to the SIP server/registrar

Expected results:
Proper DNS SRV lookup

Does this happen every time?
yes

Other information:
Feel free to contact me via ICQ (92246415) for more in-depth information.