Roni12q created an issue (kamailio/kamailio#4307)
hello
can you help me with my last project in my college i try to install kamailio but when i run pcscf i have many error. The point in my error is the kamailio can't find module
how the installation i make
mkdir -p /usr/local/src/
cd /usr/local/src/
git clone https://github.com/kamailio/kamailio kamailio-5.4
cd kamailio
git checkout -b 5.4 origin/5.4
i used kamailio 5.4 just like journal i found in google scholar (https://riu.ufam.edu.br/…
[View More]handle/prefix/6232) and they made it so i used it journal for my references, but the end is error.
maybe you can help me to my last project
that's mean a lot to me thank you
this the log
dragonroni@dragonroni:~$ sudo su
[sudo] password for dragonroni:
Sorry, try again.
[sudo] password for dragonroni:
root@dragonroni:/home/dragonroni# mkdir -p /var/run/kamailio_pcscfroot@dragonroni:/home/dragonroni# kamailio -f /etc/kamailio_pcscf/kamailio_pcscf.cfg -P /kamailio_pcscf.pid -DD -E -e
loading modules under config path: /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/:/usr/lib/x86_64-linux-gnu/kamailio/modules/:/usr/local/lib64/kamailio/modules
0(44774) ERROR: [core/modparam.c:164]: set_mod_param_regex(): parameter <delete_delay> of type <2:int> not found in module <ims_registrar_pcscf>
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 399, column 51: Can't set module parameter
0(44774) ERROR: [core/modparam.c:164]: set_mod_param_regex(): parameter <ipsec_preferred_ealg> of type <1:string> not found in module <ims_ipsec_pcscf>
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 417, column 59: Can't set module parameter
0(44774) ERROR: [core/modparam.c:164]: set_mod_param_regex(): parameter <recv_mode> of type <2:int> not found in module <ims_qos>
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 435, column 35: Can't set module parameter
0(44774) ERROR: [core/modparam.c:164]: set_mod_param_regex(): parameter <dialog_direction> of type <2:int> not found in module <ims_qos>
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 436, column 42: Can't set module parameter
0(44774) ERROR: [core/cfg.y:3451]: yyparse(): cfg. parser: failed to find command ipsec_destroy_by_contact (params 4)
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 935, column 129: unknown command, missing loadmodule?
0(44774) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16
0(44774) ERROR: [core/cfg.y:3451]: yyparse(): cfg. parser: failed to find command ipsec_create (params 2)
0(44774) CRITICAL: [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio_pcscf/route/register.cfg, line 264, column 77: unknown command, missing loadmodule?
ERROR: bad config file (6 errors)
0(44774) WARNING: [core/mem/q_malloc.c:487]: qm_free(): WARNING: free(0) called from cdp_avp: cdp_avp_mod.c: cdp_avp_destroy(226)
0(44774) INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child stopping ...
0(44774) INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child stopped
0(44774) ERROR: ims_ipsec_pcscf [ipsec.c:567]: clean_sa(): Error sending delete SAs command via netlink socket: No data available
0(44774) WARNING: ims_ipsec_pcscf [cmd.c:998]: ipsec_cleanall(): Error cleaning IPSec Security associations during startup.
0(44774) ERROR: ims_ipsec_pcscf [ipsec.c:609]: clean_policy(): Error sending delete policies command via netlink socket: No data available
0(44774) WARNING: ims_ipsec_pcscf [cmd.c:1002]: ipsec_cleanall(): Error cleaning IPSec Policies during startup.
0(44774) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:309]: mod_destroy(): Error destroying spi generator
0(44774) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:313]: mod_destroy(): Error destroying port generator
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4307
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4307(a)github.com>
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#100 - Assignment operators don't work
User who did this - Alex Hermann (axlh)
http://sip-router.org/tracker/index.php?do=details&task_id=100
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hello list,
Hope everyone is fine.
I'm trying to install the latest 6.0.1 version from
https://rpm.kamailio.org/centos/ but it doesn't seem to be updated...The
latest version available there is the 5.8.5. Version 6.0.0 isn't there as
well...
Is it still maintained? or just some rpmbuild command missed?
Thank you,
Patrick
… forked INVITEs auths
#### Pre-Submission Checklist
- [*] 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
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [*] New feature (non-breaking change which …
[View More]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 #[4266](https://github.com/kamailio/kamailio/issues/4266)
#### Description
If a Negative reply for forked REGISTER comes after the first 200 response, it won't be ignored by Kamailio and will be processed the same way as replies processed for the INVITEs
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4304
-- Commit Summary --
* tm: allow pending forked REGISTER auths being handled the same way as forked INVITEs auths
-- File Changes --
M src/modules/tm/t_reply.c (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4304.patchhttps://github.com/kamailio/kamailio/pull/4304.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4304
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4304(a)github.com>
[View Less]
xadhoom created an issue (kamailio/kamailio#4252)
### Description
A kamailio cluster which replicates presentities and usrloc via dmq may incur into duplicated presentities and notifications depending on config.
The problematic setup, where each kamailio node has the following setup:
- presence enabled with dmq
- usrloc distributed with dmq
- pua_reginfo used to publish reginfo to self
Really is multiplicated by the numbers of nodes, so 4 nodes -> 4 times notifications and presentities.
…
[View More]### Troubleshooting
The problem arise because pua_reginfo hooks to usrloc and every time a "save()" is done a publish is sent, which is by design. Then the handled publish generates a presentity which is replicated via dmq from presence module.
Now, if also usrloc is replicated via DMQ, the handling of such message still trigger the hook, causing another publish with generates a different presentiy, since is new and the e-tag is different.
This causes subscribers to receive <number of nodes> notifications on every status change.
### Possible Solutions
The approach can be to optionally disable that hook (basically making pua_reginfo skipping publish) when handling a message via DMQ, so the usrloc replica is just saved.
In other modules, like pua_dialoginfo or pua_usrloc this can be already done, since publishing can be controlled from script.
### Additional Information
* **Kamailio Version**
```
6.0.1
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4252
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4252(a)github.com>
[View Less]
Kudos go to Pawel Kuzak.
Redis v7.4, hashes support auto-expiry for individual keys. By transforming sets into hashes we can support auto-expiry.
Adding module parameters use_redis_hashes and expires to control the described feature.
<!-- 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 …
[View More]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, ...)
- [ ] 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)
- [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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4306
-- Commit Summary --
* db_redis: add Redis auto expiry support by changing sets to hashes
-- File Changes --
M src/modules/db_redis/db_redis_mod.c (18)
M src/modules/db_redis/doc/db_redis_admin.xml (46)
M src/modules/db_redis/redis_connection.c (47)
M src/modules/db_redis/redis_dbase.c (385)
M src/modules/db_redis/redis_dbase.h (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4306.patchhttps://github.com/kamailio/kamailio/pull/4306.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4306
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4306(a)github.com>
[View Less]