Re: [reSIProcate-users] Assert0) inside TransactionState

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Hi Julio,

There is a serious bug in 1.7 for Windows.  Please make sure you don't use the tarball download and that you use the subversion path instead.  See the bolded note here:   http://www.resiprocate.org/ReSIProcate_1.7_Release 

Scott

On Wed, Mar 7, 2012 at 2:17 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi,

 

  We have a Windows 7  UA application built on top of recon.

 

  We are seeing the following problem: When it has a established call and receives a REFER that requests a transfer of that call, the new SIP call is placed and, roughly 30 seconds after being answered by the target, a crash happens inside TransactionState::processStateless(), line 780 (the "assert(0)" after "delete timer").

    

  This crash, of course, happens only with the Debug build of the application; in the Release buid the same assert(0) line is hit but as asserts are not compiled into release Builds the bug occurs silently.

 

  As far as our tests have shown, this behaviour only happens when using reSIProcate release 1.7,  not with reSIProcate release 1.6.

 

 

 

  As I get more data about this issue I will post here, or if someone of the list requests some additional information.

 

 

Best Regards,

Julio.

 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/