<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
I have a scenario where FS routes hundreds of calls and loop
detection is needed. Adding to that, I can't rely on hop counter
being decremented by other network elements. I can use limit in the
following fashion:<br>
<br>
<action application="limit" data="hash loop_test
${caller_id_number}${destination_number} 10
!NORMAL_CIRCUIT_CONGESTION"/><br>
<br>
So, whenever I have 10 calls with the same calling and called party
number combination, limit will kick-in and break the loop.<br>
<br>
<b>Question</b>: Is this efficient from the perspective of how
"limit" and hash back-end work? Once I have a few thousand calls,
all having unique "resource" will this become resource hungry?<br>
My main concern is that it will create hundreds of hash entries all
having the same realm but unique resource.<br>
<br>
Anyone knows a better solution?<br>
<br>
Thank you,<br>
Victor<br>
</body>
</html>