Module: kamailio
Branch: master
Commit: 48d97c1941f660aa396b5ef100584611cf92ad21
URL: https://github.com/kamailio/kamailio/commit/48d97c1941f660aa396b5ef10058461…
Author: Dragos Vingarzan <vingarzan(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-06-21T12:57:56+02:00
textopx/doc: fixed hard-to-read documentation for textopsx
- was missing line-wraps in examples list, hence very hard to read
---
Modified: src/modules/textopsx/doc/selects.xml
---…
[View More]
Diff: https://github.com/kamailio/kamailio/commit/48d97c1941f660aa396b5ef10058461…
Patch: https://github.com/kamailio/kamailio/commit/48d97c1941f660aa396b5ef10058461…
---
diff --git a/src/modules/textopsx/doc/selects.xml b/src/modules/textopsx/doc/selects.xml
index 6d4dd4e3a25..3c72c21cd36 100644
--- a/src/modules/textopsx/doc/selects.xml
+++ b/src/modules/textopsx/doc/selects.xml
@@ -9,30 +9,35 @@
<title>@hf_value</title>
<para>
Get value of required header-value or param. Note that functions called 'value2'
- works with Authorization-like headers where comma is not treated as value delimiter. Formats:
- @hf_value.HFNAME[IDX] # idx value, negative value counts from bottom
- @hf_value.HFNAME.PARAM_NAME
- @hf_value.HFNAME[IDX].PARAM_NAME
- @hf_value.HFNAME.p.PARAM_NAME # or .param., useful if required called "uri", "p", "param"
- @hf_value.HFNAME[IDX].p.PARAM_NAME # dtto
- @hf_value.HFNAME[IDX].uri # (< & > excluded)
- @hf_value.HFNAME[*] # return comma delimited list of all values (combines headers)
- @hf_value.HFNAME # the same as above [*] but may be parsed by cfg.y
- @hf_value.HFNAME[*].uri # return comma delimited list of uris (< & > excluded)
- @hf_value.HFNAME.uri # the same as above [*] but may be parsed by cfg.y
- @hf_value.HFNAME[IDX].name # returns name part, quotes excluded
- @hf_value.HFNAME.name # returns name part of the first value
+ works with Authorization-like headers where comma is not treated as value delimiter.
+ </para>
+ <para>
+ Formats:
+ <itemizedlist>
+ <listitem>@hf_value.HFNAME[IDX] # idx value, negative value counts from bottom</listitem>
+ <listitem>@hf_value.HFNAME.PARAM_NAME</listitem>
+ <listitem>@hf_value.HFNAME[IDX].PARAM_NAME</listitem>
+ <listitem>@hf_value.HFNAME.p.PARAM_NAME # or .param., useful if required called "uri", "p", "param"</listitem>
+ <listitem>@hf_value.HFNAME[IDX].p.PARAM_NAME # dtto</listitem>
+ <listitem>@hf_value.HFNAME[IDX].uri # (< & > excluded)</listitem>
+ <listitem>@hf_value.HFNAME[*] # return comma delimited list of all values (combines headers)</listitem>
+ <listitem>@hf_value.HFNAME # the same as above [*] but may be parsed by cfg.y</listitem>
+ <listitem>@hf_value.HFNAME[*].uri # return comma delimited list of uris (< & > excluded)</listitem>
+ <listitem>@hf_value.HFNAME.uri # the same as above [*] but may be parsed by cfg.y</listitem>
+ <listitem>@hf_value.HFNAME[IDX].name # returns name part, quotes excluded</listitem>
+ <listitem>@hf_value.HFNAME.name # returns name part of the first value</listitem>
- @hf_value2.HFNAME # returns value of first header
- @hf_value2.HFNAME[IDX] # returns value of idx's header
- @hf_value2.HFNAME.PARAM_NAME
- @hf_value2.HFNAME[IDX].PARAM_NAME
+ <listitem>@hf_value2.HFNAME # returns value of first header</listitem>
+ <listitem>@hf_value2.HFNAME[IDX] # returns value of idx's header</listitem>
+ <listitem>@hf_value2.HFNAME.PARAM_NAME</listitem>
+ <listitem>@hf_value2.HFNAME[IDX].PARAM_NAME</listitem>
- @hf_value.HFNAME[IDX].uri # return URI, quotes excluded
- @hf_value.HFNAME.p.uri # returns param named uri, not URI itself
- @hf_value.HFNAME.p.name # returns param named name, not name itself
- @hf_value.HFNAME[IDX].uri.name # any sel_any_uri nested features may be used
- @hf_value.HFNAME[IDX].nameaddr.name # select_any_nameaddr
+ <listitem>@hf_value.HFNAME[IDX].uri # return URI, quotes excluded</listitem>
+ <listitem>@hf_value.HFNAME.p.uri # returns param named uri, not URI itself</listitem>
+ <listitem>@hf_value.HFNAME.p.name # returns param named name, not name itself</listitem>
+ <listitem>@hf_value.HFNAME[IDX].uri.name # any sel_any_uri nested features may be used</listitem>
+ <listitem>@hf_value.HFNAME[IDX].nameaddr.name # select_any_nameaddr</listitem>
+ </itemizedlist>
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
[View Less]
When I start Kamailio master version that has been built on Debian 12 with default-libmysqlclient-dev depending on libmariadb-dev-compat, several warnings like this are produced:
```
2024-06-17T14:48:27.702827+03:00 siika /usr/bin/sip-proxy[297246]: WARNING: db_mysql
[km_my_con.c:187]: db_mysql_new_connection(): opt_ssl_ca option not supported by mysql
version (value (null)) - ignoring
```
The only db_mysql configuration option used in the config is ping_interval.
I would expect that the …
[View More]warnings are not produced like it is the case when I build Kamailio branch 5.8.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3884
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3884(a)github.com>
[View Less]
### Description
amqp_ssl_socket_set_*() functions are just for amqp_ssl_socket sockets
#### Reproduction
```
loadmodule "rabbitmq.so"
modparam("rabbitmq", "url", "amqp://guest:guest@rabbitmq:5672/%2Fkamailio")
```
#### Debugging Data
```
(gdb) bt
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1 0x00007fd60b427e8f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/…
[View More]pthread_kill.c:78
#2 0x00007fd60b3d8fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3 0x00007fd60b3c3472 in __GI_abort () at ./stdlib/abort.c:79
#4 0x00007fd5f5a78831 in amqp_abort (fmt=fmt@entry=0x7fd5f5a82358 "<%p> is not of type amqp_ssl_socket_t") at ./librabbitmq/amqp_api.c:183
#5 0x00007fd5f5a7f032 in amqp_ssl_socket_set_verify_peer (base=<optimized out>, verify=verify@entry=0) at ./librabbitmq/amqp_openssl.c:519
#6 0x00007fd5f5a8adf1 in rabbitmq_connect (conn=0x7fd5f5a98328 <amqp_conn>) at ./src/modules/rabbitmq/rabbitmq.c:610
#7 0x00007fd5f5a918e7 in mod_child_init (rank=-127) at ./src/modules/rabbitmq/rabbitmq.c:180
#8 0x000055ec03183a8f in init_mod_child (m=0x7fd607c8bd00, rank=-127) at core/sr_module.c:920
#9 0x000055ec031887ab in init_child (rank=rank@entry=-127) at core/sr_module.c:999
#10 0x000055ec02ff5e07 in main_loop () at ./src/main.c:1725
#11 0x000055ec02feba87 in main (argc=<optimized out>, argv=<optimized out>) at ./src/main.c:3256
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3883
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3883(a)github.com>
[View Less]
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/…
[View More]lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
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
<!--
Explain what you did, what you expected to happen, and what actually happened.
I made a test :Several volte mobile accessed into eNB, some of them made call and hung up periodically .
After some time, ims registrations all failed. I found pcscf error log below periodically when try to ims register :
2024-05-28T13:32:30.952258+08:00 spid-YL-CLU6L-V1 pcscf[13401]: ERROR: {1 750211591 REGISTER 750211591_1277609064(a)172.60.5.12} cdp [routing.c:296]: get_routing_peer(): get_routing_peer(): No connected DefaultRoute peer found for app_id 16777236 and vendor id 10415.
2024-05-28T13:32:30.952346+08:00 spid-YL-CLU6L-V1 pcscf[13401]: ERROR: {1 750211591 REGISTER 750211591_1277609064(a)172.60.5.12} cdp [diameter_comm.c:144]: AAASendMessage(): AAASendMessage(): Can't find a suitable connected peer in the routing table.
And the RX reconnection appeared periodically ,which could be found in packet capture:
2024-05-28T13:32:49.595500+08:00 spid-YL-CLU6L-V1 pcscf[13372]: INFO: cdp [receiver.c:1006]: peer_connect(): peer_connect(): Trying to connect to 127.0.0.9 port 3868
2024-05-28T13:32:49.595621+08:00 spid-YL-CLU6L-V1 pcscf[13372]: INFO: cdp [receiver.c:1106]: peer_connect(): peer_connect(): Peer pcrf.epc.mnc009.mcc460.3gppnetwork.org:3868 connected
PCRF error log periodically :
[diam] ERROR: pid:PSM/pcscf.ims.mnc009.mcc460.3gppnetwork.org in [fd_p_ce_handle_newCER@p_ce.c](mailto:fd_p_ce_handle_newCER@p_ce.c):1138: pcscf.ims.mnc009.mcc460.3gppnetwork.org: Rejecting new connection attempt while our state machine is in state 'STATE_SUSPECT'
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
Several volte mobile accessed into eNB, some of them made call and hung up periodically .
After some time, ims registrations all failed.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(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 fix.
-->
If I restarted pcscf, ims registration worked well.After some time ,the error occurred again.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
kamailio v5.6.0
* **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 `lsb_release -a` and `uname -a`)
-->
ubuntu server 18.04
```
(paste your output here)
```
[Uploading ims-reg-fail (1).zip…]()
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3879
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3879(a)github.com>
[View Less]