26 Aug
2010
26 Aug
'10
4:23 p.m.
Hello,
I have a question about the "priority" in the dispatcher module. I looked
in the docu-wiki and there was nothing which actually described how this
field is used (exactly), so I can only guess or ask the list.
Say I have 3 destinations in a set:
set: 1
dest: sip:1.2.3.4:5060
priority: 1
set: 1
dest: sip:1.2.3.5:5060
priority: 1
set: 1
dest: sip:1.2.3.6:5060
priority: 0
I am using ds_select_domain("1","4") to retrieve my list of
destinations.
In this scenario, would the calls only route to 1.2.3.6 if .4 and .5 were
both out of service?
Thanks.
26 Aug
26 Aug
5:06 p.m.
Hello,
On 8/26/10 3:23 PM, Geoffrey Mina wrote:
Hello,
I have a question about the "priority" in the dispatcher module. I
looked in the docu-wiki and there was nothing which actually described
how this field is used (exactly), so I can only guess or ask the list.
the priority is used to sort the records in memory. IIRC, the highest
priority the first in the list (for same priority should be the order
returned by database query result).
If you use round-robin, the the first destination used is the one with
highest priority, the next, ... and loop again.
The priority is particularly good for classic serial forking (algorithm
9), where always first destination is the highest priority.
Cheers,
Daniel
Say I have 3 destinations in a set:
set: 1
dest: sip:1.2.3.4:5060 <http://1.2.3.4:5060>
priority: 1
set: 1
dest: sip:1.2.3.5:5060 <http://1.2.3.5:5060>
priority: 1
set: 1
dest: sip:1.2.3.6:5060 <http://1.2.3.6:5060>
priority: 0
I am using ds_select_domain("1","4") to retrieve my list of
destinations.
In this scenario, would the calls only route to 1.2.3.6 if .4 and .5
were both out of service?
Thanks.
_______________________________________________
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://www.asipto.com/
5:47 p.m.
OK, so In my scenario this wouldn't achieve what I am looking for. I
basically want 2 servers to get all the round-robin requests unless
they are unavailable. Then I would want the lower proiority servers
brought into the mix.
Maybe ill take a look at the source to see how tough this would be.
Thanks.
On 8/26/10, Geoffrey Mina <geoffreymina(a)gmail.com> wrote:
Hello,
I have a question about the "priority" in the dispatcher module. I looked
in the docu-wiki and there was nothing which actually described how this
field is used (exactly), so I can only guess or ask the list.
Say I have 3 destinations in a set:
set: 1
dest: sip:1.2.3.4:5060
priority: 1
set: 1
dest: sip:1.2.3.5:5060
priority: 1
set: 1
dest: sip:1.2.3.6:5060
priority: 0
I am using ds_select_domain("1","4") to retrieve my list of
destinations.
In this scenario, would the calls only route to 1.2.3.6 if .4 and .5 were
both out of service?
Thanks.
--
Sent from my mobile device
6:13 p.m.
You can just do this yourself with script arrays and custom database
queries. Easily. Why is everyone so hung up on trying to squeeze
logic functionality from modules that isn't there?
On 08/26/2010 10:47 AM, Geoffrey Mina wrote:
OK, so In my scenario this wouldn't achieve what I
am looking for. I
basically want 2 servers to get all the round-robin requests unless
they are unavailable. Then I would want the lower proiority servers
brought into the mix.
Maybe ill take a look at the source to see how tough this would be.
Thanks.
On 8/26/10, Geoffrey Mina<geoffreymina(a)gmail.com> wrote:
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Hello,
I have a question about the "priority" in the dispatcher module. I looked
in the docu-wiki and there was nothing which actually described how this
field is used (exactly), so I can only guess or ask the list.
Say I have 3 destinations in a set:
set: 1
dest: sip:1.2.3.4:5060
priority: 1
set: 1
dest: sip:1.2.3.5:5060
priority: 1
set: 1
dest: sip:1.2.3.6:5060
priority: 0
I am using ds_select_domain("1","4") to retrieve my list of
destinations.
In this scenario, would the calls only route to 1.2.3.6 if .4 and .5 were
both out of service?
Thanks.
7:17 p.m.
On 8/26/10 4:47 PM, Geoffrey Mina wrote:
OK, so In my scenario this wouldn't achieve what I
am looking for. I
basically want 2 servers to get all the round-robin requests unless
they are unavailable. Then I would want the lower proiority servers
brought into the mix.
Maybe ill take a look at the source to see how tough this would be.
you can do that. It is up to your logic in config -- use as may setids
as you need in cascade. E.g., just build the logic so that if all routes
in dispatcher setid X fails then use routes from setid Y.
Cheers,
Daniel
Thanks.
On 8/26/10, Geoffrey Mina<geoffreymina(a)gmail.com> wrote:
> Hello,
> I have a question about the "priority" in the dispatcher module. I looked
> in the docu-wiki and there was nothing which actually described how this
> field is used (exactly), so I can only guess or ask the list.
>
> Say I have 3 destinations in a set:
>
> set: 1
> dest: sip:1.2.3.4:5060
> priority: 1
>
> set: 1
> dest: sip:1.2.3.5:5060
> priority: 1
>
> set: 1
> dest: sip:1.2.3.6:5060
> priority: 0
>
>
> I am using ds_select_domain("1","4") to retrieve my list of
destinations.
>
> In this scenario, would the calls only route to 1.2.3.6 if .4 and .5 were
> both out of service?
>
> Thanks.
>
--
Daniel-Constantin Mierla
http://www.asipto.com/
5202
days inactive
5202
days old
4 comments
3 participants
participants (3)
-
Alex Balashov -
Daniel-Constantin Mierla -
Geoffrey Mina