>From debian bugreport https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892538
```
Source: kamailio
Severity: serious
Tags: sid buster
User: debian-gcc(a)lists.debian.org
Usertags: gcj-rm
Hi,
kamailio depends or build-depends on GCJ. GCJ has been dropped
upstream since GCC 7, so we are dropping it from Debian. Thus please
either drop support for GCJ if you are just building an alternative
package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to
default-jdk / default-jre as appropriate.
Cheers, Emilio
```
>From https://gcc.gnu.org/gcc-7/changes.html
```
Java (GCJ)
The GCC Java frontend and associated libjava runtime library have been removed from GCC.
```
Can the ``app_java`` module be built with openjdk-9-jdk?
--
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/1487
If I run set_contact_alias nothing happens - the contact remains the same on the outbound message There's no error returned and debug logs indicate a proper header
However, if I add "msg_apply_changes()" on the line after set_contact_alias the Contact sent to next hop has the alias content No other changes
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/445
### Description
Yealink phones is subscribes using `application/dialog-info+xml`. In this case for many phones false reported `early` state.
### Troubleshooting
#### Reproduction
Not knows. Some phones is displayes properly, some is not.
#### Debugging Data
none
#### Log Messages
not yet done
#### SIP Traffic
In provided pcap. is subscribed two clients `yealink` phone and `x-lite` softphone.
Created call to extension 201 (sip login). For `x-lite` status is changed properly for `yealink` is not.
Filters
`udp.port==13322` caller leg
`udp.port==1025` callee legs
`udp.srcport==5060&&udp.dstport==5060` yealink phone
`udp.port==15502` xlite
[blf-test.pcap.gz](https://github.com/kamailio/kamailio/files/1849284/blf-te…
packet 14 - kamailio reports 201 extension is Available to xlite
packet 25 - kamailio reports 201 is early to yealink (unexpected)
packet 108 - created call to 201 extension
packer 109 - ringing to caller
packet 118 - kamailio send ringing to caller
packet 119 - INVITE send to callee
packet 124 - callee send Trying
packet 127 - kamailio reports 201 is ringing to yalink
packet 129 - kamailio reports 201 is busy to xlite
packet 145 - kamailio send session progress to caller
packet 146 - callee send ringing
packet 154 - caller send cancel
packet 156 - kamailio send early to yealink (unexpected)
packet 156 - kamailio send Available to x-lite
### Possible Solutions
not known
### Additional Information
Kamailio installed from kazoo team repo
```
[root@kamailio01 ~]# kamailio -V
version: kamailio 5.0.3 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 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 on 11:07:05 Sep 23 2017 with gcc 4.8.5
[root@kamailio01 ~]#
```
* **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`)
-->
```
[root@kamailio01 ~]# uname -a
Linux kamailio01.cloudpbx.ai.co.uk 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@kamailio01 ~]# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
[root@kamailio01 ~]#
```
--
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/1489
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests.
If you have questions about using Kamailio or related to its configuration file,
ask on sr-users mailing list:
* http://lists.sip-router.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.sip-router.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 you submit a feature request (or enhancement), you can delete the text of
the template and only add the description of what you would like to be added.
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 I-CSCF Kamailio module with 5.0.1 version we got the error:
"I_perform_user_authorization_request(): no int value param passed"
Same configuration file works well on 5.0.0 version
<!--
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
1(26715) ERROR: *** cfgtrace:request_route=[register] c=[/etc/KAMAILIO_ASTERISK_CFG/IMS_5/icscf/./kamailio.cfg] l=374 a=26 n=I_perform_user_authorization_request
1(26715) ERROR: <core> [core/sr_module.c:1766]: get_int_fparam(): Unexpected param type: 1280329042
1(26715) ERROR: ims_icscf [registration.c:78]: I_perform_user_authorization_request(): no int value param passed
1(26715) ERROR: *** cfgtrace:request_route=[register] c=[/etc/KAMAILIO_ASTERISK_CFG/IMS_5/icscf/./kamailio.cfg] l=375 a=26 n=send_reply
[log_ko.gz](https://github.com/kamailio/kamailio/files/961675/log_ko.gz)
[kamailio.cfg.txt](https://github.com/kamailio/kamailio/files/961677/kamaili…
<!--
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).
-->
```
(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 `uname -a`)
-->
```
(paste your output 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/1099
Hi,
we're trying to have scalable Kamailio nodes that are stateless.
That means that we can for example load dispatchers and reload them from an API endpoint.
Now we're stuck on the dialog part. All our nodes load the dialogs from a shared db, what happens when a node gets down is that a packet reaches another node and does not know how to handle that because the dialog does not have it's ip address. Also there is no possibility to reload the dialogs from db so that we could update the records in the db and have the dialogs ip changed on an anctive node's ip.
Is there a possibility to have a function to reload the dialogs from db on a running kamailio?
--
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/1274
Hello,
I'm using keepalive module with drouting module... the event route works fine:
NOTICE: <script>: Gateway up: OPTIONS sip:1.2.3.4
NOTICE: <script>: Gateway up: OPTIONS sip:5.6.7.8
but kamcmd command not:
kamcmd keepalive.list
foobar
42
foobar
42
{
text: foobar
number: 42
}
{
list: {
nn: 17
nn: 22
}
}
{
uri: sip:1.2.3.4
owner: drouting
last checked: Wed Feb 21 11:20:12 2018
last up: Wed Dec 31 19:00:00 1969
last down: Wed Feb 21 11:20:13 2018
}
{
uri: sip:5.6.7.8
owner: drouting
last checked: Wed Feb 21 11:20:12 2018
last up: Wed Dec 31 19:00:00 1969
last down: Wed Feb 21 11:20:12 2018
Thank you
Regards...
--
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
Hello,
in many modules we have a template text about our support contacts in the
"FAQ" part:
"E-mails regarding any stable Kamailio release should be sent to
<sr-users(a)lists.kamailio.org> and e-mails regarding development
versions should be sent to <sr-dev(a)lists.kamailio.org>.
If you want to keep the mail private, send it to
<sr-users(a)lists.kamailio.org>."
The lower part (about the private contact) makes no sense anymore. It used
contain a private SER contact address, and lost somehow its meaning during the
conversion to Kamailio.
I would like to change to this text to:
"If you need to keep the e-mail private (e.g. for security issues) send it to
management at kamailio dot org."
Any objections against this change, or remarks about the replacement text?
Regards,
Henning
- add support for OpenSSL engine and loading private keys from HSM
- for when kamailio is a TLS edge proxy and needs to use HSM
- currently we initialize the engine in worker processes as PKCS#11
libraries are not guaranteed to be fork() safe
- new config params
- engine: name the OpenSSL engine
- engine_config: an OpenSSL config format file used to bootstrap engines
- engine_algorithms: list of algorithms to delegate to the engine
- tested with Gemalto SafeNet Luna (AWS CloudHSM) with RSA and EC private keys
TLSv1.2 and PFS cipher suites
<!-- 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
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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 -->
- add support for OpenSSL engine and loading private keys from HSM
- for when kamailio is a TLS edge proxy and needs to use HSM
- currently we initialize the engine in worker processes as PKCS#11
libraries are not guaranteed to be fork() safe
- new config params
- engine: name the OpenSSL engine
- engine_config: an OpenSSL config format file used to bootstrap engines
- engine_algorithms: list of algorithms to delegate to the engine
- tested with Gemalto SafeNet Luna (AWS CloudHSM) with RSA and EC private keys
TLSv1.2 and PFS cipher suites
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1484
-- Commit Summary --
* tls: add support for OpenSSL engine and private keys in HSM
-- File Changes --
M src/modules/tls/tls_domain.c (178)
M src/modules/tls/tls_mod.c (91)
M src/modules/tls/tls_mod.h (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1484.patchhttps://github.com/kamailio/kamailio/pull/1484.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/1484