I have been trying to replace the SDP connection IP with some other IP using module `mangler` (`Kamailio v5.7.0`). But It seem like its malfunctioning
```
if ($rs == 200) {
xlog("L_INFO", "200 $rm Detected");
sdp_mangle_ip("192.168.0.132/24","8.8.8.8");
}
```
and results I received are like this below
```
v=0 o=- 107808851201429815 2 IN IP4 192.168.0.132
s=- t=0 0
m=audio 24794 RTP/AVP 0 8 101
c=IN IP4 192.168.0.1328.8.8.8
a=mid:audio
a=sendrecv
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=ssrc:822878909 cname:0ZfUBhl8cMeHaeVl
a=nortpproxy:yes
```
I first ask the same question in mailing list `sr-users(a)lists.kamailio.org` but after waiting for some time (>24hrs) i cant see my question on on forum, that why I open a ticket here.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3554
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3554(a)github.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:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
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
I have some buggy devices that get upset by SRTP payloads in SDP that are marked inactive. As a hack, I was attempting to delete them when going to certain endpoints that are known to be problematic:
```
if (is_method("INVITE"))
sdp_remove_transport("RTP/SAVP");
```
### Troubleshooting
Per below, there is some garbage that looks like a port number inserted before `m=audio` that seems to have come from rtpproxy rewriting for NAT traversal. Removing the NAT traversal rewrite logic entirely fixes the problem, but also makes NAT traversal not happen. Changing the order of `sdp_remove_transport()` with respect to `rtpproxy_manage()` does not change anything.
#### Reproduction
This was seen with a Grandstream DP752 phone talking to SEMS, but applying the code snippet above and getting a packet trace will be enough. The original SDP had the RTP/SAVP transport first, followed by an RTP/AVP one. For the problem to occur, NAT SDP rewriting has to occur using rtpproxy.
#### Debugging Data
Here is the payload after sfp_remove_transport() removed the RTP/SAVP section:
```
v=0
o=15176190619 8000 8000 IN IP4 X.X.X.X
s=SIP Call
c=IN IP4 X.X.X.X
t=0 0
46108m=audio 55082 RTP/AVP 125 9 0 8 2 18 97 101
a=sendrecv
a=rtpmap:125 opus/48000/2
a=fmtp:125 maxplaybackrate=16000
a=ptime:20
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16,32-36,54
a=nortpproxy:yes
```
There is a garbage 46108 (I think what would have been the port number for SAVP data) at the beginning of the m=audio line. It seems that the rewrite by rtpproxy is still inserting this port number even though the transport in question has been removed.
#### Log Messages
None relevant.
#### SIP Traffic
(See above)
### Possible Solutions
None.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
$ kamailio -v
version: kamailio 5.6.2 (x86_64/freebsd) 54a9c1
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, 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, select, kqueue.
id: 54a9c1
compiled on 10:44:33 Jul 20 2023 with cc FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
```
* **Operating System**:
FreeBSD 13.2
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3555
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3555(a)github.com>
Module: kamailio
Branch: master
Commit: b6979b503ffe65314526a8a2824f50b3f46b7a22
URL: https://github.com/kamailio/kamailio/commit/b6979b503ffe65314526a8a2824f50b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: The Root <root(a)kamailio.org>
Date: 2023-09-05T12:46:08+02:00
modules: readme files regenerated - tm ... [skip ci]
---
Modified: src/modules/tm/README
---
Diff: https://github.com/kamailio/kamailio/commit/b6979b503ffe65314526a8a2824f50b…
Patch: https://github.com/kamailio/kamailio/commit/b6979b503ffe65314526a8a2824f50b…
---
diff --git a/src/modules/tm/README b/src/modules/tm/README
index 0b44b81813c..19f4a9a3781 100644
--- a/src/modules/tm/README
+++ b/src/modules/tm/README
@@ -1864,11 +1864,12 @@ modparam("tm", "failover_reply_codes", "code=403;code=488;class=5")
4.1. t_relay([host, port])
- Relay a message statefully either to the destination indicated in the
- current URI (if called without any parameters) or to the specified host
- and port. In the later case (host and port specified) the protocol used
- is the same protocol on which the message was received. It creates a
- transaction.
+ Relay a SIP request statefully either to the destination indicated in
+ the current URI (if called without any parameters) or to the specified
+ host and port. In the later case (host and port specified) the protocol
+ used is the same protocol on which the message was received. It creates
+ the SIP transaction, if none was created before (e.g., with
+ t_newtran()).
t_relay() is the stateful version for forward() while t_relay(host,
port) is similar to forward(host, port).
#### 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)
- [x] 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
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
I am not very familiar with the build/packaging process but I'm hoping we can get `jwt` module packaged for debian since the dependencies (`libjwt`) already ship with most recent debian distributions. Any feedback would be appreciated here, thanks.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3556
-- Commit Summary --
* jwt: build jwt module for debian distributions
-- File Changes --
M pkg/kamailio/deb/bionic/rules (1)
M pkg/kamailio/deb/bookworm/rules (1)
M pkg/kamailio/deb/bullseye/rules (1)
M pkg/kamailio/deb/buster/rules (1)
M pkg/kamailio/deb/debian/rules (1)
M pkg/kamailio/deb/focal/rules (1)
M pkg/kamailio/deb/jammy/rules (1)
M pkg/kamailio/deb/jessie/rules (1)
M pkg/kamailio/deb/precise/rules (1)
M pkg/kamailio/deb/sid/rules (1)
M pkg/kamailio/deb/stretch/rules (1)
M pkg/kamailio/deb/trusty/rules (1)
M pkg/kamailio/deb/wheezy/rules (1)
M pkg/kamailio/deb/xenial/rules (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3556.patchhttps://github.com/kamailio/kamailio/pull/3556.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3556
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3556(a)github.com>
Halo Experts,
So sorry to disturb you for the kamailio start failure issue I faced recently when doing patching from version 5.5.4 to 5.5.6. Really appreciated if you could give me some assistance on it ! And attached is the start log. Thanks.
Best regards,
Louis LIU
Senior Software Engineer (Cloud Platform && Audio/Video Intercom) M +86 18575580920 8F-A CES Building,No.3099
Global Offer Innovation E bin.liu2(a)se.com<mailto:bin.liu2@se.com> Keyuan South Road, Nanshan District
Home & Distribution Division, Energy Management Shenzhen, China
[cid:image001.png@01D9CAE5.A472D190]
Download mySchneider app<https://www.se.com/ww/en/work/support/myschneider-app/> 24/7 support Mobile catalog. Acces to expert help.
Internal
<!-- 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This PR fixes the conversion from UCS2 to UTF-8 and viceversa. Previously the code was not handling emojis and certain characters.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3546
-- Commit Summary --
* smsops: Fix conversion from UCS-2 to UTF-8 and viceversa
-- File Changes --
M src/modules/smsops/smsops_impl.c (219)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3546.patchhttps://github.com/kamailio/kamailio/pull/3546.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3546
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3546(a)github.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
I loaded module "db_postgres.so". I expected kamilio to start. It didn't
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### config file
```
#!KAMAILIO
#!define WITH_POSTGRESSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_PRESENCE
#!define WITH_MSGREBUILD
#!define WITH_NAT
#!define WITH_NATSIPPING
..
.
..
#!ifdef WITH_POSTGRESSQL
loadmodule "db_postgres.so"
#!endif
```
#### 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).
-->
```
Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [db.c:204]: db_bind_mod(): Module db_postgresql not found. Missing loadmodule?
Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: usrloc [usrloc_mod.c:361]: mod_init(): failed to bind database module
Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so)
```
output from ls of modules directory:
```
acc.so call_obj.so dialog.so ipops.so msrp.so presence_conference.so qos.so sipcapture.so statsd.so uid_avp_db.so
acc_diameter.so carrierroute.so dialplan.so jsonrpcs.so mtree.so presence_dialoginfo.so ratelimit.so sipdump.so stun.so uid_domain.so
alias_db.so cfg_db.so dispatcher.so keepalive.so nat_traversal.so presence_mwi.so regex.so sipjson.so tcpops.so uid_gflags.so
app_jsdt.so cfg_rpc.so diversion.so kemix.so nathelper.so presence_profile.so registrar.so sipt.so textops.so uid_uri_db.so
app_sqlang.so cfgt.so dmq.so kex.so nosip.so presence_reginfo.so rls.so siptrace.so textopsx.so uri_db.so
async.so cfgutils.so dmq_usrloc.so lcr.so outbound.so presence_xml.so rr.so siputils.so timer.so userblocklist.so
auth.so corex.so domain.so log_custom.so p_usrloc.so pua.so rtimer.so sl.so tm.so usrloc.so
auth_db.so counters.so domainpolicy.so lrkproxy.so path.so pua_bla.so rtjson.so sms.so tmrec.so xcap_client.so
auth_diameter.so ctl.so drouting.so mangler.so pdb.so pua_dialoginfo.so rtpengine.so smsops.so tmx.so xcap_server.so
auth_xkeys.so db2_ops.so enum.so matrix.so pdt.so pua_reginfo.so rtpproxy.so speeddial.so topoh.so xhttp.so
avp.so db_cluster.so evrexec.so maxfwd.so permissions.so pua_rpc.so sanity.so sqlops.so topos.so xhttp_prom.so
avpops.so db_flatstore.so exec.so mediaproxy.so pike.so pua_usrloc.so sca.so ss7ops.so tsilo.so xhttp_rpc.so
benchmark.so db_postgres.so group.so mohqueue.so pipelimit.so pua_xmpp.so sdpops.so sst.so uac.so xlog.so
blst.so db_text.so htable.so mqueue.so prefix_route.so pv.so seas.so statistics.so uac_redirect.so xprint.so
call_control.so debugger.so imc.so msilo.so presence.so pv_headers.so secfilter.so statsc.so uid_auth_db.so
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
tried renaming db_postgres.so to db_postgresql.so, but that didn't work, so I reversed it
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.4 (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: unknown
compiled with gcc 10.2.1
```
* **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`)
-->
```
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Linux opensips 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3196
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3196(a)github.com>
I noticed that sometimes the trunk registration just fails after TTL expiry and the kamailio tries to resolve an A record for next_hop=<sip:reg.sip-trunk.telekom.de:5060;transport=tcp> where actually no A record exists resulting in an unregistered trunk for one register period. After the one failed period the SRV will result in correct CNAME resolving again and the trunk will be registered for one full hour (baes on TTL expiry of SRV record).
```
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: uac [uac_reg.c:1138]: uac_reg_send(): using custom socket tcp:10.124.2.2:5060 to send request
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/socket_info.c:702]: grep_sock_info(): checking if host==us: 10==10 && [10.124.2.2] == [10.124.2.2]
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/socket_info.c:709]: grep_sock_info(): checking if port 5060 (advertise 5060) matches port 5060
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: tm [h_table.c:580]: tm_xdata_replace(): replace existing list in backup xd from new xd
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: tm [h_table.c:413]: build_cell(): created new cell 0x7fc7766aa400
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: tm [h_table.c:568]: tm_xdata_replace(): restore X/AVP msg context from backup data
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: tm [uac.c:468]: t_uac_prepare(): next_hop=<sip:reg.sip-trunk.telekom.de:5060;transport=tcp>
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:534]: _dns_hash_find(): (_sip._tcp.reg.sip-trunk.telekom.de(34), 33), h=666
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/resolve.c:999]: get_record(): skipping 0 NS (p=0x560cf3e135dc, end=0x560cf3e135dc)
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/resolve.c:1012]: get_record(): parsing 0 ARs (p=0x560cf3e135dc, end=0x560cf3e135dc)
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:1640]: dns_get_related(): (0x7fc7766f9ab8 (_sip._tcp.reg.sip-trunk.telekom.de, 33), 33, *(nil)) (0)
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:746]: dns_cache_add_unsafe(): adding _sip._tcp.reg.sip-trunk.telekom.de(34) 33 (flags=0) at 666
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:534]: _dns_hash_find(): (reg.sip-trunk.telekom.de(24), 1), h=400
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/resolve.c:784]: get_record(): lookup(reg.sip-trunk.telekom.de, 1) failed
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:768]: dns_cache_mk_bad_entry(): (reg.sip-trunk.telekom.de, 1, 60, 1)
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: <core> [core/dns_cache.c:708]: dns_cache_add(): adding reg.sip-trunk.telekom.de(24) 1 (flags=1) at 400
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: ERROR: <core> [core/resolve.c:1730]: sip_hostport2su(): could not resolve hostname: "reg.sip-trunk.telekom.de"
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "reg.sip-trunk.telekom.de"
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: ERROR: tm [uac.c:491]: t_uac_prepare(): no socket found
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: DEBUG: tm [h_table.c:132]: free_cell_helper(): freeing transaction 0x7fc7766aa400 from uac.c:632
Aug 21 16:55:57 seelze-iptel1 kamailio[4116711]: ERROR: uac [uac_reg.c:1178]: uac_reg_send(): failed to send request for [siptrunk]
```
At this point it should not try to resolve reg.sip-trunk.telekom.de but instead one of the SRV CNAMES.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3547
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3547(a)github.com>
### Description
I want debug memory usage by TLS module.
To do this used command
```
make -C src/modules/tls CFLAGS="-DTLS_MALLOC_DBG=1"
```
And this output
```
[root@sbc-stage-a0 kamailio]# make -C src/modules/tls CFLAGS="-DTLS_MALLOC_DBG=1"
make: Entering directory '/root/bak/kamailio/src/modules/tls'
CC (gcc) [M tls.so] tls_domain.o
CC (gcc) [M tls.so] tls_rand.o
CC (gcc) [M tls.so] tls_map.o
CC (gcc) [M tls.so] tls_cfg.o
CC (gcc) [M tls.so] tls_mod.o
CC (gcc) [M tls.so] tls_util.o
CC (gcc) [M tls.so] tls_config.o
CC (gcc) [M tls.so] tls_server.o
CC (gcc) [M tls.so] tls_select.o
CC (gcc) [M tls.so] tls_dump_vf.o
CC (gcc) [M tls.so] tls_init.o
tls_init.c:137:2: warning: #warning "tls module compiled with malloc debugging info (extra overhead)" [-Wcpp]
#warning "tls module compiled with malloc debugging info (extra overhead)"
^~~~~~~
tls_init.c: In function ‘ser_malloc’:
tls_init.c:218:5: warning: implicit declaration of function ‘_shm_malloc’; did you mean ‘shm_malloc’? [-Wimplicit-function-declaration]
p=_shm_malloc(size+s, file, "via ser_malloc", line);
^~~~~~~~~~~
shm_malloc
tls_init.c:218:4: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
p=_shm_malloc(size+s, file, "via ser_malloc", line);
^
tls_init.c:224:39: error: invalid application of ‘sizeof’ to incomplete type ‘struct qm_frag’
((struct qm_frag*)((char*)p-sizeof(struct qm_frag)))->func=
^~~~~~
tls_init.c: In function ‘ser_realloc’:
tls_init.c:253:5: warning: implicit declaration of function ‘_shm_realloc’; did you mean ‘shm_realloc’? [-Wimplicit-function-declaration]
p=_shm_realloc(ptr, size+s, file, "via ser_realloc", line);
^~~~~~~~~~~~
shm_realloc
tls_init.c:253:4: warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
p=_shm_realloc(ptr, size+s, file, "via ser_realloc", line);
^
tls_init.c:259:39: error: invalid application of ‘sizeof’ to incomplete type ‘struct qm_frag’
((struct qm_frag*)((char*)p-sizeof(struct qm_frag)))->func=
^~~~~~
tls_init.c: In function ‘tls_pre_init’:
tls_init.c:684:7: warning: implicit declaration of function ‘CRYPTO_set_mem_ex_functions’; did you mean ‘CRYPTO_set_mem_functions’? [-Wimplicit-function-declaration]
if (!CRYPTO_set_mem_ex_functions(ser_malloc, ser_realloc, ser_free)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~
CRYPTO_set_mem_functions
tls_init.c:684:60: error: ‘ser_free’ undeclared (first use in this function); did you mean ‘sk_free’?
if (!CRYPTO_set_mem_ex_functions(ser_malloc, ser_realloc, ser_free)) {
^~~~~~~~
sk_free
tls_init.c:684:60: note: each undeclared identifier is reported only once for each function it appears in
make: *** [../../Makefile.rules:100: tls_init.o] Error 1
make: Leaving directory '/root/bak/kamailio/src/modules/tls'
```
### Additional Information
kamailio 5.6.4 with some customisation
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3532
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3532(a)github.com>