(Feature request)
be able to recover data from htable variable when kamailio starts, from another kamailio instances through dmq module.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/260
Apparently the default locks are set to PTHREAD mutex, when the architecture is not handled explicitely. It should be reviewed and eventually switch to standard POSIX, they should work everywhere while PTHREAD are targeting threads and work only in few cases for processes.
--
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/1035
repro servers peer with each other in a federated manner just like SMTP servers for email, but using TLS mutual authentication to prevent impersonation.
Kamailio has TLS support and should be able to talk to such servers and other Kamailio servers in the same way.
It would be good to create a recommended sample configuration for this type of service and also add it to the RTC Quick Start Guide:
http://rtcquickstart.org/guide/multi/sip-proxy.html
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/531
### Description
<!--
I want to do call drop when balance reach to 0.
so for that i am using CNXCC module and kamailio 4.2 version
now when user balance reach to 0 then i can see in log
terminate_call(): Error executing dlg_end_dlg command. Return code was [404]
Apr 1 06:49:56 sip /usr/sbin/kamailio[1316]: ALERT: cnxcc [cnxcc_check.c:81]: check_calls_by_money(): [S2N5rn7nlu] call has exhausted its credit. Breaking the loop
So my target is call disconnect when users balance reach at 0.
-->
#### Log Messages
```
terminate_call(): Error executing dlg_end_dlg command. Return code was [404]
Apr 1 06:49:56 sip /usr/sbin/kamailio[1316]: ALERT: cnxcc [cnxcc_check.c:81]: check_calls_by_money(): [S2N5rn7nlu] call has exhausted its credit. Breaking the loop
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
kamctl -v
/usr/sbin/kamctl 4.2.0
```
* **Operating System**:
```
Centos 6 64bit
```
--
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/1051
I suggest we delete the "email_address" field in database schemas for auth_db. I think it was put there as an example of extendability but a lot of users seems confused about this and Kamailio by default does not use that field at all.
Any opinions? If we reach an agreement we'll produce patches and clean up the various schemas.
--
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/858
OpenSSL is well known for huge amount of deadly security vulnerabilities, even before heartbleed.
It would be nice if I could avoid bringing in such a library just because of Kamailio - having support for GnuTLS will let the user to make such a choice.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/371
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
<!--
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