7 Aug
2014
7 Aug
'14
9:23 p.m.
Hello. I try to integrate dispathcer module (with db table dispatcher) to
my Kamailio server.
I have problem with changing IP at db table, but when I calling - call goes
to old IP that alread deleted from db.
I tested my table with query that selects destination address from table,
and it replyes to me correct address.
I use round-robin ("4") algorythm
modparam("dispatcher", "db_url",DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "setid_col", "setid")
modparam("dispatcher", "destination_col", "destination")
modparam("dispatcher", "force_dst", 1)
modparam("dispatcher", "flags", 3)
modparam("dispatcher", "dst_avp", "$avp(i:271)")
modparam("dispatcher", "grp_avp", "$avp(i:272)")
modparam("dispatcher", "cnt_avp", "$avp(i:273)")
modparam("dispatcher", "ds_ping_from",
"sip:proxy@10.0.0.2")
modparam("dispatcher", "ds_ping_interval",15)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=404;code=484;class=3")
How to disable this cache?
7 Aug
7 Aug
9:47 p.m.
Hi,
After making changes to database, run "kamctl dispatcher reload" from
commandline.
Regards,
Kristian Høgh
On Friday 08 August 2014 01:23:43 Yuriy Gorlichenko wrote:
Hello. I try to integrate dispathcer module (with db
table dispatcher) to
my Kamailio server.
I have problem with changing IP at db table, but when I calling - call goes
to old IP that alread deleted from db.
I tested my table with query that selects destination address from table,
and it replyes to me correct address.
I use round-robin ("4") algorythm
modparam("dispatcher", "db_url",DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "setid_col", "setid")
modparam("dispatcher", "destination_col", "destination")
modparam("dispatcher", "force_dst", 1)
modparam("dispatcher", "flags", 3)
modparam("dispatcher", "dst_avp", "$avp(i:271)")
modparam("dispatcher", "grp_avp", "$avp(i:272)")
modparam("dispatcher", "cnt_avp", "$avp(i:273)")
modparam("dispatcher", "ds_ping_from",
"sip:proxy@10.0.0.2")
modparam("dispatcher", "ds_ping_interval",15)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=404;code=484;class=3")
How to disable this cache?
8 Aug
8 Aug
3:56 a.m.
Ок. I will rty it. What about realtime reading this table of dispatcher
nodule? Does iyt have any solutions without kamctl?
08.08.2014 1:47 пользователь "Kristian F. Høgh" <kfh(a)uni-tel.dk> написал:
Hi,
After making changes to database, run "kamctl dispatcher reload" from
commandline.
Regards,
Kristian Høgh
On Friday 08 August 2014 01:23:43 Yuriy Gorlichenko wrote:
> Hello. I try to integrate dispathcer module (with db table dispatcher)
to
> my Kamailio server.
>
> I have problem with changing IP at db table, but when I calling - call
goes
> to old IP that alread deleted from db.
>
> I tested my table with query that selects destination address from
table,
and it replyes
to me correct address.
I use round-robin ("4") algorythm
modparam("dispatcher", "db_url",DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "setid_col", "setid")
modparam("dispatcher", "destination_col", "destination")
modparam("dispatcher", "force_dst", 1)
modparam("dispatcher", "flags", 3)
modparam("dispatcher", "dst_avp", "$avp(i:271)")
modparam("dispatcher", "grp_avp", "$avp(i:272)")
modparam("dispatcher", "cnt_avp", "$avp(i:273)")
modparam("dispatcher", "ds_ping_from",
"sip:proxy@10.0.0.2")
modparam("dispatcher", "ds_ping_interval",15)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=404;code=484;class=3")
How to disable this cache?
_______________________________________________
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 
6:21 a.m.
There is no db-only for dispatcher, you have to do reload.
If you don't need keepalive mechanism, perhaps you can try loading the
addresses from database with sqlops and do the dispatching algorithm via
config file only.
Cheers,
Daniel
On 08/08/14 05:56, Yuriy Gorlichenko wrote:
Ок. I will rty it. What about realtime reading this table of
dispatcher nodule? Does iyt have any solutions without kamctl?
08.08.2014 1:47 пользователь "Kristian F. Høgh" <kfh(a)uni-tel.dk
<mailto:kfh@uni-tel.dk>> написал:
_______________________________________________
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
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany ::: Oct 15-17, San Francisco, USA
Hi,
After making changes to database, run "kamctl dispatcher reload"
from
commandline.
Regards,
Kristian Høgh
On Friday 08 August 2014 01:23:43 Yuriy Gorlichenko wrote:
> Hello. I try to integrate dispathcer module (with db table
dispatcher) to
> my Kamailio server.
>
> I have problem with changing IP at db table, but when I calling -
call goes
> to old IP that alread deleted from db.
>
> I tested my table with query that selects destination address from
table,
> and it replyes to me correct address.
>
> I use round-robin ("4") algorythm
>
> modparam("dispatcher", "db_url",DBURL)
> modparam("dispatcher", "table_name", "dispatcher")
> modparam("dispatcher", "setid_col", "setid")
> modparam("dispatcher", "destination_col",
"destination")
> modparam("dispatcher", "force_dst", 1)
> modparam("dispatcher", "flags", 3)
> modparam("dispatcher", "dst_avp", "$avp(i:271)")
> modparam("dispatcher", "grp_avp", "$avp(i:272)")
> modparam("dispatcher", "cnt_avp", "$avp(i:273)")
> modparam("dispatcher", "ds_ping_from", "sip:proxy@10.0.0.2
<mailto:sip%3Aproxy@10.0.0.2>")
modparam("dispatcher", "ds_ping_interval",15)
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_reply_codes",
"class=2;code=403;code=404;code=484;class=3")
How to disable this cache?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
4:39 p.m.
On Fri, Aug 8, 2014 at 2:21 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
There is no db-only for dispatcher, you have to do
reload.
If you don't need keepalive mechanism, perhaps you can try loading the
addresses from database with sqlops and do the dispatching algorithm via
config file only.
I wonder what would be needed to implement some sort of TTL for the
dispatcher cache. Do any of the other modules implement TTL in any
fashion for DB queries?
--
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger(a)polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger
11 Aug
11 Aug
7:34 a.m.
On 08/08/14 18:39, Paul Belanger wrote:
On Fri, Aug 8, 2014 at 2:21 AM, Daniel-Constantin
Mierla
<miconda(a)gmail.com> wrote:
That can be implemented with a timer callback to reload periodically
records from database. The function to reload is there and there are
many examples of adding timer callbacks in modules. So if anyone is
looking to add it in the module, should not be something comples.
Alternative, have a script run by cron.d executing kamctl dispatcher reload.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany ::: Oct 15-17, San Francisco, USA
There is no db-only for dispatcher, you have to
do reload.
If you don't need keepalive mechanism, perhaps you can try loading the
addresses from database with sqlops and do the dispatching algorithm via
config file only.
I wonder what would be needed to implement some sort of TTL for the
dispatcher cache. Do any of the other modules implement TTL in any
fashion for DB queries?
3627
days inactive
3631
days old
5 comments
4 participants
participants (4)
-
Daniel-Constantin Mierla -
Kristian F. Høgh -
Paul Belanger -
Yuriy Gorlichenko