Hi Max, > *you need to enable creation of core files* Please let me know how to do that ?
I'm really busy these days + my scenario is now in production, so it will be a bit hard for me to test. However, I will setup the same scenario on different server and collect the requested information. I should be able to do that in the next 2 or 3 weeks, so please excuse me in advance about the delay :) Thanks -- Kamen On 19 February 2011 02:36, Maxim Sobolev <[email protected]> wrote: > On 2/11/2011 9:56 AM, Kamen Petrov wrote: > >> I have been suggested by the opensips developers to raise that issue to >> your attention. >> >> My SIP network topology is as follow: >> 1) origination IP >> 2) opensips proxy >> 3) opensips running in b2b mode >> 4) termination IP >> >> I am running opensips trunk version currently with RTPproxy version >> 1.2.0. I have been running the latest RTPproxy version before but >> switched back to 1.2.0 mostly because the logging wasn't working good >> with the latest version. The issue I'm going to report have been noticed >> with both latest version and 1.2.0. >> >> So, on the opensips proxy (that is point 2 from the call flow), I am >> running the following configuration: >> > > Kamen, > > It would be nice if you can send a stack trace for that crash. To do so you > need to enable creation of core files and then run the following command > after the proxy has crashed: > > $ gdb rtpproxy /path/to/rtpproxy.core > gdb> bt > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: [email protected] > Skype: SippySoft >
_______________________________________________ Devel mailing list [email protected] http://lists.rtpproxy.org/mailman/listinfo/devel
