I clicked on send button before finishing...too much work :P If I change "nat.uac" for an uppercase version, such as NAT_UAC, fixup function does not complain.... 2006/11/8, samuel <samu60(a)gmail.com>om>:

SER tries to see if you specified directly a number or a pre-declared flag (possibly specified with "flag: flag_name_1[:number] [other flag specs...];" config directive) in your modparam. If you specified a flag string, the function str2s that tries number conversion fails (and misleadingly prints an "ERROR" prefixed message on the debug level). If you didn't specify that flag with "flag: ...;" directive, the flag is 'automatically' registered by modparam (but I would advise to declare it with the directive, as the cfg gets easier readable). Flag names do not support `.'. HTH, Bogdan. samuel wrote: -- Bogdan Pintea iptego GmbH - VoIP Security http://www.iptego.de

Hi Samuel, the document is my job. 1) I noticed that flags with "." cannot be used with cookie filter when I was completing the document, but the rest worked without problem for me. In what occasion do you get this error? ( level of debug in ser.cfg?, any compile time options for debugging?) I agree I might have missed the error at debug level, but flags containing "." works for me. I will have look at it for sure. 2) you can change it to different unix socket such as /var/run/rtpproxy.sock. It's up to you. Lada samuel wrote: > Bogdan, Thank you very much! > > Greger, can you try to update the "Optimizing the use of RTP Proxy > document" so people don't get confused (flag containing . and > declaring the flags in advance)?? > other comments: > rtpproxy hast /tmp/foo as "default" fifo interconnection and it will > fail if you just start rtpproxy...do you thing it can be usefull to > change it to the default /var/run/rtpproxy.sock?? > > Regards, > Samuel. > > 2006/11/9, Bogdan Pintea &lt;pintea(a)iptego.de&gt;de>: >> SER tries to see if you specified directly a number or a pre-declared >> flag (possibly specified with "flag: flag_name_1[:number] [other flag >> specs...];" config directive) in your modparam. >> >> If you specified a flag string, the function str2s that tries number >> conversion fails (and misleadingly prints an "ERROR" prefixed >> message on >> the debug level). >> >> If you didn't specify that flag with "flag: ...;" directive, the >> flag is >> 'automatically' registered by modparam (but I would advise to >> declare it >> with the directive, as the cfg gets easier readable). >> >> Flag names do not support `.'. >> >> >> HTH, >> Bogdan. >> >> samuel wrote: >> > My own reply... >> > >> > I mised the flags definition (NEWS file): >> > >> > (...) >> > - added named flags, declared at the beginning of the config file >> with: >> > flags flag1_name[:position], flag2_name ... >> > Example: >> > flags test, a:1, b:2 ; >> > route{ >> > setflag(test); >> > if (isflagset(a)){ # equiv. to isflagset(1) >> > .... >> > } >> > resetflag(b); # equiv. to resetflag(2) >> > (...) >> > >> > It still give me the str2s ERROR but SER starts. I have to check yet >> > if the flags are properly used in the config file >> > >> > Samuel. >> > 2006/11/8, samuel &lt;samu60(a)gmail.com&gt;om>: >> >> I clicked on send button before finishing...too much work :P >> >> >> >> If I change "nat.uac" for an uppercase version, such as NAT_UAC, >> fixup >> >> function does not complain.... >> >> >> >> 2006/11/8, samuel &lt;samu60(a)gmail.com&gt;om>: >> >> > I can not use "nat.uac" and "nat.uas" as registrar flags: >> >> > >> >> > 0(12872) str2s: ERROR: unexpected char N in NATuac >> >> > 0(12872) set_mod_param_regex: 'registrar' matches module >> 'registrar' >> >> > 0(12872) find_param_export: found <load_nat_flag> in module >> registrar >> >> > [/usr/local/lib/ser/modules/registrar.so] >> >> > 0(12872) set_mod_param_regex: found <load_nat_flag> in module >> >> > registrar [/usr/local/lib/ser/modules/registrar.so] >> >> > 0(12872) str2s: ERROR: unexpected char N in NATuas >> >> > >> >> >> > _______________________________________________ >> > Serusers mailing list >> > Serusers(a)lists.iptel.org >> > http://lists.iptel.org/mailman/listinfo/serusers >> > >> >> >> -- >> Bogdan Pintea >>

Have you read Bogdan's post?? He explained quite well the reason of the error in the log and why it works even if you do not declare it explicitely as flags in the config file. Samuel. 2006/11/9, Ladislav Andel &lt;ladaan(a)iptel.org&gt;rg>: > I forgot to say. Thanks for the feedback. > But it still gives me the same error "str2s" as you are mentioning. > I have tried to check out all possibilities of defining flags at my > testing SER, but getting the same result. str2s error. > Again, it works for me even if I don't declare "flags" lines at the > beginning of the script (even with the parsing string error in the log) > > Any other comments from developers? > > Lada > > > Ladislav Andel wrote: > > Hi Samuel, > > the document is my job. > > > > 1) I noticed that flags with "." cannot be used with cookie filter > > when I was completing the document, but the rest worked without > > problem for me. > > In what occasion do you get this error? ( level of debug in ser.cfg?, > > any compile time options for debugging?) > > I agree I might have missed the error at debug level, but flags > > containing "." works for me. > > I will have look at it for sure. > > > > 2) you can change it to different unix socket such as > > /var/run/rtpproxy.sock. It's up to you. > > > > Lada > > > > > > samuel wrote: > >> Bogdan, Thank you very much! > >> > >> Greger, can you try to update the "Optimizing the use of RTP Proxy > >> document" so people don't get confused (flag containing . and > >> declaring the flags in advance)?? > >> other comments: > >> rtpproxy hast /tmp/foo as "default" fifo interconnection and it will > >> fail if you just start rtpproxy...do you thing it can be usefull to > >> change it to the default /var/run/rtpproxy.sock?? > >> > >> Regards, > >> Samuel. > >> > >> 2006/11/9, Bogdan Pintea &lt;pintea(a)iptego.de&gt;de>: > >>> SER tries to see if you specified directly a number or a > pre-declared > >>> flag (possibly specified with "flag: flag_name_1[:number] [other > flag > >>> specs...];" config directive) in your modparam. > >>> > >>> If you specified a flag string, the function str2s that tries number > >>> conversion fails (and misleadingly prints an "ERROR" prefixed > >>> message on > >>> the debug level). > >>> > >>> If you didn't specify that flag with "flag: ...;" directive, the > >>> flag is > >>> 'automatically' registered by modparam (but I would advise to > >>> declare it > >>> with the directive, as the cfg gets easier readable). > >>> > >>> Flag names do not support `.'. > >>> > >>> > >>> HTH, > >>> Bogdan. > >>> > >>> samuel wrote: > >>> > My own reply... > >>> > > >>> > I mised the flags definition (NEWS file): > >>> > > >>> > (...) > >>> > - added named flags, declared at the beginning of the config file > >>> with: > >>> > flags flag1_name[:position], flag2_name ... > >>> > Example: > >>> > flags test, a:1, b:2 ; > >>> > route{ > >>> > setflag(test); > >>> > if (isflagset(a)){ # equiv. to isflagset(1) > >>> > .... > >>> > } > >>> > resetflag(b); # equiv. to resetflag(2) > >>> > (...) > >>> > > >>> > It still give me the str2s ERROR but SER starts. I have to > check yet > >>> > if the flags are properly used in the config file > >>> > > >>> > Samuel. > >>> > 2006/11/8, samuel &lt;samu60(a)gmail.com&gt;om>: > >>> >> I clicked on send button before finishing...too much work :P > >>> >> > >>> >> If I change "nat.uac" for an uppercase version, such as NAT_UAC, > >>> fixup > >>> >> function does not complain.... > >>> >> > >>> >> 2006/11/8, samuel &lt;samu60(a)gmail.com&gt;om>: > >>> >> > I can not use "nat.uac" and "nat.uas" as registrar flags: > >>> >> > > >>> >> > 0(12872) str2s: ERROR: unexpected char N in NATuac > >>> >> > 0(12872) set_mod_param_regex: 'registrar' matches module > >>> 'registrar' > >>> >> > 0(12872) find_param_export: found <load_nat_flag> in module > >>> registrar > >>> >> > [/usr/local/lib/ser/modules/registrar.so] > >>> >> > 0(12872) set_mod_param_regex: found <load_nat_flag> in module > >>> >> > registrar [/usr/local/lib/ser/modules/registrar.so] > >>> >> > 0(12872) str2s: ERROR: unexpected char N in NATuas > >>> >> > > >>> >> > >>> > _______________________________________________ > >>> > Serusers mailing list > >>> > Serusers(a)lists.iptel.org > >>> > http://lists.iptel.org/mailman/listinfo/serusers > >>> > > >>> > >>> > >>> -- > >>> Bogdan Pintea >

First of all, apologies Ladislav, I thought Greger was doing the document from the onsip times...and since the doc is not signed I just guessed. I have debug at maximum so I can get all possible errors (9, which is more than the upper limit I think :P) I haven't time to test NAT staff but it seems that it might work... About the rtpproxy socket, I just mentioned because if people find the document and start using it as config file there'll be a new top-10 question in the list: "rtpproxy does not work" because the socket is not the rtpproxy default socket. Samuel.

http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy Ladislav Andel wrote: _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers