<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
using KEMI API in Python v2.7.18 for Kamailio v5.6.2, I encounter error in `ksr_onsend_route`, it always gives following error,
```
ERROR: app_python [python_support.c:154]: python_handle_exception(): apy_exec: ksr_onsend_route((null)): Unhandled exception in the Python code:
TypeError: an integer is required
```
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
Above error happens even if there is no code in this function and it returns success, e.g.
``` python
...
def ksr_onsend_route(self, msg):
return 1
...
```
#### Reproduction
It happens always whenever `ksr_onsend_route` function exists in `kamailio` class in KEMI python configuration for kamailio.
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
Nothing relevant in debug even with `debug=9` set.
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
#### 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).
-->
```
ERROR: app_python [python_support.c:154]: python_handle_exception(): apy_exec: ksr_onsend_route((null)): Unhandled exception in the Python code:
TypeError: an integer is required
```
#### 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).
-->
```
REGISTER sip:voip-test.sip-domain.de:5060 SIP/2.0.
Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK-1523596-64-0.
From: <sip:490000063@voip-test.sip-domain.de:5060>;tag=64.
To: <sip:490000063@voip-test.sip-domain.de:5060>.
Call-ID: call_id_64.
CSeq: 1 REGISTER.
Contact: sip:490000063@x.x.x.x:5060.
Max-Forwards: 70.
Content-Length: 0.
..
```
### Possible Solutions
I suspect the problem is at low level (native code) of app_python module.
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.6.2 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id:
compiled with gcc 10.2.1
```
```
Python 2.7.18
```
* **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 `lsb_release -a` and `uname -a`)
-->
```
Linux test-sip-server 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3274
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3274(a)github.com>
### Description
When I use Kamailio 5.6 with kazoo config file, then can see error messages:
```
WARNING: <core> [core/rvalue.c:1043]: rval_get_int(): automatic string to int conversion for "63823655406" failed
WARNING: <core> [core/rvalue.c:1949]: rval_expr_eval_int(): rval expression conversion to int failed (140,54-140,73)
```
This warning message related to commit bcd59d73e2fc5ae8e14cad520e726ef431f0563f.
Kazoo sending timestamp using the Gregorian format and timestamp value greater than max int value.
As a result, JSON string values with a timestamp cannot be parsed and converted to int.
As I understand required to add long format support into Kamailio.
This was tested using this Kamailio config.
```
listen=udp:127.0.0.1:5060
######## Advanced logger module ########
loadmodule "xlog.so"
######## Generic Hash Table container in shared memory ########
loadmodule "htable.so"
event_route[htable:mod-init] {
if ( 63823655406 > 0 ) {
xlog("L_ERR", "*** Kamailio support long data type!\n");
} else {
xlog("L_ERR", "*** Kamailio not support long data type!\n");
}
}
```
### Expected behavior
Kamailio is able to convert strings to long data type.
#### Actual observed behavior
Kamailio was not able to convert strings to long data type.
@lazedo, probable you want to know about this behavior.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3172
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3172(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
We have observed that when the call is answered and it is in active state more than 30 seconds, kamailio sends the notify messages with the "Idle" appearance to all the subscribed extensions. Practically it should not send the idle notification when the call is in active state.
We have tried to change the mod parameter "purge_expired_interval" to 3600 seconds. but still idle notification transmit in 30 seconds. To overcome this issue, we have commented below line in the sca.c file.
register_timer( sca_appearance_purge_stale, sca, sca->cfg->purge_expired_interval);
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3249
-- Commit Summary --
* Update sca.c - Fix done for Appearance purge stale
-- File Changes --
M src/modules/sca/sca.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3249.patchhttps://github.com/kamailio/kamailio/pull/3249.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3249
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3249(a)github.com>
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Added SCTP support for CDP module
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3327
-- Commit Summary --
* cdp: Add SCTP support
-- File Changes --
M src/modules/cdp/acceptor.c (2)
M src/modules/cdp/config.h (4)
M src/modules/cdp/configexample/ConfigExample.xml (5)
M src/modules/cdp/configparser.c (10)
M src/modules/cdp/peer.c (3)
M src/modules/cdp/peer.h (3)
M src/modules/cdp/peermanager.c (4)
M src/modules/cdp/receiver.c (7)
M src/modules/cdp/tcp_accept.c (9)
M src/modules/cdp/tcp_accept.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3327.patchhttps://github.com/kamailio/kamailio/pull/3327.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3327
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3327(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Following carrierroute module functions are exported to KEMI API.
- cr_load_next_domain ( )
- cr_route ( )
- cr_nofallback_route ( )
Additionally various fix-up free functions added for better memory management. The documentation has been updated to correctly explain various parameters and use cases.
#### Example 1: Proxy Routing
```python3
def route_proxy(self, msg):
KSR.info("==================== route_proxy\n")
rU = KSR.kx.get_ruser()
if rU == None:
return -255
if KSR.carrierroute.cr_route("default", "proxy", rU, rU, "call_id") < 0:
KSR.sl.sl_send_reply(400, "Bad Request")
return -255
```
#### Example 2: Registrar Routing
```python3
def route_registrar(self, msg):
KSR.info("==================== route_registrar\n")
rU = KSR.kx.get_ruser()
if rU == None:
rU = ""
if KSR.carrierroute.cr_nofallback_route("default", "register", rU, rU, "from_user") < 0:
KSR.sl.sl_send_reply(400, "Bad Request")
return -255
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3325
-- Commit Summary --
* carrierroute: added fixup free functions
* carrierroute: exported cr_load_next_domain(), cr_route() and cr_nofallback_route() to kemi
* carrierroute: added helper methods to simplify config and kemi functions, also some code clean up
* carrierroute: updated module docs
-- File Changes --
M src/modules/carrierroute/carrierroute.c (46)
M src/modules/carrierroute/cr_fixup.c (176)
M src/modules/carrierroute/cr_fixup.h (4)
M src/modules/carrierroute/cr_func.c (675)
M src/modules/carrierroute/cr_func.h (65)
M src/modules/carrierroute/doc/carrierroute.xml (79)
M src/modules/carrierroute/doc/carrierroute_admin.xml (1403)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3325.patchhttps://github.com/kamailio/kamailio/pull/3325.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3325
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3325(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3320
-- Commit Summary --
* Replace kamailio.org/wiki with kamailio.org/wikidocs
-- File Changes --
M .github/CONTRIBUTING.md (2)
M INSTALL (6)
M README (2)
M README.md (2)
M doc/README.md (2)
M doc/docbook/entities.xml (2)
M doc/man/kamailio.cfg.5 (2)
M doc/misc/NEWS (20)
M etc/kamailio.cfg (2)
M misc/examples/kemi/kamailio-basic-kemi.cfg (2)
M misc/examples/mixed/kamailio-minimal-anycast.cfg (2)
M misc/examples/mixed/kamailio-minimal-proxy.cfg (2)
M misc/examples/pkg/kamailio-basic.cfg (2)
M misc/examples/pkg/kamailio-oob.cfg (2)
M misc/examples/webrtc/kamailio-default-websocket.cfg (2)
M src/modules/acc/doc/acc_admin.xml (4)
M src/modules/app_java/README-draft (4)
M test/travis/README.md (2)
M test/unit/21.cfg (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3320.patchhttps://github.com/kamailio/kamailio/pull/3320.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3320
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3320(a)github.com>
Module: kamailio
Branch: master
Commit: e5bdceba953e2aeef14d5e44eec4c2efc9b61295
URL: https://github.com/kamailio/kamailio/commit/e5bdceba953e2aeef14d5e44eec4c2e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-01-11T14:06:50+01:00
misc/examples: updated the link to wiki site
---
Modified: misc/examples/kemi/kamailio-basic-kemi.cfg
Modified: misc/examples/mixed/kamailio-minimal-anycast.cfg
Modified: misc/examples/mixed/kamailio-minimal-proxy.cfg
Modified: misc/examples/pkg/kamailio-basic.cfg
Modified: misc/examples/pkg/kamailio-oob.cfg
Modified: misc/examples/webrtc/kamailio-default-websocket.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/e5bdceba953e2aeef14d5e44eec4c2e…
Patch: https://github.com/kamailio/kamailio/commit/e5bdceba953e2aeef14d5e44eec4c2e…
---
diff --git a/misc/examples/kemi/kamailio-basic-kemi.cfg b/misc/examples/kemi/kamailio-basic-kemi.cfg
index c9b23725aa6..b6bdfbb9398 100644
--- a/misc/examples/kemi/kamailio-basic-kemi.cfg
+++ b/misc/examples/kemi/kamailio-basic-kemi.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at http://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
# Several features can be enabled using '#!define WITH_FEATURE' directives:
diff --git a/misc/examples/mixed/kamailio-minimal-anycast.cfg b/misc/examples/mixed/kamailio-minimal-anycast.cfg
index 7ec2d98979c..40d4788f609 100644
--- a/misc/examples/mixed/kamailio-minimal-anycast.cfg
+++ b/misc/examples/mixed/kamailio-minimal-anycast.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at https://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
diff --git a/misc/examples/mixed/kamailio-minimal-proxy.cfg b/misc/examples/mixed/kamailio-minimal-proxy.cfg
index 2d5a7dc8b94..a332c12409b 100644
--- a/misc/examples/mixed/kamailio-minimal-proxy.cfg
+++ b/misc/examples/mixed/kamailio-minimal-proxy.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at https://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
diff --git a/misc/examples/pkg/kamailio-basic.cfg b/misc/examples/pkg/kamailio-basic.cfg
index fab75f25133..4c2a014425e 100644
--- a/misc/examples/pkg/kamailio-basic.cfg
+++ b/misc/examples/pkg/kamailio-basic.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at http://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
# Several features can be enabled using '#!define WITH_FEATURE' directives:
diff --git a/misc/examples/pkg/kamailio-oob.cfg b/misc/examples/pkg/kamailio-oob.cfg
index 21401eee641..075f1a65be6 100644
--- a/misc/examples/pkg/kamailio-oob.cfg
+++ b/misc/examples/pkg/kamailio-oob.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at http://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
# Several features can be enabled using '#!define WITH_FEATURE' directives:
diff --git a/misc/examples/webrtc/kamailio-default-websocket.cfg b/misc/examples/webrtc/kamailio-default-websocket.cfg
index 0fbb774eef6..8005605ff96 100644
--- a/misc/examples/webrtc/kamailio-default-websocket.cfg
+++ b/misc/examples/webrtc/kamailio-default-websocket.cfg
@@ -6,7 +6,7 @@
#
# Direct your questions about this file to: <sr-users(a)lists.kamailio.org>
#
-# Refer to the Core CookBook at https://www.kamailio.org/wiki/
+# Refer to the Core CookBook at https://www.kamailio.org/wikidocs/
# for an explanation of possible statements, functions and parameters.
#
# Note: the comments can be:
Hello,
Kamailio SIP Server v5.6.3 stable release is out.
This is a maintenance release of the latest stable branch, 5.6, that
includes fixes since the release of v5.6.2. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.6.x. Deployments running previous v5.6.x
versions are strongly recommended to be upgraded to v5.6.3.
For more details about version 5.6.3 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2023/01/kamailio-v5-6-3-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Hello,
I am considering to release Kamailio v5.6.3 (out of branch 5.6) next
week (likely on Wednesday, Jan 11, 2023). If anyone is aware of
issues not yet on the bug tracker, report them there asap in order to
have a better chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
When we send any custom header in the CANCEL Request.. same request is not forwarding to the down stream. Custom Header are missing in th request which is received by the downstream.
We are using t_relay() to forwards the request.
Please let me know if any parameters are required to be enabled for this issue.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### 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).
-->
```
(paste your log messages here)
```
#### 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).
-->
Upstream CANCEL Request Sent
----------------------------------------------
Session Initiation Protocol (CANCEL)
Request-Line: CANCEL sip:inbound@192.168.2.200:5060;transport=UDP SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.2.192:8000;branch=z9hG4bK-25588-1-0
From: <sip:inbound@192.168.2.192:8000>;tag=1
To: <sip:inbound@192.168.2.200:5060;user=phone>
Call-ID: 1-25588(a)192.168.2.192
[Generated Call-ID: 1-25588(a)192.168.2.192]
CSeq: 1 CANCEL
Max-Forwards: 70
Session-ID: 357f74433c5454178cde3d5278b40ec6
User-Agent: A175 Collaboration Tablet
Content-Length: 0
Down Stream CANCEL Request received
----------------------------------------------------
Session Initiation Protocol (CANCEL)
Request-Line: CANCEL sip:inbound@192.168.2.200:5060;transport=UDP SIP/2.0
Message Header
From: <sip:inbound@192.168.2.192:8000>;tag=1
To: <sip:inbound@192.168.2.200:5060;user=phone>
Call-ID: 1-25588(a)192.168.2.192
[Generated Call-ID: 1-25588(a)192.168.2.192]
CSeq: 1 CANCEL
Via: SIP/2.0/UDP 192.168.1.200;branch=z9hG4bK561f.944ad825d740820aeb834f49c3cea1b7.0;rport
Max-Forwards: 69
Content-Length: 0
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **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 `lsb_release -a` and `uname -a`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3326
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3326(a)github.com>
Module: kamailio
Branch: master
Commit: 72cd0ac533d4e6b881aa5e4f2e1724c6da312ca2
URL: https://github.com/kamailio/kamailio/commit/72cd0ac533d4e6b881aa5e4f2e1724c…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-01-10T13:21:27+01:00
app_python3s: checks for function execution handler
---
Modified: src/modules/app_python3s/app_python3s_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/72cd0ac533d4e6b881aa5e4f2e1724c…
Patch: https://github.com/kamailio/kamailio/commit/72cd0ac533d4e6b881aa5e4f2e1724c…
---
diff --git a/src/modules/app_python3s/app_python3s_mod.c b/src/modules/app_python3s/app_python3s_mod.c
index ba68d019e2..f2614f27a8 100644
--- a/src/modules/app_python3s/app_python3s_mod.c
+++ b/src/modules/app_python3s/app_python3s_mod.c
@@ -323,7 +323,9 @@ int apy3s_script_init_exec(PyObject* pModule, str *fname, int *vparam)
if (PyErr_Occurred()) {
LM_ERR("error exception occurred\n");
apy3s_handle_exception("script_init");
- Py_DECREF(pHandler);
+ if (pHandler != NULL) {
+ Py_DECREF(pHandler);
+ }
goto error;
}
@@ -331,11 +333,10 @@ int apy3s_script_init_exec(PyObject* pModule, str *fname, int *vparam)
LM_ERR("PyObject_CallObject() returned NULL but no exception!\n");
if (!PyErr_Occurred())
PyErr_Format(PyExc_TypeError,
- "Function '%s' of module '%s' has returned not returned"
- " object. Should be a class instance.",
+ "Function '%s' of module '%s' has not returned"
+ " an object. Should be a class instance.",
fname->s, _sr_apy3s_bname);
apy3s_handle_exception("script_init");
- Py_DECREF(pHandler);
goto error;
}
Py_XDECREF(pHandler);