Re: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation Fault If AORContains Two '*'
Hi, >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On >Behalf Of ext Jerry Richards >Sent: Thursday, October 04, 2007 10:11 PM >To: sofia-sip-devel@lists.sourceforge.net >Subject: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation >Fault If AORContains Two '*' > >Does anyone know why I get a Segmentation Fault if I call >nua_handle() or >nua_invite() with an NUTAG_URL() containing two '*' in the AOR? Don't do that, then? :) Or maybe, I completely misunderstood the problem. What exactly goes into NUTAG_URL? Best regards, Mikhail - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] FW: Initialization of Sofia SIP v1.12.6 Error
This has a big impact to my application. Doesn't the Initialization and deinitialization paragraph of the Sofia SIP User Agent Library - "nua" - High-Level User Agent Module document say: "... This can be handled for example by having a separate thread that calls NUA functions to send messages or ..."? Is this no longer true in 1.12.6? Best Regards, Jerry -Original Message- From: Pekka Pessi [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 6:27 AM To: Jerry Richards Cc: sofia-sip-devel@lists.sourceforge.net Subject: Re: [Sofia-sip-devel] FW: Initialization of Sofia SIP v1.12.6 Error 2007/9/18, Jerry Richards <[EMAIL PROTECTED]>: > My 1.12.4 based application always called su_root_create() and nua_create() > first, then called su_root_run() from a newly created thread. After that, > nua_register() is called. > > Did something in this area change in version 1.12.6? Unfortunately, yes. Now some su_root_ functions use the thread ID to do some optimizations. So you have to call su_root_create() and nua-create() from the same thread that acutally runs the stack. -- Pekka.Pessi mail at nokia.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation Fault If AORContains Two '*'
Hi, My phone can use star-codes to activate phone features (e.g. *72 for call forwarding). And it is possible for a user to activate a feature, then dial a star-code, then press re-dial to introduce a double star-code string (e.g. *73*72). I'm wondering if protect against this by writing software to remove one of the star-codes prior to invoking nua_handle/nua_invite? The entire NUTAG_URL() looks like: "sip:[EMAIL PROTECTED]:5060"). I would rather let the user do whatever the user wants to do, so that I don't pre-empt some future capability. My issue with sofia-sip: I think it should protect itself from generating a segmentation fault. True? If you dial the URL above, do you also see the segmentation fault on your platform? Best Regards, Jerry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, October 05, 2007 4:10 AM To: [EMAIL PROTECTED]; sofia-sip-devel@lists.sourceforge.net Subject: RE: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation Fault If AORContains Two '*' Hi, >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On >Behalf Of ext Jerry Richards >Sent: Thursday, October 04, 2007 10:11 PM >To: sofia-sip-devel@lists.sourceforge.net >Subject: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation >Fault If AORContains Two '*' > >Does anyone know why I get a Segmentation Fault if I call >nua_handle() or >nua_invite() with an NUTAG_URL() containing two '*' in the AOR? Don't do that, then? :) Or maybe, I completely misunderstood the problem. What exactly goes into NUTAG_URL? Best regards, Mikhail <>- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
[Sofia-sip-devel] [ sofia-sip-Bugs-1684327 ] Stack is not caching authentication credentials
Bugs item #1684327, was opened at 2007-03-20 15:27 Message generated for change (Comment added) made by mzabaluev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1684327&group_id=143636 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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rajeev K (rajuareraju) Assigned to: Nobody/Anonymous (nobody) Summary: Stack is not caching authentication credentials Initial Comment: Section 22.2 of RFC 3261 says "Once authentication credentials have been supplied either directly by the user, or discovered in an internal keyring), UAs SHOULD cache the credentials for a given value of the To header field and "realm" and attempt to re-use these values on the next request for that destination.". and the stack is not doing it. For the end user there is no effect of this bug, but the application will generate more traffic with a proxy which will challenge all the requests. -- Comment By: Mikhail Zabaluev (mzabaluev) Date: 2007-10-05 19:05 Message: Logged In: YES user_id=313104 Originator: NO This leads to some proxies challenging unlikely requests such as BYE, so the client has to add authentication handling for nua_r_bye etc. (not a bad thing to do anyway). The stack caches the credentials only for ACKs which are sent as a result of a 200 response, but not ACK for the other status codes. Isn't it in violation of RFC 3261? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1684327&group_id=143636 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation Fault If AORContains Two '*'
Hi, >-Original Message- >From: ext Jerry Richards [mailto:[EMAIL PROTECTED] >Sent: Friday, October 05, 2007 5:41 PM >To: Zabaluev Mikhail (Nokia-M/Helsinki); >sofia-sip-devel@lists.sourceforge.net >Subject: RE: [Sofia-sip-devel] NUTAG_URL() Causes Segmentation >Fault If AORContains Two '*' > >My phone can use star-codes to activate phone features (e.g. >*72 for call forwarding). And it is possible for a >user to activate a feature, then dial a star-code, then press >re-dial to introduce a double star-code string (e.g. >*73*72). I'm wondering if protect against this by >writing software to remove one of the star-codes prior to >invoking nua_handle/nua_invite? The entire NUTAG_URL() looks >like: "sip:[EMAIL PROTECTED]:5060"). I would rather >let the user do whatever the user wants to do, so that I don't >pre-empt some future capability. > >My issue with sofia-sip: I think it should protect itself from >generating a segmentation fault. True? If you dial the URL >above, do you also see the segmentation fault on your platform? It works for me, but Telepathy-SofiaSIP might do it differently. Can you look up the location of the crash in a core file or something? Regards, Mikhail - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
