I am going
to have to go with the "upgrade" crowd in this one. Running
OpenSER 1.3 at this point is like running a libc5-based Linux
distro. Almost no advice or discussion is relevant to it
because there have been such tectonic, generational shifts
since.
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Atlanta, GA 30030
Tel: +1-678-954-0671
Web: http://www.evaristesys.com/,
http://www.alexbalashov.com
Edson - Lists <
4lists@gmail.com>
wrote:
>Please upgrade to latest stable and try again....
>
>Why? If you have to ask it, than you didn't got it...
>
>new version === new functionalities
>
>99% of list support and tips are based on last stable
version. 1.3 is
>pretty old...
>
>Edson.
>
>Em 23/03/2012 10:06, Robert R escreveu:
>> Hi,
>>
>> Even though when I try to use "uac_replace_from( )"
in branch_route
>> block I get the same error message:
>>
>> branch_route[2]
>> {
>> if ( $avp(i:204) )
>> {
>> uac_replace_from("hello");
>> }
>>
>> }
>>
>>
>> error message:
>>
>> Not starting openser: invalid configuration file!
>> Mar 23 09:03:00 [7542] CRITICAL:core:yyerror: parse
error in config
>> file, line 623, column 26-27: Command cannot be
used in the block
>> Mar 23 09:03:00 [7542] ERROR:core:main: bad config
file (1 errors)
>>
>> PS: I am running an old release of openser 1.3.
>>
>> Thanks,
>> R
>>
>>
>>
>>
>> On Thu, Mar 22, 2012 at 1:23 PM, Daniel-Constantin
Mierla
>> <
miconda@gmail.com
<mailto:
miconda@gmail.com>>
wrote:
>>
>>
>>
>> On 3/22/12 6:12 PM, Alex Balashov wrote:
>>
>> On 03/22/2012 01:00 PM, Robert R wrote:
>>
>> When I am trying to modify FROM field
in the "failure_route"
>> block I
>> get an error message:
>>
>> failure_route[1]
>> {
>> ...
>> append_branch();
>> t_relay();
>> }
>>
>> Not starting openser: invalid
configuration file!
>> Mar 22 10:51:39 [6457]
CRITICAL:core:yyerror: parse error in
>> config
>> file, line 662, column 32-33: Command
cannot be used in the
>> block
>> Mar 22 10:51:39 [6457]
ERROR:core:main: bad config file (1
>> errors)
>>
>>
>> You can probably get around it this way:
>>
>> failure_route[1]
>> {
>> ...
>>
>> append_branch();
>>
>> route(STUFF);
>> t_relay();
>> }
>>
>>
>> route[STUFF]
>> {
>> uac_replace_from(...);
>> }
>>
>> indeed this should work -- it is no reason of
not being usable in
>> failure_route, perhaps is so from the time of
development. The
>> function itself is allowed in branch_route
which is called from
>> inside t_relay() (when t_on_branch(...) is
used), therefore we can
>> relax the restriction for failure_route, imo.
>>
>> One thing to take care of, if you use
uac_replace_from() in request
>> route and then in failure route, you may end
in malformed format, so
>> it is recommended to use it in branch_route,
then the changes done
>> by the function will be per each forwarded
branch.
>>
>> Cheers,
>> Daniel
>>
>> --
>> Daniel-Constantin Mierla
>> Kamailio Advanced Training, April 23-26,
2012, Berlin, Germany
>> http://www.asipto.com/index.__php/kamailio-advanced-__training/
>> <http://www.asipto.com/index.php/kamailio-advanced-training/>
>>
>>
>>
>> _________________________________________________
>> SIP Express Router (SER) and
Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
>> http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users