Package conflates SIP domain and server hostname

[nwhitehorn]

The SIP client code uses the server as the domain for the SIP account, such that SIP ID user@example.com will try to send data to a server identified by the DNS A record example.com. There are a number of cases where this does not happen:

• If the server is supposed to be looked by SRV records instead of A record
• If the user is supposed to use some proxy server with a different hostname

It would be great if both SRV records would be supported and a proxy server host could be specified.

Also, thanks so much for writing this. The Python SIP situation was pretty dire and I am delighted to see the fast progress you have made here.

[tayler6000]

Thank you for your kind words @nwhitehorn, and for the issue. I planned on implementing proper hostname resolution with SRV records, but I had not created an issue for it yet.

Proxy support has come up repeatedly in issues. I personally test with Asterisk, which is a PBX/Registrar, and not a proxy. Do you know of any good SIP proxy software that I could write tests against? If not, perhaps a free online service? I'd like proxy support to be implemented in 2.0.0

[nwhitehorn]

We use kamailio, if it's helpful. Not always the easiest to configure, unfortunately.