9 Nov
2010
9 Nov
'10
1:04 a.m.
Hi,
I don't get any reply til yet, after i detailed the problem.
Was my problem description not clear enough, or you agree with me.
I need a confirmation that i am not wrong and this problem can't be
solved with the current multidomain implementation.
Alex, Jiri please state if you agree or disagree with me.
And if i am wrong, then please point out where i am wrong.
Many Thanks!
Misi
2010-11-05 18:19 keltezéssel, MÉSZÁROS Mihály írta:
2010-11-05 09:31 keltezéssel, Alex Balashov írta:
On 11/05/2010 04:10 AM, MÉSZÁROS Mihály wrote:
I will try to explain where i saw the problem.
Of course it can be that i am wrong, so AFAIK ..
If there is domain atlanta.test with with such a DNS.
$TTL 60
$ORIGIN atlanta.test.
@ IN SOA a1.atlanta.test. root.a1.atlanta.test. (
2009071301 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS a1
@ IN NS a2
a1 IN A 192.168.0.1
a2 IN A 192.168.0.2
;; order pref flags service
regexp replacement
@ IN NAPTR 10 10 "s" "SIPS+D2T"
"" _sips._tcp
@ IN NAPTR 20 10 "s" "SIP+D2T"
"" _sip._tcp
@ IN NAPTR 30 10 "s" "SIP+D2U"
"" _sip._udp
;; Priority Weight Port Target
_sips._tcp IN SRV 10 0 5061 a1
_sips._tcp IN SRV 20 0 5061 a2
_sip._tcp IN SRV 10 0 5060 a1
_sip._tcp IN SRV 20 0 5060 a2
_sip._udp IN SRV 10 0 5060 a1
_sip._udp IN SRV 20 0 5060 a2
* UA type1
It is implementing RFC3263 correctly. (Very rare such a good
implementation.)
so it will send a register
REGISTER atlanta.test
To:alice@atalnta.test
o Correctly this client will use the proxy preference and in
best case use tcp + tls.
* UA2
It is implementing only dns A record support.
so it will send a register
REGISTER a1.atlanta.test
To: alice(a)a1.atlanta.test
* UA3
It is a strange UA resolves everything to ip address.
so it will send the register
REGISTER 192.168.0.1
To: alice(a)192.168.0.1
* UA4
Maybe there are more case, and can be continued. But till now i
faced only to the above three cases.
Where i saw the problem with kamailio multidomain setup (AFAIK):
I want to use the three as one "sip routing domain" or i don't know
how to name it correctly.
When it saves the AoR <=> Contact bindings to location database
(mysql), the registrar will create and save the contacts to three
separated domain according to the above three UA behavior:
* atlanta.test
* a1.atlanta.test
* 192.168.0.1
So i must add three times the user in subscriber table for the three
domain, to allow the user alice to authenticate from any UA.
And i will have three domain in location database for only one "sip
routing domain".
So if i want to have a second domain, called biloxi.test with similar
setup, on the same host where atlanta.test is,
then i get bigger mess. And i have six domain...
I hope you see where i have a problem.
And AFAIK i can't set to registrar function save() the domain, if i
use database backend.
Highly appreciated if You can suggest a solution for this.
It will be nice if you, or anyone can suggest some solution to this
problem.
Many Thanks!
Cheers,
Misi
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello all!
Is there any known problem to run multiple kamailio/sip-router instance
in one host.
I need this to handle multidomain situation.
The multidomain what is built in is not satisfactory, because the UA-s
what are from varying vendors.
And some has strange or a very limited SIP implementation.
Some can only register ip address, some can use RFC3263, but some can
use only DNS A record. :(
Any answer, suggestion appreciated very well!
I still don't see why handling multiple domains in a single instance
would be a problem.