Hi Juha,
Below are LCR tables input data
Lcr_gw table :
(id, lcr_id, gw_name, ip_addr, hostname, port, params, uri_scheme,
transport, strip, prefix, tag, flags, defunct)
1, 1, 'gw1', '192.168.26.4', '192.168.26.4', 5060, '', 1,
1, 0, null,null,
1,null
2, 1, 'gw2', '192.168.26.1', '192.168.26.1', 5060, '', 1,
1, 0, null,null,
1,null
3, 1, 'gw3', '192.168.26.6', '192.168.26.6', 5060, '', 1,
1, 0, null,null,
1,null
LCR_rule target:
(id,lcr_id, prefix,from_uri,request_uri, stopper, enabled)
1, 1, '961', null,null, 1, 1
LCR_rule_target table :
(id,lcr_id ,rule_id,gw_id,priority,weight)
1, 1, 1, 1, 1, 1
2, 1, 1, 2, 2, 2
3, 1, 1, 3, 3, 3
Thanks
Ali
-----Original Message-----
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Juha Heinanen
Sent: Monday, June 01, 2015 11:32 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Kamailio LCR Multiple choices
Ali Taher writes:
Yes I know , I gave 192.168.26.4 smaller priority ,
then 192.168.26.1
then 192.168.26.6.
So in this way gateways must be ordered as 192.168.26.4 , 192.168.26.1
, 192.168.26.6.
Yet I got them ordered as 192.168.26.6, 192.168.26.4 , 192.168.26.1 ,
192.168.26.6.
If as you're saying it's sorting issue , then why I got 192.168.26.6
gateway twice (at the first and at the end).
as i mentioned, it is not possible to say anything based on the above
information. you need to check your lcr tables, especially lcr_rule_target
table.
-- juha
_______________________________________________
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