Hi,

Indeed, from what I've checked so far, the $var() value is initialized to 0. This is done when kamailio starts.

However, the issue we faced is more related to this excerpt from kamailio cookbooks, pseudovariables: ``` Note: A script variable persists over the Kamailio process in which it was initialized, so be sure of giving it a new value before reading it or you'll get the value asigned in any other previous message processed by the same Kamailio process (pid). ``` Let me know if now its more clear what the PR tries to warn.

Thank you, Stefan

@smititelu - that note from the docs sounds ok for me (maybe because I wrote it, although I am not sure I did). Practically wants to say that assign explicitly a value before using it, not to get the value set a while ago in another SIP message processing context.

If you do:

``` request_route { ... while ($var(i) < 100) { ... $var(i) = $var(i) + 1; } ... } ```

The while loop gets inside once because $var(i) is 0 first time, but then remains set to 100 for all next requests. Therefore set it to the value you want before using it:

``` request_route { ... $var(i) = 0; while ($var(i) < 100) { ... $var(i) = $var(i) + 1; } ... } ```

Feel free to change the statement in the docs, if you consider more clarifications there, but I don't see any benefit in storing an extra int field in the internal var structure.

Maybe $vn() offers better the kind of variable you need. It is like $var() but can have $null value (state).

Hi @miconda . Is it because of memory consumption that you don't want to store an additional _int_ inside the _var_ structure? The reason we came up with this PR is a strange incident we had that was rather difficult to debug because we, you could say, wrongly used script variables. Reading the docs is important, sure. But I think the project would benefit from this feature because it could help users to debug or avoid unwanted strange scenarios.

It is not an alarm, it is just a log message warning the user that he uses something that is not initialized. I once used a while(true) statement in the configuration file, which also was a valid statement and intended by me. Back then I saw that there was a warning printed when starting Kamailio. That's where I saw that Kamailio does some checking this and Perls _use strict_ statement kind of motivated us to implement this feature. Would it be OK if we would make it also configurable?

@miconda indeed you are right, but it will help in this situation: - first request has not SOME_HEADER - try to use a $var which value has not been explicitly set before => log a warning

If we start kamailio with e.g. 64 (routing) child processes there are 64 first SIP messages that might or might not have SOME_HEADER => some will print warning, some will not => if really unlucky, all will not :D

Yes, I agree. The patch is just meant to merely give you a config hint, at best effort. Won't solve the wrong value problem or change $var() behavior in any way.

Ok. I am closing the PR for now. Thanks a lot for the feedback.