Module: kamailio
Branch: 5.1
Commit: c9693c18aeed8efc36905702221cd466bedcb9df
URL: https://github.com/kamailio/kamailio/commit/c9693c18aeed8efc36905702221cd46…
Author: Henning Westerholt <hw(a)kamailio.org>
Committer: Henning Westerholt <hw(a)kamailio.org>
Date: 2018-04-12T21:35:24+02:00
msilo: remove not working tm parameter in the example cfg, reported from Abdul Basit
- remove the not working, too small tm parameter in the example cfg
- has been not changed in the last 10 years, probably not valid anymore
- reported from Abdul Basit on sr-users
(cherry picked from commit 22b13d4d44cb0dbd71b87deab42af5f7c8ea932f)
---
Modified: src/modules/msilo/doc/msilo.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/c9693c18aeed8efc36905702221cd46…
Patch: https://github.com/kamailio/kamailio/commit/c9693c18aeed8efc36905702221cd46…
---
diff --git a/src/modules/msilo/doc/msilo.cfg b/src/modules/msilo/doc/msilo.cfg
index 05329f0299..e6c74ff6d2 100644
--- a/src/modules/msilo/doc/msilo.cfg
+++ b/src/modules/msilo/doc/msilo.cfg
@@ -48,12 +48,6 @@ modparam("msilo","contact_hdr","Contact: registrar@192.168.1.2:5060;msilo=yes\r\
modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
modparam("msilo","offline_message","*** User $rU is offline!")
-# -- tm params --
-
-modparam("tm", "fr_timer", 10 )
-modparam("tm", "fr_inv_timer", 15 )
-modparam("tm", "wt_timer", 10 )
-
route{
if ( !mf_process_maxfwd_header("10") )
Module: kamailio
Branch: master
Commit: 22b13d4d44cb0dbd71b87deab42af5f7c8ea932f
URL: https://github.com/kamailio/kamailio/commit/22b13d4d44cb0dbd71b87deab42af5f…
Author: Henning Westerholt <hw(a)kamailio.org>
Committer: Henning Westerholt <hw(a)kamailio.org>
Date: 2018-04-12T21:31:59+02:00
msilo: remove not working tm parameter in the example cfg, reported from Abdul Basit
- remove the not working, too small tm parameter in the example cfg
- has been not changed in the last 10 years, probably not valid anymore
- reported from Abdul Basit on sr-users
---
Modified: src/modules/msilo/doc/msilo.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/22b13d4d44cb0dbd71b87deab42af5f…
Patch: https://github.com/kamailio/kamailio/commit/22b13d4d44cb0dbd71b87deab42af5f…
---
diff --git a/src/modules/msilo/doc/msilo.cfg b/src/modules/msilo/doc/msilo.cfg
index 7bec0841e6..1ea4bc3545 100644
--- a/src/modules/msilo/doc/msilo.cfg
+++ b/src/modules/msilo/doc/msilo.cfg
@@ -48,12 +48,6 @@ modparam("msilo","contact_hdr","Contact: registrar@192.168.1.2:5060;msilo=yes\r\
modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
modparam("msilo","offline_message","*** User $rU is offline!")
-# -- tm params --
-
-modparam("tm", "fr_timer", 10 )
-modparam("tm", "fr_inv_timer", 15 )
-modparam("tm", "wt_timer", 10 )
-
route{
if ( !mf_process_maxfwd_header("10") )
### 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
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
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
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
**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:xxxx@xxxx;user=phone;tag=SDt2dkc98-04020267673121
Max-Forwards: 63
Record-Route: sip:192.168.70.126:5060;user=i0o0S000000ad;lr;Cpkt=XWJOA;C=xxxx,sip:192.168.70.126:5070;user=00000214;lr;Cpkt=YJJEE;C=xxx
To: sip:+yyyy@xxxx;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=z9hG4bK5g8vgn00cobc0atd6hf0sb0000g00.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@xxxx;tag=SDt2dkc98-04020267673121
Max-Forwards: 62
To: sip:xxx@xxxx;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@xxxx;tag=SDt2dkc98-04020267673121
To: sip:xxx@xxxx;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**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
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
> CC (clang) [M cdp.so] authstatemachine.o
> authstatemachine.c:748:3: warning: implicit conversion from 'int' to 'char' changes value from 209 to -47 [-Wconstant-conversion]
> set_4bytes(x, AAA_SUCCESS);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ./diameter.h:77:44: note: expanded from macro 'set_4bytes'
> (_b)[2]=((_v)&0x0000ff00)>>8;(_b)[3]=((_v)&0x000000ff);}
> ~ ~~~~^~~~~~~~~~~
> authstatemachine.c:758:3: warning: implicit conversion from 'int' to 'char' changes value from 209 to -47 [-Wconstant-conversion]
> set_4bytes(x, AAA_SUCCESS);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ./diameter.h:77:44: note: expanded from macro 'set_4bytes'
> (_b)[2]=((_v)&0x0000ff00)>>8;(_b)[3]=((_v)&0x000000ff);}
> ~ ~~~~^~~~~~~~~~~
> ocs_avp_helper.c:329:3: warning: implicit conversion from 'int' to 'char' changes value from 128 to -128 [-Wconstant-conversion]
> set_4bytes(x, 86400);
> ^~~~~~~~~~~~~~~~~~~~
> ./../cdp/diameter.h:77:44: note: expanded from macro 'set_4bytes'
> (_b)[2]=((_v)&0x0000ff00)>>8;(_b)[3]=((_v)&0x000000ff);}
> ~ ~~~~^~~~~~~~~~~
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1497
-- Commit Summary --
* cdp: fix compilation warning
-- File Changes --
M src/modules/cdp/diameter.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1497.patchhttps://github.com/kamailio/kamailio/pull/1497.diff
--
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/pull/1497