Module: kamailio
Branch: master
Commit: 7a619c8f014a3c402942ef478ee76ce237b7e21a
URL: https://github.com/kamailio/kamailio/commit/7a619c8f014a3c402942ef478ee76ce…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-01-09T10:01:48+01:00
modules: readme files regenerated - dialog ... [skip ci]
---
Modified: src/modules/dialog/README
---
Diff: https://github.com/kamailio/kamailio/commit/7a619c8f014a3c402942ef478ee76ce…
Patch: https://github.com/kamailio/kamailio/commit/7a619c8f014a3c402942ef478ee76ce…
---
diff --git a/src/modules/dialog/README b/src/modules/dialog/README
index d3bc615b53..4e3f43e99b 100644
--- a/src/modules/dialog/README
+++ b/src/modules/dialog/README
@@ -438,9 +438,10 @@ Chapter 1. Admin Guide
2. How it works
- To create the dialog associated with an initial request, the flag
- “dlg_flag” (Section 6.4, “dlg_flag (integer)”) must be set before
- creating the corresponding transaction.
+ To create the dialog associated with an initial INVITE request, execute
+ the function “dlg_manage()” or set the flag specified by parameter
+ “dlg_flag” (Section 6.4, “dlg_flag (integer)”) before creating the
+ corresponding transaction.
The dialog is automatically destroyed when a “BYE” is received. In case
of no “BYE”, the dialog lifetime is controlled via the default timeout
@@ -623,6 +624,10 @@ modparam("dialog", "rr_param", "xyz")
Flag to be used for marking if a dialog should be constructed for the
current request (this make sense only for initial requests).
+ Note: it is not needed to set this parameter and its corresponding flag
+ for initial request in case the “dlg_manage()” function is used. In
+ other words, using “dlg_manage()” alone is enough.
+
Default value is “none”.
Example 1.4. Set dlg_flag parameter
Module: kamailio
Branch: master
Commit: e4dfe3587943d69d556b15df3492cf38c3b21a5f
URL: https://github.com/kamailio/kamailio/commit/e4dfe3587943d69d556b15df3492cf3…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-01-09T09:50:12+01:00
dialog: docs - more info about using the flag and dlg_manage()
---
Modified: src/modules/dialog/doc/dialog_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/e4dfe3587943d69d556b15df3492cf3…
Patch: https://github.com/kamailio/kamailio/commit/e4dfe3587943d69d556b15df3492cf3…
---
diff --git a/src/modules/dialog/doc/dialog_admin.xml b/src/modules/dialog/doc/dialog_admin.xml
index ca0109b31f..9adca735db 100644
--- a/src/modules/dialog/doc/dialog_admin.xml
+++ b/src/modules/dialog/doc/dialog_admin.xml
@@ -45,9 +45,10 @@
<section>
<title>How it works</title>
<para>
- To create the dialog associated with an initial request, the flag
- <quote>dlg_flag</quote> (<xref linkend="dialog.p.flag"/>) must be set before
- creating the corresponding transaction.
+ To create the dialog associated with an initial INVITE request, execute
+ the function <quote>dlg_manage()</quote> or set the flag specified by
+ parameter <quote>dlg_flag</quote> (<xref linkend="dialog.p.flag"/>)
+ before creating the corresponding transaction.
</para>
<para>
The dialog is automatically destroyed when a <quote>BYE</quote> is
@@ -256,6 +257,12 @@ modparam("dialog", "rr_param", "xyz")
current request (this make sense only for initial requests).
</para>
<para>
+ Note: it is not needed to set this parameter and its corresponding flag
+ for initial request in case the <quote>dlg_manage()</quote> function
+ is used. In other words, using <quote>dlg_manage()</quote> alone is
+ enough.
+ </para>
+ <para>
<emphasis>
Default value is <quote>none</quote>.
</emphasis>
<!-- 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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1792
-- Commit Summary --
* Modules: rtpengine-rtpengine_query exported to ksr routes
-- File Changes --
M src/modules/rtpengine/rtpengine.c (20)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1792.patchhttps://github.com/kamailio/kamailio/pull/1792.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/1792
Ubuntu 18.04 & Kamailio V 5.1
I am unable to start kamailio services due the below error.
● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server
Loaded: loaded (/lib/systemd/system/kamailio.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-01-08 22:36:49 UTC; 12s ago
Process: 12933 ExecStart=/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GROUP (code=exited, status=255)
Main PID: 12877 (code=exited, status=0/SUCCESS)
Jan 08 22:36:49 kamatl03 kamailio[12933]: udp: kamatl03:5060
Jan 08 22:36:49 kamatl03 kamailio[12933]: udp: localhost:5060
Jan 08 22:36:49 kamatl03 kamailio[12933]: udp: localhost.localdomain:5060
Jan 08 22:36:49 kamatl03 /usr/sbin/kamailio[12955]: INFO: carrierroute [carrierroute.c:213]: mod_init(): use file as configuration source
Jan 08 22:36:49 kamatl03 /usr/sbin/kamailio[12955]: ERROR: carrierroute [carrierroute.c:215]: mod_init(): can't stat config file
Jan 08 22:36:49 kamatl03 /usr/sbin/kamailio[12955]: ERROR: <core> [core/sr_module.c:986]: init_mod(): Error while initializing module carrierroute (/usr/lib/x86_64-linu
Jan 08 22:36:49 kamatl03 /usr/sbin/kamailio[12955]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Jan 08 22:36:49 kamatl03 systemd[1]: kamailio.service: Control process exited, code=exited status=255
Jan 08 22:36:49 kamatl03 systemd[1]: kamailio.service: Failed with result 'exit-code'.
Jan 08 22:36:49 kamatl03 systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server.
***********************Here is the Module Selection in configuraiton file***************
####### Modules Section ########
# set paths to location of modules (to sources or installation folders)
#!ifdef WITH_SRCPATH
mpath="/usr/local/lib64/kamailio/modules"
#!else
mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/"
#!endif
--
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/1798
Hi,
I have the following architecture - SIP provider <-> Kamailio <-> Asterisk
servers
Currently I have everything setup and incoming calls from Sip are routed to
my asterisk server. The issue is however that when I answer the call, there
is no media in the call. I have tried connecting with a normal local
extension(not SIP,eg 1001) and there is a normal flow of media.
When i try to sniff my connection via Wireshark on the asterisk server,
there is an outflow of RTP packets but the same RTP traffic does not appear
on the Wireshark of my Kamailio server connection.
I am not sure if this is an RTP engine issue and how to resolve this.
I have -
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:45038")
this in my kamailio cfg but I don;t know which port to use here.
Any suggestions?
### Description
If an AVP containing a regex is passed to the t_check_status function, it does not match.
Example:
```
failure_route[DEFAULT]
{
$avp(FAILURE_CODES) = "5[0-9][0-9]";
xlog("L_WARN", "Status code: $T_reply_code\n");
if ($avp(FAILURE_CODES) != $null)
{
xlog("L_WARN", "resp codes regex: $avp(FAILURE_CODES)\n");
if (t_check_status("$avp(FAILURE_CODES)"))
{
xlog("L_WARN", "t_check_status matched\n");
}
}
}
```
#### Reproduction
Using the code above in a failure_route should match a 500 response, but it does not.
### Possible Solutions
The fixup_t_check_status in tm.c:663 attempts to match FPARAM_AVP/FPARAM_SELECT/FPARAM_REGEX parameter types.
If another check for the FPARAM_PVS parameter type then the issue appears fixed
--
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/1795