Hello All, Another idea you might wish to consider: Regarding amplification of "900 Internal NUA Error" logging: What I did locally to the nua_client_init_request() function of libsofia-sip-ua/nua/nua_stack.c is to set a local variable before each "goto error" statement so that I know which one caused the failure (there are 7 gotos). Then I included this number in the call to nua_client_return() invocation, so that the log looks like:
event r_invite 900 Internal NUA Error (1) at ../../../libsofia-sip-ua/nua/nua_stack.c:2354 The "(1)" above indicates which goto caused the error. Best Regards, Jerry -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, January 18, 2008 8:22 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: sofia-sip-devel@lists.sourceforge.net Subject: RE: [Sofia-sip-devel] FW: Determining cause of 900 Internal NUAError Hi, >>That is, the following: >>Add uniqueness to all uses of NUA_INTERNAL_ERROR like, >> nua_stack_event(nua, nh, NULL, e, NUA_INTERNAL_ERROR >> "at" __FILE__ ":" __LINE__, NULL); > >__LINE__ is naked int, not a string... Sure, some stringizing #weirdness is necessary. BR, Mikhail ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
