Module: kamailio
Branch: master
Commit: 8762c56a1c78e4ba151ef9fb4290b3938c0c984f
URL: https://github.com/kamailio/kamailio/commit/8762c56a1c78e4ba151ef9fb4290b39…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-07-06T10:01:24+02:00
modules: readme files regenerated - acc ... [skip ci]
---
Modified: src/modules/acc/README
---
Diff: https://github.com/kamailio/kamailio/commit/8762c56a1c78e4ba151ef9fb4290b39…
Patch: https://github.com/kamailio/kamailio/commit/8762c56a1c78e4ba151ef9fb4290b39…
---
diff --git a/src/modules/acc/README b/src/modules/acc/README
index baff8e8b32..da1da0331c 100644
--- a/src/modules/acc/README
+++ b/src/modules/acc/README
@@ -131,7 +131,6 @@ Sven Knoblich
7.1. acc_log_request(comment)
7.2. acc_db_request(comment, table)
7.3. acc_request(comment, table)
- 7.4. acc_diam_request(comment)
2. Frequently Asked Questions
@@ -188,7 +187,6 @@ Sven Knoblich
1.49. acc_log_request usage
1.50. acc_db_request usage
1.51. acc_db_request usage
- 1.52. acc_diam_request usage
Chapter 1. Admin Guide
@@ -287,7 +285,6 @@ Chapter 1. Admin Guide
7.1. acc_log_request(comment)
7.2. acc_db_request(comment, table)
7.3. acc_request(comment, table)
- 7.4. acc_diam_request(comment)
1. Overview
@@ -298,9 +295,9 @@ Chapter 1. Admin Guide
support for radius is enabled.
There is some very early support of the Diameter protocol in the
- “acc_diameter” module which will be deleted in coming releases. This
- support is not up to date with the current Diameter protocols. If you
- need Diameter support, please use the ims_charging module.
+ “acc_diameter” module, but is not up to date with the current Diameter
+ protocols. If you need Diameter support, please use the ims_charging
+ module.
To account a transaction and to choose which set of backends to be
used, the script writer just has to set some flags (see the module
@@ -1326,7 +1323,6 @@ modparam("acc", "cdr_on_failed", 0)
7.1. acc_log_request(comment)
7.2. acc_db_request(comment, table)
7.3. acc_request(comment, table)
- 7.4. acc_diam_request(comment)
7.1. acc_log_request(comment)
@@ -1394,23 +1390,6 @@ acc_request("100 Received", "acc_$time(year)_$time(mon)");
acc_db_request("$var(code) $avp(reason)", "acc");
...
-7.4. acc_diam_request(comment)
-
- Like acc_log_request, acc_diam_request reports on a request. It reports
- to the configured Diameter server.
-
- Meaning of the parameters is as follows:
- * comment - Comment to be appended. The string can contain any number
- of pseudo-variables.
-
- This function can be used from ANY_ROUTE.
-
- Example 1.52. acc_diam_request usage
-...
-acc_diam_request("Some comment");
-acc_diam_request("$var(code) Error: $avp(reason)");
-...
-
Chapter 2. Frequently Asked Questions
2.1. What happened with old log_fmt parameter
Module: kamailio
Branch: master
Commit: 402515c92238c3628c78a2b44ac0a05130897207
URL: https://github.com/kamailio/kamailio/commit/402515c92238c3628c78a2b44ac0a05…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-07-06T09:59:57+02:00
acc: docs - removed acc_diam_request() section
- it is now exported by acc_diameter
---
Modified: src/modules/acc/doc/acc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/402515c92238c3628c78a2b44ac0a05…
Patch: https://github.com/kamailio/kamailio/commit/402515c92238c3628c78a2b44ac0a05…
---
diff --git a/src/modules/acc/doc/acc_admin.xml b/src/modules/acc/doc/acc_admin.xml
index f88d403d2b..41935c8dae 100644
--- a/src/modules/acc/doc/acc_admin.xml
+++ b/src/modules/acc/doc/acc_admin.xml
@@ -23,10 +23,9 @@
</para>
<para>
There is some very early support of the <acronym>Diameter</acronym>
- protocol in the <quote>acc_diameter</quote> module which will be deleted
- in coming releases. This support is not up to date with the current
- Diameter protocols. If you need Diameter support, please use the
- <acronym>ims_charging</acronym> module.
+ protocol in the <quote>acc_diameter</quote> module, but is not up to date
+ with the current Diameter protocols. If you need Diameter support,
+ please use the <acronym>ims_charging</acronym> module.
</para>
<para>
To account a transaction and to choose which set of backends to be
@@ -1555,37 +1554,6 @@ acc_request("100 Received", "acc");
acc_request("100 Received", "acc_$time(year)_$time(mon)");
acc_db_request("$var(code) $avp(reason)", "acc");
...
-</programlisting>
- </example>
- </section>
- <section id="acc.f.acc_diam_request">
- <title>
- <function moreinfo="none">acc_diam_request(comment)</function>
- </title>
- <para>
- Like <function moreinfo="none">acc_log_request</function>,
- <function moreinfo="none">acc_diam_request</function> reports on
- a request. It reports to the configured Diameter server.
- </para>
- <para>
- Meaning of the parameters is as follows:</para>
- <itemizedlist>
- <listitem>
- <para><emphasis>comment</emphasis> - Comment to be appended.
- The string can contain any number of pseudo-variables.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- This function can be used from ANY_ROUTE.
- </para>
- <example>
- <title>acc_diam_request usage</title>
- <programlisting format="linespecific">
-...
-acc_diam_request("Some comment");
-acc_diam_request("$var(code) Error: $avp(reason)");
-...
</programlisting>
</example>
</section>
#### Pre-Submission Checklist
- [x] 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)
- [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
- [ ] 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:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Wireshark project allows embedding session encryption keys into PCAP files. So it allows parsing encrypted packets as it was unencrypted.
[More info](https://blog.didierstevens.com/2021/01/11/decrypting-tls-streams-with…
I prepared a change that allows export session encryption keys.
Please review PR. If ok, then I add commits with DocBook info.
Kyys may be emeberd using command
```
editcap --inject-secrets tls,/var/lib/kamailio/session_keylog encrypted.pcap with_keys.pcapng
```
As prototype used
https://github.com/openssl/openssl/blob/master/apps/lib/s_cb.c#L1480-L1525
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2785
-- Commit Summary --
* tls: added new session_keylog_enable and session_keylog_filename configuration params
* tls: first interation of session key logger
* tls: added logs output
-- File Changes --
M src/modules/tls/tls_cfg.c (6)
M src/modules/tls/tls_cfg.h (2)
M src/modules/tls/tls_init.c (79)
M src/modules/tls/tls_init.h (2)
M src/modules/tls/tls_mod.c (2)
M src/modules/tls/tls_rpc.c (2)
M src/modules/tls/tls_server.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2785.patchhttps://github.com/kamailio/kamailio/pull/2785.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/2785
Hello,
As mobile applications based on kamailio are growing exponentially on Play Store and App Store, i would suggest if you could add by default the code for ios/android push notifications.
I have problems mainly for incoming call (phone wakeup) on linphone iphone app, as kamailio is missing the push solution. On Android i am using Baresip and works perfect without push.
Navigating on the web, i found some uncomplete or minimum tutorials to implement this.
Like: https://denys-pozniak.medium.com/apple-push-notification-with-kamailio-eeca…
And also some code snippets of a modification of "kamailio.cfg" to add support for ios push notifications. (see below).
Could someone have this already working? Or kamailio official developers could add this by default inside source code?
`# keep a record of an IPhone for 4 hours
modparam("htable", "htable", "iphone_remote=>size=10;autoexpire=14400;")
modparam("htable", "htable", "iphone_voip=>size=10;autoexpire=14400;")
modparam("htable", "htable", "iphone_check=>size=10;autoexpire=14400;")
modparam("htable", "htable", "vtp=>size=10;autoexpire=120;")
route[REGISTRAR] {
...
...
if (save("location")) {
# user registered, now look at the useragent header for iPhone string
if ($hdr(User-Agent)=~"LinphoneiOS.*") {
$var(uri) = @contact.uri; # select the uri from contact header
$var(pn-prid) = $(var(uri){uri.param,pn-prid}); # get the uri param pn-prid from the uri, i.e. 1DF26BC10F597676B
xlog("!!!! - $var(pn-prid)");
$var(i) = 0;
$var(n) = $(var(pn-prid){s.count,&});
while( $var(i) <= $var(n)) {
$var(pn-prid_item) = $(var(pn-prid){s.select,$var(i),&});
$var(pn-prid_type) = $(var(pn-prid_item){s.select,1,:});
$var(pn-prid_token) = $(var(pn-prid_item){s.select,0,:});
if ( $var(pn-prid_type) == "remote" ) {
$var(pn-prid_remote) = $(var(pn-prid_item){s.select,0,:}) ;
}
if ( $var(pn-prid_type) == "voip" ) {
$var(pn-prid_voip) = $(var(pn-prid_item){s.select,0,:}) ;
}
$var(i) = $var(i) + 1;
}
xlog("L_INFO","iPhone PUSH tokens for user $fU - remote: $var(pn-prid_remote), voip: $var(pn-prid_voip)");
# store the values of tokens to htable with fromUser as key
$sht(iphone_remote=>$fU) = $var(pn-prid_remote);
$sht(iphone_voip=>$fU) = $var(pn-prid_voip);
$sht(iphone_check=>$fU) = 1;
if ( $sht(vtp=>id_index::$tU) != $null ) {
xlog("L_INFO", "New $rm ru=$ru tu=$tu \n");
route(JOIN);
}
} else {
# no iphone
$sht(iphone_check=>$fU) = 0;
}
...
...
}
route[LOCATION] {
...
...
if (!lookup("location")) {
$var(rc) = $rc;
# handle PUSH notifications for iPhone
# iphones should not be registered and contacts stored in database
# hence lookup should fail and we need to try to push iphone first
if ($sht(iphone_check=>$tU) == 1) {
xlog("L_ERR", "[PUSH] The to user has already used iPhone, trying push notifications");
xlog("L_ERR", "[PUSH] No registration to try, suspending.");
sl_send_reply("100", "Suspending");
route(SUSPEND);
route(RELAY);
exit;
}
...
...
if (is_method("INVITE")) {
setflag(FLT_ACCMISSED);
# handle PUSH notifications for iPhone
# in some cases, iphone does not send de-register when going to background
# for these circumstances, push iphone even if it has an active registration
if ($sht(iphone_check=>$tU) == 1) {
xlog("L_ERR", "[PUSH] The to user has already used iPhone, trying push notifications");
xlog("L_ERR", "[PUSH] No registration to try, suspending.");
sl_send_reply("100", "Suspending");
route(SUSPEND);
}
}
route(RELAY);
exit;
}
route[SUSPEND] {
if ( !t_suspend() ) {
xlog("L_ERROR","[SUSPEND] failed suspending trasaction [$T(id_index):$T(id_label)]\n");
send_reply("501", "Suspending error");
exit;
} else {
xlog("L_INFO","[SUSPEND] suspended transaction [$T(id_index):$T(id_label)] $fU=> $rU\n");
$sht(vtp=>id_index::$rU) = $T(id_index);
$sht(vtp=>id_label::$rU) = $T(id_label);
xlog("L_INFO","[SUSPEND] htable key value [$sht(vtp=>id_index::$rU) -- $sht(vtp=>id_label::$rU)]\n");
route(SENDPUSH);
exit;
}
}
route[SENDPUSH] {
#http_client_query("http://url/push.php"<http://url/push.php>, "user=$rU\r\npn-tok=$sht(tokens=>$rU)\r\n","Content-Type: text/plain", "$var(result)");
xlog("!!!!!!!!!!!!!!!!!!!!!! PUSH !!!!!!!!!!!!!!!!!!!");
xlog("/opt/push/push.sh $ci $sht(iphone_voip=>$tU)");
exec_avp("/opt/push/push.sh $ci $sht(iphone_voip=>$tU)");
xlog("!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!");
sl_send_reply("100", "Pushing");
}
route[JOIN] {
xlog("L_WARN","[JOIN] htable key value [$sht(vtp=>id_index::$tU) -- $sht(vtp=>id_label::$tU)]\n");
t_continue("$sht(vtp=>id_index::$tU)", "$sht(vtp=>id_label::$tU)", "RESUME");
$sht(vtp=>joined::$tU) = 1;
}
route[RESUME] {
lookup("location");
xlog("L_INFO","[RESUME] rm=$rm ru=$ru du=$du \n");
t_relay();
$sht(vtp=>id_index::$tU) = $null;
$sht(vtp=>id_label::$tU) = $null;
exit; }
`
--
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/2793