i try script:
```
$var(some_string) = 'a=foo1;b=foo2;c=foo3,4,5;d=3';
$var(c_value) = $(var(some_string){param.value,c,;});
xlog("L_INFO", "'c' param from '$var(some_string)' is '$var(c_value)'");
```
in log:
> 'c' param from 'a=foo1;b=foo2;c=foo3,4,5;d=3' is 'foo3'
Has this behaviour any reason? or it's possible to delete comma from stop list (and use separator parameter for comma-delimited list)?
```
diff --git a/parser/parse_param.c b/parser/parse_param.c
index b9e0fbc..e7784c8 100644
--- a/parser/parse_param.c
+++ b/parser/parse_param.c
@@ -355,7 +355,6 @@ static inline int parse_token_param(str* _s, str* _r, char separator)
case '\t':
case '\r':
case '\n':
- case ',':
/* So if you find
* any of them
* stop iterating
```
---
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/648
The actual implementation is based on the cfg actions, so when there is no 'return' action defined the route flow detected is wrong.
---
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/569
If I enable dialog module Kamailio will fail to start with following error:
ERROR: dialog [dialog.c:498]: mod_init(): no dlg flag set!!
In the documentation this parameter is set to 4 as an example:
modparam("dialog", "dlg_flag", 4)
But no comments made as to why number 4 is used, which numbers are possible to use and most importantly - why such default value is chosen?
In any case - module should use default which does not break server's configuration.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/372
(Feature request)
be able to recover data from htable variable when kamailio starts, from another kamailio instances through dmq module.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/260
repro servers peer with each other in a federated manner just like SMTP servers for email, but using TLS mutual authentication to prevent impersonation.
Kamailio has TLS support and should be able to talk to such servers and other Kamailio servers in the same way.
It would be good to create a recommended sample configuration for this type of service and also add it to the RTC Quick Start Guide:
http://rtcquickstart.org/guide/multi/sip-proxy.html
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/531
OpenSSL is well known for huge amount of deadly security vulnerabilities, even before heartbleed.
It would be nice if I could avoid bringing in such a library just because of Kamailio - having support for GnuTLS will let the user to make such a choice.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/371
If I run set_contact_alias nothing happens - the contact remains the same on the outbound message There's no error returned and debug logs indicate a proper header
However, if I add "msg_apply_changes()" on the line after set_contact_alias the Contact sent to next hop has the alias content No other changes
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/445