Max Gregorian wrote:
Which is the actual domain name that the server is supposed to be responsible for? *sipserver.mobilia.it http://sipserver.mobilia.it* or just *mobilia.it http://mobilia.it* or both?
I think just mobilia.it..
but that's something I haven't been able to understand completely.
sipserver.mobilia.it http://sipserver.mobilia.it seems to be fine:
Domain Type Class TTL Answer sipserver.mobilia.it http://sipserver.mobilia.it. A IN 86400 89.202.252.16 http://www.dnsstuff.com/tools/whois.ch?ip=89.202.252.16 mobilia.it http://mobilia.it. NS IN 86400 dns2.nic.it http://dns2.nic.it. mobilia.it http://mobilia.it. NS IN 86400 sipserver.mobilia.it http://sipserver.mobilia.it. mobilia.it http://mobilia.it. NS IN 86400 ns.mobilia.it http://ns.mobilia.it. ns.mobilia.it http://ns.mobilia.it. A IN 86400 151.17.2.2 http://151.17.2.2
Right now, I'd like it to listen for all of mobilia.it (and I'd be ecstatic)..
Multiple domains will be coming later.
Are you after a /multi-domain/ setup? As I understand it the domain module (if that is what your are using) is meant to be good for multi-domain setups, but have you considered keeping it simple and testing with a simple setup initially?
Just do:
*listen=udp:89.202.252.16:5060 http://89.202.252.16:5060 # IP address of Server # listen=udp:sipserver.mobilia.it:5060 http://sipserver.mobilia.it:5060 # Domain of server #
I think you will need these, regardless of whether you are using the domain module or not. And then I just use:
Holy cow, you can have multiple listen lines!!!
You learn something new every day (it seems I am recently).
*if (!uri==myself) {* *}*
It certainly works for me, even in a multi-domain setup with multiple public IPs, if not a little unwieldy.
Cool.
Thanks.
On 11/3/06, *nick* <nick@mobilia.it mailto:nick@mobilia.it> wrote:
I'm trying to get my machine ready to work externally, with public Ip addresses. I believe I've got all the pieces ready for the domain. I have the PTR records published for my server's public IP address. I have the .sip_.udp.mobilia.it. 0 0 5060 sipserver.mobilia.it <http://sipserver.mobilia.it>. record (I tried it with and without the .mobilia.it added to the udp) published, I tell the server to listen on the IP addresses which maps it's name in DNS, I have a line after listen : alias="mobilia.it <http://mobilia.it>" (I've tried both FQDN and this) I've exported the domain both as the command export SIP_DOMAIN="mobilia.it <http://mobilia.it>" and in the openserctlrc (does it need to be the FQDN or just the domain, again, neither seem to make a difference..) however, I still can't get the machine to believe that it is actually responsible for this domain. When I register I have errors along this line: (it registers, obviously, but the logic is wrong, since he thinks the user is coming from another domain). grep_sock_info - checking if host==us: 10==13 && [ mobilia.it <http://mobilia.it>] == [89.202.252.16 <http://89.202.252.16>] Nov 3 10:13:34 sipserver /usr/local/sbin/openser[3193]: grep_sock_info - checking if port 5060 matches port 5060 Nov 3 10:13:34 sipserver /usr/local/sbin/openser[3193]: grep_sock_info - checking if host==us: 10==13 && [mobilia.it <http://mobilia.it>] == [89.202.252.16 <http://89.202.252.16>] Nov 3 10:13:34 sipserver /usr/local/sbin/openser[3193]: grep_sock_info - checking if port 5060 matches port 5060 Can anyone venture a guess as to what I might be missing??? _______________________________________________ Users mailing list Users@openser.org <mailto:Users@openser.org> http://openser.org/cgi-bin/mailman/listinfo/users