Hi everyone,
I hope you're all doing well! I'm currently working on a project where I'm integrating Kamailio with Dovecot, and I'm looking for some advice or best practices from those who have experience with this setup.
Specifically, I'm interested in how best to configure Kamailio to work seamlessly with Dovecot for handling email traffic. Any tips on optimizing performance, potential pitfalls to avoid, or resources that could guide me through the integration would be greatly appreciated.
Also, if there are any particular modules or configurations you’ve found useful, I'd love to hear about them!
https://www.igmguru.com/blog/how-to-pass-ccsp-certification-exam
Thanks in advance for your help!
Best Regards
<!-- 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
- [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
- [ ] 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/3936
-- Commit Summary --
* ims_qos_npn: fixed issues in 3GPP-User-Location-Information decoding to P-Access-Network-Info header value
-- File Changes --
M src/modules/ims_qos_npn/rx_avp.c (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3936.patchhttps://github.com/kamailio/kamailio/pull/3936.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3936
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3936(a)github.com>
Module: kamailio
Branch: master
Commit: 3debbb5a608c135c628799546ee95c96abe18824
URL: https://github.com/kamailio/kamailio/commit/3debbb5a608c135c628799546ee95c9…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-08-21T09:30:50+02:00
corex: docs for forward_uac() function
---
Modified: src/modules/corex/doc/corex_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/3debbb5a608c135c628799546ee95c9…
Patch: https://github.com/kamailio/kamailio/commit/3debbb5a608c135c628799546ee95c9…
---
diff --git a/src/modules/corex/doc/corex_admin.xml b/src/modules/corex/doc/corex_admin.xml
index 3d6ff893808..61529f94335 100644
--- a/src/modules/corex/doc/corex_admin.xml
+++ b/src/modules/corex/doc/corex_admin.xml
@@ -977,6 +977,34 @@ event_route[dispatcher:dst-down] {
xinfo("matched local socket name\n");
}
...
+</programlisting>
+ </example>
+ </section>
+ <section id="corex.f.forward_uac">
+ <title>
+ <function moreinfo="none">forward_uac()</function>
+ </title>
+ <para>
+ Forward received request with a single Via header, the one added
+ by &kamailio;, the other ones being removed. Useful in cases when
+ its reply should not be sent back (e.g., the reply was already sent
+ out from &kamailio;).
+ </para>
+ <para>
+ This function can be used in REQUEST_ROUTE.
+ </para>
+ <example>
+ <title><function>forward_uac</function> usage</title>
+ <programlisting format="linespecific">
+...
+request_route {
+ ...
+ sl_send_reply("200", "OK");
+ $du = "sip:mirror.com:5080";
+ forward_uac();
+ ...
+}
+...
</programlisting>
</example>
</section>
Yes, I commented it in the other issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/3d002d561e82b8bb71b225da708bdfd…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/3d002d561e82b8bb71b225da708bdfd9ce504335/145517761(a)github.com>