OK, thanks for testing and feedback. I am going to backport to stable branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1496.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1496#event-1571464959___
Kamailio (SER) - Development Mailing List
Well, it only worked once...
Now I am having the problem of infinite loop when routing the first INVITE of a
new dialog. As if the dialog of an already hung up call is reused for new
calls...
I am investigating and will update this ticket with any new finding.
--
You are receiving this because
It works @miconda. Thank you very much!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1496#issuecomment-380825960___
Kamailio (SER) -
Can you try with latest master branch? I pushed a patch to it, let's see if it
fixed and then can be backported.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
By searching in the code, I found that the error message I had *no valid dlg
uuid (0: - 0:)* is found only in the function tps_storage_update_dialog.
>From my log file, I can say that this error message was showing during the
>handling of the 200 OK (of the RE-INVITE). Hence I suppose that the
Table topos_d and topos_t before the REINVITE:
**topos_d:**
(id;rectime;s_method;s_cseq;a_callid;a_uuid;b_uuid;a_contact;b_contact;as_contact;bs_contact;a_tag;b_tag;a_rr;b_rr;s_rr;iflags;a_uri;b_uri;r_uri;a_srcaddr;b_srcaddr;a_socket;b_socket)
470690;2018-04-11
Can you reproduce the issue and paste here the corresponding records from
database tables topos_d and topos_t? Add again also the new SIP requests and
replies in order to match with what is in the database.
--
You are receiving this because you are subscribed to this thread.
Reply to this
### Description
I have an instance of Kamailio running with topos module enabled as described
bellow:
(Core network)<---> (**Kamailio** running on 192.168.70.106:5061) <-->
(Provider network)
Here is the scenario:
1. An INVITE comming from Core network through Kamailio to the
