Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Jurijs Ivolga
Hi Aristedis, To use both servers simultaneously you need to have group id as 1 for both of them, because ds_select_dst("1", "4") will choose only servers from group what is in the first argument(in this case 1) and group 2 will never be used in your case. To make this work probably you need to l

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Daniel-Constantin Mierla
Hello, if you send first register to one asterisk and it replies 401, then the following up register has to be sent to same asterisk, otherwise the authentication fails if you send to 2nd asterisk and it doesn't recognize the nonce, no matter the user password is the same. Maybe asterisk has opti

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Aristeidis Tsitras
I experience something really strange when i change the dispatcher list to have the same priority both of the servers. I am getting 401 (unauthorised) to the extensions trying to register. Even though they in asterisk they seem to be registered, the debug shows 401. Not able to call from one extens

[SR-Users] Dialplan: using $avp("key") on subst rule with regexp capturing group

2020-07-21 Thread João Vitor Arruda
Hello, I'm trying to use the dialplan with $avp("key") on match_exp and subst_exp but i'm getting an error message when there is a regex capturing group on subst_exp to be used on repl_exp This is the config used: modparam("dialplan", "match_dynamic", 1) $avp(s:PSTNAC) = "0"; Dialplan e

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Jurijs Ivolga
Ah, I see the problem, just change list file in following way: 1 sip:192.168.0.100:5080 0 0 maxload=20 1 sip:192.168.0.101:5080 0 0 maxload=20 Jurijs On Tue, Jul 21, 2020 at 3:28 PM Jurijs Ivolga wrote: > Hi Aristedis, > > Sorry, indeed you have module parameters. > > When one asterisk is do

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Jurijs Ivolga
Hi Aristedis, Sorry, indeed you have module parameters. When one asterisk is down what you see when you run: kamcmd dispatcher.list Jurijs On Tue, Jul 21, 2020 at 3:19 PM Aristeidis Tsitras wrote: > i know that there is something wrong, but i can not figure it out. > Especially for the modp

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Aristeidis Tsitras
i know that there is something wrong, but i can not figure it out. Especially for the modparam settings that Mr Jurijs Ivolga is proposing, I already had them. it is the kamailio.cfg that I originally attached. Unfortunately I did not manage to find anything in the parameters that will solve the

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Arsen Semenov
Hi Aristeidis, David is right, first would be good to check the status of the destinations. In your configuration there are couple of things to have in mind: need to set correct flag param https://kamailio.org/docs/modules/5.5.x/modules/dispatcher.html#dispatcher.p.flags select the algorithm used

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Jurijs Ivolga
Hi Aristeidis, In your case Dispatcher module is misconfigured and it missing crutials parts like: modparam("dispatcher", "flags", 2) # without this flag no failover will happen, as you experiencing modparam("dispatcher", "xavp_dst", "_dsdst_") # this xavps will hold the list with addresses an

Re: [SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread David Villasmil
First thing is trying to get both servers status on opensips and make sure opensips sees them up: https://opensips.org/html/docs/modules/2.3.x/dispatcher.html#idp5739696 On Tue, 21 Jul 2020 at 12:12, Aristeidis Tsitras wrote: > I have a Kamailio and 2 asterisk servers. All users are created

[SR-Users] Dispatcher does not go to 2nd server

2020-07-21 Thread Aristeidis Tsitras
I have a Kamailio and 2 asterisk servers. All users are created in both of the asterisk servers. I am forwarding the registration to asterisk. The problem is that it is always used on only one server from the list. Even if one goes to shutdown, then there is not any registration sent to the availab