[SR-Users] htable shtcn expressions

[Brooks Bridges]

5.4.1 on this dev system, I will update it to the most recent 5.4.x and see if anything changes and if not look at going up to 5.5.x, thanks!


-----Original Message-----
From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Fred Posner
Sent: Friday, October 29, 2021 7:34 AM
To: sr-users at lists.kamailio.org
Subject: Re: [SR-Users] htable shtcn expressions

On 10/29/21 2:28 AM, Brooks Bridges wrote:
> That was my understanding of how it should work as well, however in my
> testing it does not appear to be working that way.
>
> e.g. if there is a key of "+18884441111” in my dataset and I do
> $shtcn(htablename=>~%8884441111) I get a count of 0.
>
> As far as regex, I am trying to avoid that as I was told many years
> ago that regex is inherently slow when compared to other operations in
> Kamailio.  I was told this by someone I trust as an authority, and
> since this is a quite high volume system (greater than 1500 requests
> per second at peak load), every millisecond matters.

What version are you running?

My test with 5.5:

$sht(a=>+18884441111) = 1;

xlog("L_INFO","match right 111 $shtcn(a=>~%111)"); xlog("L_INFO","match left 111 $shtcn(a=>%~111)"); xlog("L_INFO","match left +1 $shtcn(a=>%~+1)"); xlog("L_INFO","match right 444111 $shtcn(a=>~%4441111)");


kamailio[12832]: INFO: match right 111 1
kamailio[12832]: INFO: match left 111 0
kamailio[12832]: INFO: match left +1 1
kamailio[12832]: INFO: match right 444111 1


Fred Posner | palner.com
Matrix: @fred:matrix.lod.com
o: +1 (212) 937-7844

Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.