[sr-dev] git:master:9ddf2b6b: modules: readme files regenerated - acc ... [skip ci]

[Kamailio Dev]

Module: kamailio
Branch: master
Commit: 9ddf2b6b5679e508da25dbdc4807115349541ea9
URL: 
https://github.com/kamailio/kamailio/commit/9ddf2b6b5679e508da25dbdc4807115349541ea9

Author: Kamailio Dev 
Committer: Kamailio Dev 
Date: 2018-04-11T23:48:06+02:00

modules: readme files regenerated - acc ... [skip ci]

---

Modified: src/modules/acc/README
Modified: src/modules/app_perl/README
Modified: src/modules/cdp/README
Modified: src/modules/cdp_avp/README
Modified: src/modules/dialog/README
Modified: src/modules/dispatcher/README
Modified: src/modules/ims_dialog/README
Modified: src/modules/ims_registrar_scscf/README
Modified: src/modules/ims_usrloc_pcscf/README
Modified: src/modules/nathelper/README
Modified: src/modules/registrar/README
Modified: src/modules/rtpengine/README
Modified: src/modules/rtpproxy/README
Modified: src/modules/snmpstats/README

---

Diff:  
https://github.com/kamailio/kamailio/commit/9ddf2b6b5679e508da25dbdc4807115349541ea9.diff
Patch: 
https://github.com/kamailio/kamailio/commit/9ddf2b6b5679e508da25dbdc4807115349541ea9.patch


___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] module FAQ, private contact replacement

[Henning Westerholt]

Am Mittwoch, 4. April 2018, 09:07:33 CEST schrieb Daniel-Constantin Mierla:
> On 04.04.18 08:14, Henning Westerholt wrote:
> > Am Dienstag, 3. April 2018, 22:59:42 CEST schrieb Daniel-Constantin 
Mierla:
> >>> I will change it to involve only security bugs, this way we could easily
> >>> change it when we have a dedicated security contact address. If we get
> >>> to much spam, I will remove it completely.
> >> 
> >> I still think this is not the right way to do it, but remove it
> >> completely. It is not across all modules, only couple of them.
> >> 
> >> And again, so far nobody actually used it. When having to report
> >> something more sensitive, people found the way to do it.
> >> 
> >> Management doesn't have to do anything with those modules and should not
> >> get involved in their readme. There is a contact page with more details
> >> on project's website.
> [..]

Hello,

the additional information was removed again.

Henning

___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] git:master:e0403459: module docs: remove info for confidential security reports again from module FAQs

[Henning Westerholt]

Module: kamailio
Branch: master
Commit: e0403459f582e9264379a36061f1ef09e788bedc
URL: 
https://github.com/kamailio/kamailio/commit/e0403459f582e9264379a36061f1ef09e788bedc

Author: Henning Westerholt 
Committer: Henning Westerholt 
Date: 2018-04-11T23:41:24+02:00

module docs: remove info for confidential security reports again from module 
FAQs

---

Modified: doc/docbook/entities.xml
Modified: src/modules/acc/doc/acc_faq.xml
Modified: src/modules/app_perl/doc/app_perl_faq.xml
Modified: src/modules/cdp/doc/cdp_faq.xml
Modified: src/modules/cdp_avp/doc/cdp_avp_faq.xml
Modified: src/modules/dialog/doc/dialog_faq.xml
Modified: src/modules/dispatcher/doc/dispatcher_faq.xml
Modified: src/modules/ims_dialog/doc/ims_dialog_faq.xml
Modified: src/modules/ims_registrar_scscf/doc/ims_registrar_scscf_faq.xml
Modified: src/modules/ims_usrloc_pcscf/doc/ims_usrloc_pcscf_faq.xml
Modified: src/modules/nathelper/doc/nathelper_faq.xml
Modified: src/modules/registrar/doc/registrar_faq.xml
Modified: src/modules/rtpengine/doc/rtpengine_faq.xml
Modified: src/modules/rtpproxy/doc/rtpproxy_faq.xml
Modified: src/modules/snmpstats/doc/snmpstats_faq.xml

---

Diff:  
https://github.com/kamailio/kamailio/commit/e0403459f582e9264379a36061f1ef09e788bedc.diff
Patch: 
https://github.com/kamailio/kamailio/commit/e0403459f582e9264379a36061f1ef09e788bedc.patch


___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] 200 OK message for RE-INVITE is dropped when using topos module (#1496)

[David Minh Phan]

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 

[sr-dev] git:master:cc6865cd: db_redis: Fix scanning large tables

[Andreas Granig]

Module: kamailio
Branch: master
Commit: cc6865cd7d0fc48709acd7685d315eb5575e45bd
URL: 
https://github.com/kamailio/kamailio/commit/cc6865cd7d0fc48709acd7685d315eb5575e45bd

Author: Andreas Granig 
Committer: Andreas Granig 
Date: 2018-04-11T17:28:32+02:00

db_redis: Fix scanning large tables

* When querying large tables (e.g. pre-loading location by usrloc),
  make sure to use O(1) when adding keys by prepending them to list.
* Increase batch size of redis scan command to reduce number of
  redis queries.
* Batch creation of DB_ROW entries to free up memory allocated by
  redis in heap regularly.
* Fix more issues reported by coverity.

---

Modified: src/modules/db_redis/redis_connection.c
Modified: src/modules/db_redis/redis_dbase.c
Modified: src/modules/db_redis/redis_table.c

---

Diff:  
https://github.com/kamailio/kamailio/commit/cc6865cd7d0fc48709acd7685d315eb5575e45bd.diff
Patch: 
https://github.com/kamailio/kamailio/commit/cc6865cd7d0fc48709acd7685d315eb5575e45bd.patch


___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] KeepAlive Module (#1476)

[Daniel-Constantin Mierla]

@gbour, @voztovoice - can this be closed? I see a commit by @gbour referenced 
here.

-- 
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/1476#issuecomment-380490786___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] Is t_flush_flags() really needed? (#1490)

[Daniel-Constantin Mierla]

Closed #1490.

-- 
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/1490#event-1568858450___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] Is t_flush_flags() really needed? (#1490)

[Daniel-Constantin Mierla]

Closing, the patch was pushed to master. If still not working as expected, 
reopen.

-- 
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/1490#issuecomment-380490303___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] 200 OK message for RE-INVITE is dropped when using topos module (#1496)

[Daniel-Constantin Mierla]

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 email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1496#issuecomment-380489952___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] [kamailio/kamailio] 200 OK message for RE-INVITE is dropped when using topos module (#1496)

[David Minh Phan]

### 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 Provider network 
and the call is established correctly (with 200 OK and ACK correctly routed).
2. The call is put on hold by the callee. A RE-INVITE comming from Provider 
network through Kamailio to the Core network. This REINVITE is routed correctly.
3. The Core network sent 200 OK reply to the RE-INVITE. The 200 OK message 
reached the Kamailio and was dropped there. (It SHOULD go back to the Provider 
network).

 Log Messages



When Kamailio received this 200 OK, I see this log message:
```
ERROR: topos [tps_storage.c:1299]: tps_db_update_dialog(): no valid dlg uuid 
(0: - 0:)
```

 SIP Traffic



**Here is the REINVITE message arriving from our provider:**

```
INVITE sip:btpsh-5acddf40-d74-5@192.168.70.106:5061 SIP/2.0
Call-ID: 79acbb714c21354c
Contact: sip:80.10.231.10:5060;transport=udp
Content-Type: application/sdp
CSeq: 1 INVITE
From: sip:@;user=phone;tag=SDt2dkc98-04020267673121
Max-Forwards: 63
Record-Route: 
sip:192.168.70.126:5060;user=i0o0S00ad;lr;Cpkt=XWJOA;C=,sip:192.168.70.126:5070;user=0214;lr;Cpkt=YJJEE;C=xxx
To: sip:+@;user=phone;tag=1713351228
Via: SIP/2.0/UDP 
192.168.70.126:5060;branch=z9hG4bK-XWJO-000227ab-7eda6242,SIP/2.0/UDP 
192.168.70.126:5070;received=192.168.70.126;rport=5070;branch=z9hG4bK-YJJE-000a057c-0bf8ef7c,SIP/2.0/UDP
 193.200.4.20:5060;emission,SIP/2.0/UDP 
80.10.231.10:5060;received=80.10.231.10;rport=5060;branch=z9hG4bK5g8vgn00cobc0atd6hf0sbg00.1
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236
```

**Here is the REINVITE comming out of Kamailio into our core side:**

```
INVITE sip:192.168.40.106:5090;did=d03.e3be0354 SIP/2.0
Via: SIP/2.0/UDP 
192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
Call-ID: 79acbb714c21354c
Content-Type: application/sdp
CSeq: 1 INVITE
From: sip:+xxx@;tag=SDt2dkc98-04020267673121
Max-Forwards: 62
To: sip:xxx@;tag=1713351228
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236
Route: xxx
Contact: sip:atpsh-5acddf40-d75-5@192.168.70.106:5061
```

**Here is the 200 OK for this REINVITE message comming from the Core network** 
(This message arrived to Kamailio but is never sent to our provider).

```
SIP/2.0 200 OK
Via: SIP/2.0/UDP 
192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
From: sip:+xxx@;tag=SDt2dkc98-04020267673121
To: sip:xxx@;tag=1713351228
Call-ID: 79acbb714c21354c
CSeq: 1 INVITE
Contact: sip:192.168.40.106:5090;did=d03.e3be0354
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 197
```

### Additional Information

  * **Kamailio Version** - output of `kamailio -v`

kamailio 5.1.2

* **Operating System**:



Centos Linux 3.10.0-514.26.1.el7.x86_64

* **Database**:

PostgreSQL 9.4


-- 
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___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] git:master:80ac75e0: modules: readme files regenerated - tmx ... [skip ci]

[Kamailio Dev]

Module: kamailio
Branch: master
Commit: 80ac75e0d5cba58cbf6bb5fbce35b56e7f4fbe86
URL: 
https://github.com/kamailio/kamailio/commit/80ac75e0d5cba58cbf6bb5fbce35b56e7f4fbe86

Author: Kamailio Dev 
Committer: Kamailio Dev 
Date: 2018-04-11T15:46:28+02:00

modules: readme files regenerated - tmx ... [skip ci]

---

Modified: src/modules/tmx/README

---

Diff:  
https://github.com/kamailio/kamailio/commit/80ac75e0d5cba58cbf6bb5fbce35b56e7f4fbe86.diff
Patch: 
https://github.com/kamailio/kamailio/commit/80ac75e0d5cba58cbf6bb5fbce35b56e7f4fbe86.patch

---

diff --git a/src/modules/tmx/README b/src/modules/tmx/README
index 56d9ca546c..81568f329d 100644
--- a/src/modules/tmx/README
+++ b/src/modules/tmx/README
@@ -263,6 +263,10 @@ if (t_reply_callid("123qaz", "5", "458", "Replied 
remotely")) {
transaction. It make sense only in routing block if the transaction was
created via t_newtran() and the flags have been altered since.
 
+   It is not needed to execute this function when using t_relay() (or
+   similar tm relay functions, flags are synchornized automatically in
+   that case).
+
This function can be used from ANY_ROUTE .
 
Example 1.5. t_flush_flags usage
@@ -277,6 +281,10 @@ t_flush_flags();
transaction was created via t_newtran() and the extended flags have
been altered since.
 
+   It is not needed to execute this function when using t_relay() (or
+   similar tm relay functions, xflags are synchornized automatically in
+   that case).
+
This function can be used from ANY_ROUTE .
 
Example 1.6. t_flush_xflags usage


___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] git:master:d87a6a01: tmx: docs - notes that flush x/flags is not needed when doing tm relay

[Daniel-Constantin Mierla]

Module: kamailio
Branch: master
Commit: d87a6a012f7888ea74a0f25731fb6b442e4e38aa
URL: 
https://github.com/kamailio/kamailio/commit/d87a6a012f7888ea74a0f25731fb6b442e4e38aa

Author: Daniel-Constantin Mierla 
Committer: Daniel-Constantin Mierla 
Date: 2018-04-11T15:41:21+02:00

tmx: docs - notes that flush x/flags is not needed when doing tm relay

---

Modified: src/modules/tmx/doc/tmx_admin.xml

---

Diff:  
https://github.com/kamailio/kamailio/commit/d87a6a012f7888ea74a0f25731fb6b442e4e38aa.diff
Patch: 
https://github.com/kamailio/kamailio/commit/d87a6a012f7888ea74a0f25731fb6b442e4e38aa.patch

---

diff --git a/src/modules/tmx/doc/tmx_admin.xml 
b/src/modules/tmx/doc/tmx_admin.xml
index 9f6168bb0f..fe630d2f76 100644
--- a/src/modules/tmx/doc/tmx_admin.xml
+++ b/src/modules/tmx/doc/tmx_admin.xml
@@ -215,6 +215,11 @@ if (t_reply_callid("123qaz", "5", "458", "Replied 
remotely")) {
created via t_newtran() and the flags have been altered since.


+   It is not needed to execute this function when using t_relay() 
(or
+   similar tm relay functions, flags are synchornized 
automatically in
+   that case).
+   
+   
This function can be used from ANY_ROUTE .


@@ -236,6 +241,11 @@ t_flush_flags();
created via t_newtran() and the extended flags have been 
altered since.


+   It is not needed to execute this function when using t_relay() 
(or
+   similar tm relay functions, xflags are synchornized 
automatically in
+   that case).
+   
+   
This function can be used from ANY_ROUTE .




___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] git:master:d0668c77: tm: resync xflags on new t_newtran() attempt

[Daniel-Constantin Mierla]

Module: kamailio
Branch: master
Commit: d0668c7736455dc1231d6a5403effb297fe9d741
URL: 
https://github.com/kamailio/kamailio/commit/d0668c7736455dc1231d6a5403effb297fe9d741

Author: Daniel-Constantin Mierla 
Committer: Daniel-Constantin Mierla 
Date: 2018-04-11T15:09:40+02:00

tm: resync xflags on new t_newtran() attempt

- have the same behaviour as for flags
- reported by GH #1490

---

Modified: src/modules/tm/t_lookup.c

---

Diff:  
https://github.com/kamailio/kamailio/commit/d0668c7736455dc1231d6a5403effb297fe9d741.diff
Patch: 
https://github.com/kamailio/kamailio/commit/d0668c7736455dc1231d6a5403effb297fe9d741.patch

---

diff --git a/src/modules/tm/t_lookup.c b/src/modules/tm/t_lookup.c
index 49d02111f1..494afd457c 100644
--- a/src/modules/tm/t_lookup.c
+++ b/src/modules/tm/t_lookup.c
@@ -1326,8 +1326,11 @@ int t_newtran( struct sip_msg* p_msg )
/* t_newtran() has been already called, and the script
 * might changed the flags after it, so we must update the flags
 * in shm memory -- Miklos */
-   if (T->uas.request)
+   if (T->uas.request) {
T->uas.request->flags = p_msg->flags;
+   memcpy(T->uas.request->xflags, p_msg->xflags,
+   KSR_XFLAGS_SIZE * sizeof(flag_t));
+   }
 
return E_SCRIPT;
}


___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] topos module producing invalid SIP message (missing Via header) when handling 200 OK to OPTIONS request (#1350)

[Daniel-Constantin Mierla]

@qmphan - open a new issue, do not comment on a closed issue from several 
months ago, even if seems related, this one was closed with the code base at 
the same time. Use the relevant comments and details you put here and make a 
new issue.

-- 
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/1350#issuecomment-380446786___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] Is t_flush_flags() really needed? (#1490)

[Daniel-Constantin Mierla]

Looked in the code and the flags are resync'ed on t_relay() (or the similar 
relay functions), that happens because of:

  * 
https://github.com/kamailio/kamailio/blob/master/src/modules/tm/t_lookup.c#L1327

And t_newtran() is executed inside t_relay_to():

  * 
https://github.com/kamailio/kamailio/blob/master/src/modules/tm/t_funcs.c#L241

The behaviour is coming via SER project, based on the comments there.

I am going to add the same for xflags.

On the other hand, the t_flush_flags() might still be useful for the case when 
the transaction is created, but not forwarded (e.g., local handling or, even I 
haven't checked the code, could be the case of suspending the transaction), so 
I am going to keep the functions, but document that they are not needed if the 
transaction is forwarded with t_relay() or similar functions.

-- 
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/1490#issuecomment-380444664___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] topos module producing invalid SIP message (missing Via header) when handling 200 OK to OPTIONS request (#1350)

[David Minh Phan]

The same problem still exist with the lastest code. That's logic because I had 
reported this error before the commit 97532ca

Any help is highly appreciated.

-- 
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/1350#issuecomment-380418384___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] topos module producing invalid SIP message (missing Via header) when handling 200 OK to OPTIONS request (#1350)

[David Minh Phan]

Well, I've just read the #1421. Let me update the code and test again first.

-- 
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/1350#issuecomment-380412551___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Re: [sr-dev] [kamailio/kamailio] topos module producing invalid SIP message (missing Via header) when handling 200 OK to OPTIONS request (#1350)

[David Minh Phan]

I still have the problem of routing the 200 OK message for the REINVITE.

192.168.70.106:5061 is the Kamailio with topos module enabled.

**Here is the REINVITE message arriving from our provider:**

INVITE sip:btpsh-5acddf40-d74-5@192.168.70.106:5061 SIP/2.0
Call-ID: 79acbb714c21354c
Contact: 
Content-Type: application/sdp
CSeq: 1 INVITE
From: ;tag=SDt2dkc98-04020267673121
Max-Forwards: 63
Record-Route: 
,
To: ;tag=1713351228
Via: SIP/2.0/UDP 
192.168.70.126:5060;branch=z9hG4bK-XWJO-000227ab-7eda6242,SIP/2.0/UDP 
192.168.70.126:5070;received=192.168.70.126;rport=5070;branch=z9hG4bK-YJJE-000a057c-0bf8ef7c,SIP/2.0/UDP
 193.200.4.20:5060;emission,SIP/2.0/UDP 
80.10.231.10:5060;received=80.10.231.10;rport=5060;branch=z9hG4bK5g8vgn00cobc0atd6hf0sbg00.1
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236

**Here is the REINVITE comming out of Kamailio into our core side:**

INVITE sip:192.168.40.106:5090;did=d03.e3be0354 SIP/2.0
Via: SIP/2.0/UDP 
192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
Call-ID: 79acbb714c21354c
Content-Type: application/sdp
CSeq: 1 INVITE
From: ;tag=SDt2dkc98-04020267673121
Max-Forwards: 62
To: ;tag=1713351228
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236
Route: xxx
Contact: 


**Here is the 200 OK for this REINVITE message comming from the core side** 
(This message arrived to Kamailio but is never sent to our provider).

SIP/2.0 200 OK
Via: SIP/2.0/UDP 
192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
From: ;tag=SDt2dkc98-04020267673121
To: ;tag=1713351228
Call-ID: 79acbb714c21354c
CSeq: 1 INVITE
Contact: 
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 197

**When Kamailio received this 200 OK, I see this log message:**
ERROR: topos [tps_storage.c:1299]: tps_db_update_dialog(): no valid dlg uuid 
(0: - 0:)

Some hint on how to debug this please @miconda ?





-- 
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/1350#issuecomment-380411710___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev