8 Dec
2015
8 Dec
'15
2:54 a.m.
Hello Everyone,
Looking for some design suggestion.
I am trying achieve routing based on domain.tld. I thought use drouting, but not sure if
it suitable for this task.
Example:
Kamailio Server 1
|
|__________________ PBX Group 1 domain1.tld
|
|____ PBX Server 1
|
|____PBX Server 2
|__________________ PBX Group 2 domain2.tld
|
|____ PBX Server 1
|
|____PBX Server 2
and so on.
Slava.
9 Dec
9 Dec
10:02 a.m.
Hello,
drouting or other least cost routing modules typically choose the
destination based on prefix matching.
In this case you need matching on domain, which I would do it with a
combination of htable+dispatcher.
In htable (stored in database as well), I will keep items (domain, setid).
In dispatcher will be: setid and the associated PBX addresses.
First retrieve the setid by looking up domain in hash table, then with
the retrieved setid value, use ds_select_dst(setid, ...).
Cheers,
Daniel
On 08/12/15 01:54, Slava Bendersky wrote:
Hello Everyone,
Looking for some design suggestion.
I am trying achieve routing based on domain.tld. I thought use
drouting, but not sure if it suitable for this task.
Example:
Kamailio Server 1
|
|__________________ PBX Group 1
domain1.tld
|
|____ PBX Server 1
|
|____PBX Server 2
|__________________ PBX Group
2 domain2.tld
|
|____ PBX Server 1
|
|____PBX Server 2
and so on.
Slava.
_______________________________________________
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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
3301
days inactive
3302
days old
1 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Slava Bendersky