[Devel] [ openser-Bugs-1544868 ] Call forward busy, segmentation fault

[SourceForge.net]

Bugs item #1544868, was opened at 2006-08-22 23:31
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1544868&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: modules
Group: ver 1.0.x
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: reticent (unspin)
>Assigned to: Bogdan (bogdan_iancu)
Summary: Call forward busy, segmentation fault

Initial Comment:
I've found a reproduceable segmentation fault during a 
simple call
forward busy scenario:
1. Terminating caller receives INVITE
2. Responds busy, OpenSER catches the 487 and re-
executes several
routing blocks
3. During a simple operation in one of these routing 
blocks (checking a
flag i believe) OpenSER is terminated with a signal 11 
and dumps core

Below is a gdb backtrace (bt, and bt full. in order) 
of the core file

Please let me know if you need any more information
This was reproduced on Openser rel 1_0_0, checked out 
of CVS this morning

----------------------------------------------------------------------

>Comment By: Bogdan (bogdan_iancu)
Date: 2006-08-23 13:26

Message:
Logged In: YES 
user_id=1275325

The problem is you are using the add_rr_param() function
from the failure route, which in 1.0.x versions is not
allowed. According to the documentation, the function must
be used only from the request route.
Most probably you have a nested calls of sub-routes from
failure route which tricks the default detection mechanism
for improper usage of function in route. If you use the -C
parameter for openser, the problem will be reported for sure.

In 1.1.0 the usage of add_rr_param is allowed from failure
route, so please upgrade.

regards,
bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1544868&group_id=139143