t; -Original Message-
> From: sr-users On Behalf Of Alex
> Balashov
> Sent: Thursday, September 15, 2022 09:39
> To: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] ndb_redis value substitution or escaping spaces
>
> base64 is a pretty trivial algorit
: sr-users On Behalf Of Alex Balashov
Sent: Thursday, September 15, 2022 09:39
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] ndb_redis value substitution or escaping spaces
base64 is a pretty trivial algorithm. You’d be surprised.
> On Sep 15, 2022, at 12:37 PM, Brooks Brid
Message-
> From: sr-users On Behalf Of Alex
> Balashov
> Sent: Thursday, September 15, 2022 09:11
> To: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] ndb_redis value substitution or escaping spaces
>
> A common approach to avoid delimiter issues in general is
] ndb_redis value substitution or escaping spaces
A common approach to avoid delimiter issues in general is to store
base64-encoded strings in Redis rather than the original strings. If whatever
is reading from Redis can un-encode them, that pretty well solves the problem.
> On Sep 15, 2022, at 12
A common approach to avoid delimiter issues in general is to store
base64-encoded strings in Redis rather than the original strings. If whatever
is reading from Redis can un-encode them, that pretty well solves the problem.
> On Sep 15, 2022, at 12:09 PM, Brooks Bridges wrote:
>
> I am aware
I am aware of, and have used sucessfully, the %s substitution option in
redis_cmd, however when trying to do 4 values I'm getting a parse error about
too many arguments. A review of the module's source appears to indicate that
there is a hard limit of 3 substitution values when using this
