Re: [SR-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null)

2017-03-27 Thread Ginhoux, Patrick
-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null) Hello, $var(...) don't hold null values, they start initialed to 0 and they are reset to 0 (when assigning $null to them) -- this is the design from the beginning which brings benefits in many situation when one doesn

Re: [SR-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null)

2017-03-27 Thread Daniel-Constantin Mierla
Hello, $var(...) don't hold null values, they start initialed to 0 and they are reset to 0 (when assigning $null to them) -- this is the design from the beginning which brings benefits in many situation when one doesn't get a chance to init. If you want a similar variable that works with null,

[SR-Users] Important problem with this test : if ($var(i:maxRangeInx)==$null)

2017-03-27 Thread Ginhoux, Patrick
Hi, I'm continue my job to 'migrate' my 3.3.1 kamailio.cfg script on a RHEL 6.2 server to the 5.0.x kamailio version on a RHEL 7.1 server, and I encounter a major problem with the '== $null' test in the script. My original script (3.3.1) contains this sequence : $var(i:rangeInx)=0;