I am closing this one, in case if misfunctionality, open a new issue. The
feature was added, if not working, it will be a new bug.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1274#issuecomment-381
Closed #1274.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1274#event-1574493588___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
ht
@miconda
We've modified the route like this now:
`
route[FOREIGN_DIALOG] {
$var(breadcrumbs) = "FOREIGN_DIALOG"; BREADCRUMBS
xlog("L_NOTICE","[f:$fU-t:$tU id:$ci | $rm] Foreign dialog detected for
Call-ID: $ci\n");
dlg_db_load_callid($ci);
setflag(FLG_AUTH_PASSED);
dlg_manage();
} # en
So, on kamailio2, you get the BYE and because the dialog is not found in
memory, you do the dlg_db_load_callid() via route[FOREIGN_DIALOG]? Or is
another logic calling route[FOREIGN_DIALOG]?
Why do you send 200ok for BYE via sl_send_reply("200","OK")? Shouldn't it be
relayed and the reply be
Ok @miconda,
So let's start with the failover case first.
I start a call on **kamailio1**:
`kamcmd> dlg.list
{
h_entry: 2294
h_id: 5833
ref: 2
call-id: lbiUaRwZR8x3mRiBjxWlJDpqkO9JHTdD
from_uri: sip:0409828...@proxy.alex.cloud.evox.it
to_uri: sip:390
Maybe you should summarise the cases that work and the cases that do now work,
because you didn't follow what I asked and now it is hard to sort out what
needs to be troubleshooted and fixed. Then we start looking at the cases that
do not work as expected, one by one.
Also, it would be good if
Yes shure,
but in the case i mentioned above there's a problem that some dialogs are
cleared on call end and some remain in state 5 and are not cleared in the
db.
Regarding the failover I can observe this after another camailio node loads
the dialog from db and the call ends client side:
```kamcm
I need for the failover case, from the second node that loads the dialog from
db -- that's what we need to debug.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1274#issuecomment-380051408___
Hi Daniel,
so with no node failover in the ongoing call I've got this:
```
kamcmd> dlg.list
{
h_entry: 3696
h_id: 3033
ref: 3
call-id: x64Qy6smfdCH8keXe7rx1gfzr5-NCKH.
from_uri: sip:0409828...@proxy.alex.cloud.evox.it
to_uri: sip:390409828...@proxy.alex.cloud.evox.it
state: 4
start_ts: 1523355019
Is it staying in state 4? Previously you added an example with state 5. State 4
means that the call was not ended yet ... If you didn't grab the rpc output for
ended dialog, do it again, i need the ref count for state 5.
There is a cleanup timeout for the cases when something on top of dialog is
I can notice that after some minutes the dialog is deleted. Is there a timeout?
--
Aleksandar Sošić
alex.sosic(at)gmailcom
On Mon, Apr 9, 2018 at 12:56 PM, Aleksandar Sosic wrote:
> Hi,
>
> I'm using 5.2.0~dev4+0~20180408010333.1091+xenial now.
> The dialog without the failover is correctly dele
Hi,
I'm using 5.2.0~dev4+0~20180408010333.1091+xenial now.
The dialog without the failover is correctly deleted now:
kamcmd> dlg.list
{
h_entry: 93
h_id: 9163
ref: 2
call-id: w6HWT0d6EZaVY3Lt1dIi0auvX1sq7Ctl
from_uri: sip:0409828...@proxy.alex.cloud.evox.it
to_uri: sip:390409828...@proxy.alex.clo
Can you try with latest version and paste again the dialog list rpc output?
Over the weekend I pushed a patch to print the reference counter value for the
dialog.
Do you use other modules that need dialog?
--
You are receiving this because you commented.
Reply to this email directly or view it
Two test calls, each of them ended client side. Still in dialog.
```kamcmd> dlg.list
{
h_entry: 1685
h_id: 9485
call-id: pd32UDkxLpckfIImaMSLBwxDuFEtHz5V
from_uri: sip:0409828...@proxy.mydomain.it
to_uri: sip:0039040123...@proxy.mydomain.it
state: 5
start_ts: 1523022068
init_ts: 1523022067
timeout
The warnings are due to different local socket addresses, probably they should
be made debug level.
Are the dialogs not deleted from database also in memory (can you see them in
the output of dialog list rpc command)? If yes, paste here the output of such
dialog from the rpc command.
--
You
Hi Daniel,
I just tested this version and what I could notice is:
with the first kamailio node comming up and doing some test calls the
dialog records in the DB are not deleted after the call end.
On kamailio node failover (call in progress, and new node up with
hangup on client side) I've got t
2018-04-05 11:43 GMT+02:00 alexsosic :
> I'm trying the install this morning and got:
> ```kamailio is already the newest version
> (5.2.0~dev4+0~20180310010216.1064+xenial).```
>
> In my sources list:
> deb http://deb.kamailio.org/kamailiodev-nightly xenial main
> deb-src http://deb.kamailio.org/
@alexsosic, nothing to do with this issue. Please use the mailing list for this.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1274#issuecomment-378885725___
I'm trying the install this morning and got:
```kamailio is already the newest version
(5.2.0~dev4+0~20180310010216.1064+xenial).```
In my sources list:
deb http://deb.kamailio.org/kamailiodev-nightly xenial main
deb-src http://deb.kamailio.org/kamailiodev-nightly xenial main
What am I doing wron
In our case we will have an autoscaling system of Kamailio based on geographic
requests and load so we will not be able to know in advance how many instances
ok kamailio will be provisioned. As you suggested for this temporary workaround
we should have :
Server 1 : 1, 101,201,301,401...
Server
If there are 3 servers, then the step should at least 3, resulting in:
```
Server1: 1, 4, 7, 10, ...
Server2: 2, 5, 8, 11, ...
Server3: 3, 6, 9, 12, ...
```
So the start value should be the `index` of the server and the increment value
has to be at least the number of servers. There is no confli
Am Mittwoch, 4. April 2018, 09:52:23 CEST schrieb Daniel-Constantin Mierla:
> I just committed the config (and kemi) function `dlg_db_load_callid(val)`,
> which should load dialog record from database by matching on callid (it
> loads also associated variables).
>
> While not tested yet given lack
I just committed the config (and kemi) function `dlg_db_load_callid(val)`,
which should load dialog record from database by matching on callid (it loads
also associated variables).
While not tested yet given lack of proper environment to simulate such scenario
(hopefully you can do it), there i
23 matches
Mail list logo
