Re: [SR-Users] Unquoted values from #!defenv

And hindsight is always 20/20. The initial question was about this: !!defenv HOME . . . event_route[evrexec:timer] { xlog("L_N", "HOME: " + HOME + "\n"); } $def(HOME) would work. Ben Kaufman Sr. VoIP Engineer P: E: bkauf...@bcmone.com 24 hour clien

Re: [SR-Users] Unquoted values from #!defenv

> it is empty string followed by token 'bar' and followed by another empty > string. OK. It makes perfect sense when viewed that way. Ben Kaufman Sr. VoIP Engineer P: E: bkauf...@bcmone.com 24 hour client support: 855.639.6300 From: Daniel-Constantin Mierla Sent: Th

Re: [SR-Users] Unquoted values from #!defenv

#!defines are preprocessor directives, think about them like copy+paste and then config interpreter tries to understand the config content. As one example in the wiki, the value of a define can be even a script snippet -- see the define of IDLOOP:   * https://www.kamailio.org/wiki/cookbooks/5.5.x

Re: [SR-Users] Unquoted values from #!defenv

Sorry, I noticed the file discrepancy after sending the email. I did make sure to retest with #!defenvs and it does work. With regards to quoted/unquoted envvars, I'm not expecting that a quoted environmental variable would do anything with the quotes, but right now, Kamailio will fail to star

Re: [SR-Users] Unquoted values from #!defenv

The example snippet you gave is with #!devenv, not with #!devenvs. Is it what you tested in this case? Cheers, Daniel On 09.12.21 15:57, Ben Kaufman wrote: > > Thank you.  It’s tested and working with this simple config: > >   > >   > > #!KAMAILIO > > loadmodule "xlog" > loadmodule "pv" > loadmod

Re: [SR-Users] Unquoted values from #!defenv

If the value is already quoted, then #!devenv should be used, that's the reason there are two variants to take it as it is or surround with quotes. Cheers, Daniel On 09.12.21 17:50, Ben Kaufman wrote: > > It does appear that #!devenvs subsequently has problems if the > environmental variable is a

Re: [SR-Users] Unquoted values from #!defenv

It does appear that #!devenvs subsequently has problems if the environmental variable is already quoted, though. I'll put together an example and open a ticket for it. From: Ben Kaufman Sent: Thursday, December 9, 2021 8:57 AM To: Kamailio (SER) - Users Mailing List Subject: RE: [SR-Users] Un

Re: [SR-Users] Unquoted values from #!defenv

Thank you. It's tested and working with this simple config: #!KAMAILIO loadmodule "xlog" loadmodule "pv" loadmodule "evrexec" modparam("evrexec", "exec", "name=evrexec:timer;wait=1000;workers=1;") #!defenv HOME request_route{ forward(); } event_route[evrexec:timer] { xlog("L_N", "HO

Re: [SR-Users] SRTP/DTLS + RTP Header encryption

Has anyone tried encrypting RTP headers in SRTP ? On Wed, Dec 8, 2021, 7:44 AM Rahul mm wrote: > Hi guys, > > Is it possible to achieve RTP header encryption along with payload in > SRTP/DTLS ? > So far what I've been able to see is RTP payload encryption. > I'm using kamailo 5.5.0 and rtpengine

Re: [SR-Users] Unquoted values from #!defenv

I pushed the code to enclose the value in between quotes. Can you test and see if works now? Cheers, Daniel On 08.12.21 19:07, Daniel-Constantin Mierla wrote: > > I expected the quoted mode parameter does the work -- I will check and > push the update. > > Regarding support for undefined env valu