<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.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.kamailio.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) 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
Currently uac_reg_lookup don't have provision to pass the mode parameter but its implement in core fuction:
https://github.com/kamailio/kamailio/blob/951c9ac9adaccc1c35e152593cb3c2e7f…
This should be imported to kemi as well as cfg function.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Expected behavior
lookup in uacreg should be supported using username based also, currently uuid based support is only there.
#### Actual observed behavior
#### Debugging Data
```
(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 improvement.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
5.4.5
```
(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/2714
Module: kamailio
Branch: master
Commit: 624da2b7deb2539064be70a7566783fd36a15886
URL: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-05-07T08:09:11+02:00
uac: docs for uac_reg_lookup_uri()
---
Modified: src/modules/uac/doc/uac_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
Patch: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
---
diff --git a/src/modules/uac/doc/uac_admin.xml b/src/modules/uac/doc/uac_admin.xml
index 352d038ea2..52362af1e3 100644
--- a/src/modules/uac/doc/uac_admin.xml
+++ b/src/modules/uac/doc/uac_admin.xml
@@ -1005,6 +1005,31 @@ if(uac_reg_lookup("$rU", "$ru"))
{
lookup("location");
}
+...
+ </programlisting>
+ </example>
+ </section>
+ <section id="uac.f.uac_reg_lookup_uri">
+ <title>
+ <function moreinfo="none">uac_reg_lookup_uri(uri, dst)</function>
+ </title>
+ <para>
+ This function sets the PV dst to SIP URI that correspond to the URI user
+ in uac registrations table. The uri can contain pseudo-variables and
+ dst must be the name of a pseudo-variable.
+ </para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>uac_reg_lookup_uri</function> usage</title>
+ <programlisting format="linespecific">
+...
+
+if(uac_reg_lookup("$var(uri)", "$ru"))
+{
+ lookup("location");
+}
...
</programlisting>
</example>
```
LD (gcc) [M app_lua_sr.so] app_lua_sr.so
CC (gcc) [M lwsc.so] lwsc_mod.o
lwsc_mod.c: In function 'lwsc_get_endpoint':
lwsc_mod.c:533:13: error: 'struct lws_context_creation_info' has no member named 'ws_ping_pong_interval'
533 | ep->crtinfo.ws_ping_pong_interval = 5; /*secs*/
| ^
make[2]: *** [../../Makefile.rules:100: lwsc_mod.o] Error 1
make[1]: *** [Makefile:511: modules] Error 1
make[1]: Leaving directory '/root/rpmbuild/BUILD/kamailio-5.5.0/src'
make: *** [Makefile:34: every-module] Error 2
```
--
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/2727
With several days before releasing v5.5.0, let's see if there is any tuning that should be done to default kamailio.cfg.
Note that the proposals and discussions must focus around current config, if any loaded module should have different values for parameters, if the routing blocks should be adjusted to cope better with common use cases.
This is not for asking refactoring or adding major changes/features. In such cases, the option is to make PR to add to `misc/examples/` (new files or to existing files).
>From the discussions done for 5.4.0, the next were considered for the future, however I haven't seen much activity on the community forums related to them during past months, so I am not sure they worth at this moment, but let list them for a starting point:
* keepalive to be done with usrloc module to get round trip timer, etc
* dlgs module loaded to see the basic stats about active calls
--
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/2719