Hello,

"kamctl dispatcher dump" should not require anymore a db engine -- what is the version of kamailio you are using?

Anyhow, you can do the raw mi command like:

kamctl mi ds_list

To reload is:

kamct mi ds_reload

Cheers, Daniel

On 18/04/16 13:04, Sébastien Brice wrote:

Hi Marrold,

kamctl dispatcher dump ERROR: This command requires a database engine - none was loaded I thought i could run dispatcher module without database, it appears my strange behavior comes from this: i do not use a database.

Instead I am usinq a flat dispatcher.list file: # Autogenerated @ Monday, April 18th 2016, 10:41:58 am 1 sip:172.16.0.203:5060 0 0 weight=50 1 sip:172.16.0.202:5060 0 0 weight=50

about the traffic generated toward asterisk boxes:

tshark -w capture1 -f "port 5060" -i eth0 -P ………… nothing get captured ………… …………

What else should i attempt ?

Thanks.

----- Mail original ----- De: "Marrold" kamailio@marrold.co.uk À: "Sébastien Brice" sebastien.brice@jvs.fr, "sr-users" sr-users@lists.sip-router.org Envoyé: Lundi 18 Avril 2016 01:16:05 Objet: Re: [SR-Users] DISPATCHER module No destinations availables even if my Asterisk Boxes are up and running

First of all I would check the result of -

# kamctl dispatcher dump

SET:: 4001 URI:: sip:10.0.97.17:5060 flags=IP priority=1 attrs=backend=be011 URI:: sip:10.0.97.18:5060 flags=IP priority=1 attrs=backend=be011 SET:: 4002 URI:: sip:10.0.97.21:5060 flags=AP priority=1 attrs=backend=be021

AP = Active, Probing IP = Inactive, Probing

I'd also run a SIP trace on the Asterisk boxes to check if they are receiving / responding to the OPTIONS pings.

On Sun, Apr 17, 2016 at 9:29 PM, Sébastien Brice sebastien.brice@jvs.fr wrote:

...

Hello everyone. I'm using kamailio as a dispatcher in front of asterisk boxes and i use a failure route if asterisk box does not respond or send 503 error (please look at my attached kamailio.cfg)

I use "ds_probing_mode", 1 and "ds_ping_reply_codes", "class=2;class=3;class=4" to OPTIONS ping the two asterisk instances but they do appear down both all the time.

That is very annoying none of the INVITE go through Asterisk, they all are stopped because of my failure_route that sets no destination available

ERROR: <script>: Destination down: INVITE sip:9980048587420715@XXX.XXX.XXX.XX (sip:ipofAsterisk1:5060) ERROR: <script>: Destination down: INVITE sip:9980048587420715@YY.YY.YYY.YY (sip:ipofAsterisk1:5060) ERROR: <script>: Destination down: INVITE sip:000442030044700@XXX.XX.X.XXX (sip:ipofAsterisk2:5060) ERROR: <script>: Destination down: INVITE sip:000442030044700@YY.YYY.YY.YYY (sip:ipofAsterisk2:5060) NOTICE: <script>: Media server sip:172.16.0.202:5060 failed to answer, selecting other one! NOTICE: <script>: No destination, sent 404

I don't know what's wrong with my setup, could someone give an eye to my kamailio.cfg and head me on the right track ? Thanks a lot.

Seb

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Run with debug =3 in kamailio.cfg and look at the syslog file to see if you spot anything that could give hints about what happens around. If you are getting too many messages and feel it is hard to analyze them, you can load debugger module and set debug level to 3 only for dispatcher module.

Cheers, Daniel

On 18/04/16 14:27, Sébastien Brice wrote:

Thx you Daniel, actually i am running kamailio 4.1.7

[root@af173cb12922 /]# kamailio -v version: kamailio 4.1.7 (x86_64/linux) 85ffd9

But Marrold was right it appears Kamailio does not probe correctly my asterisk boxes :-(

[root@af173cb12922 /]# kamctl mi ds_list SET_NO:: 1 SET:: 1 URI:: sip:172.16.0.202:5060 flags=IP priority=0 attrs=weight=50 URI:: sip:172.16.0.203:5060 flags=IP priority=0 attrs=weight=50

No ACTIVE gateway has been elected, i don't know what's wrong here.

----- Mail original ----- De: "Daniel-Constantin Mierla" miconda@gmail.com À: "Sébastien Brice" sebastien.brice@jvs.fr, "sr-users" sr-users@lists.sip-router.org, "Marrold" kamailio@marrold.co.uk Envoyé: Lundi 18 Avril 2016 14:07:00 Objet: Re: [SR-Users] DISPATCHER module No destinations availables even if my Asterisk Boxes are up and running

Hello,

"kamctl dispatcher dump" should not require anymore a db engine -- what is the version of kamailio you are using?

Anyhow, you can do the raw mi command like:

kamctl mi ds_list

To reload is:

kamct mi ds_reload

Cheers, Daniel

On 18/04/16 13:04, Sébastien Brice wrote:

...

Hi Marrold,

kamctl dispatcher dump ERROR: This command requires a database engine - none was loaded I thought i could run dispatcher module without database, it appears my strange behavior comes from this: i do not use a database.

Instead I am usinq a flat dispatcher.list file: # Autogenerated @ Monday, April 18th 2016, 10:41:58 am 1 sip:172.16.0.203:5060 0 0 weight=50 1 sip:172.16.0.202:5060 0 0 weight=50

about the traffic generated toward asterisk boxes:

tshark -w capture1 -f "port 5060" -i eth0 -P ………… nothing get captured ………… …………

What else should i attempt ?

Thanks.

----- Mail original ----- De: "Marrold" kamailio@marrold.co.uk À: "Sébastien Brice" sebastien.brice@jvs.fr, "sr-users" sr-users@lists.sip-router.org Envoyé: Lundi 18 Avril 2016 01:16:05 Objet: Re: [SR-Users] DISPATCHER module No destinations availables even if my Asterisk Boxes are up and running

First of all I would check the result of -

# kamctl dispatcher dump

SET:: 4001 URI:: sip:10.0.97.17:5060 flags=IP priority=1 attrs=backend=be011 URI:: sip:10.0.97.18:5060 flags=IP priority=1 attrs=backend=be011 SET:: 4002 URI:: sip:10.0.97.21:5060 flags=AP priority=1 attrs=backend=be021

AP = Active, Probing IP = Inactive, Probing

I'd also run a SIP trace on the Asterisk boxes to check if they are receiving / responding to the OPTIONS pings.

On Sun, Apr 17, 2016 at 9:29 PM, Sébastien Brice sebastien.brice@jvs.fr wrote:

...

Hello everyone. I'm using kamailio as a dispatcher in front of asterisk boxes and i use a failure route if asterisk box does not respond or send 503 error (please look at my attached kamailio.cfg)

I use "ds_probing_mode", 1 and "ds_ping_reply_codes", "class=2;class=3;class=4" to OPTIONS ping the two asterisk instances but they do appear down both all the time.

That is very annoying none of the INVITE go through Asterisk, they all are stopped because of my failure_route that sets no destination available

ERROR: <script>: Destination down: INVITE sip:9980048587420715@XXX.XXX.XXX.XX (sip:ipofAsterisk1:5060) ERROR: <script>: Destination down: INVITE sip:9980048587420715@YY.YY.YYY.YY (sip:ipofAsterisk1:5060) ERROR: <script>: Destination down: INVITE sip:000442030044700@XXX.XX.X.XXX (sip:ipofAsterisk2:5060) ERROR: <script>: Destination down: INVITE sip:000442030044700@YY.YYY.YY.YYY (sip:ipofAsterisk2:5060) NOTICE: <script>: Media server sip:172.16.0.202:5060 failed to answer, selecting other one! NOTICE: <script>: No destination, sent 404

I don't know what's wrong with my setup, could someone give an eye to my kamailio.cfg and head me on the right track ? Thanks a lot.

Seb

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users