Recent changes to feature-requests

Assured Services

2012-12-04T14:52:15Z

Assured Services is an integral part of our Call Management system, we want to move to FreeSWITCH which uses this stack, but the lack of Assured Services SIP (AS-SIP) is a road block for us. Is there any plans to add in AS-SIP?

Use default certificate paths from OpenSSL

2011-05-23T11:29:45Z

It should be possible to make OpenSSL use default paths to search CA certificates for verification.
A branch with a quick and dirty implementation is available here:
https://gitorious.org/~mzabaluev/sofia-sip/mzabaluev-sofia-sip/commits/system-ca-path

A backwards-compatible change would have to add a tag to enable this behavior, retaining the previous path use by default.

Log sofia-sip modules through su_log()

2009-01-26T13:31:11Z

Currently sofia-sip only permits to log through a custom logger function only the messages issued by the su module, for the other messages there is the X_PORT/X_DEBUG/X_DUMP mechanism which uses environment variables to set for each module a distinct log file and level.

Exporting in the public headers a su_log_t struct for each module (nua_log, tport_log, nth_log etc.) should make possible to define a logger for each one of the modules.

This way should be possible to integrate the sofia logging facility (not only those related to the su module) into one's application log system.

I'm still trying to undestand how to do that, but Pekka noted in the list that there could be some difficulties involving the exporting of arrays in the windows and symbian platforms.

Anyway I think it would be a nice feature, I'll try to provide a patch eventually.

Best regards.

Doxygenation in the headers.

2009-01-26T09:56:46Z

Hi,

documentation for public functions/structures should stay in the headers, while currently the doxygenation is scattered amongst .h and .c files (often duplicated).

It would be nice to clean this, having the doxygenation for sofia public symbols just in the headers.

Thanks, regards.

apply 'APPL_METHOD' on "CANCEL"

2008-10-29T01:47:06Z

Current sofia stack responds automatically with 200OK to CANCEL, and then 487 after that. I propose to make it more flexible so that application programmer could control the behavior or insert new TAG parameters.

Dialog should stick to one remote transport address

2008-10-28T16:30:39Z

In some cases there are several request destination addresses available for a target URL, such as when an SRV lookup returns entries of the same priority. Requests in a dialog should stick to one transport address chosen for the initial request. This prevents confusion on the server side, where the alternative proxies often know nothing about each other's dialogs.

This also applies to resubmissions of INVITE requests after an authentication challenge. If authentication responses are fanned around multiple proxies which know nothing of each other's challenges, the number of steps needed to make the authentication succeed is not deterministic.

Remove trailing whitespaces from the code

2008-07-29T16:19:47Z

Hi,

trailing whitespaces take useless storage space/bandwith, and make more difficult to provide clean patches since it's easy to change the number of them, also they're ugly to see ;-).

So it would be nice to avoid them, then maybe to set an hook a-la SVN to reject commits/patches containing them.

A script could easily eliminate all of them from the code (I can provide it or the patch if you like it).

Regards.

Additional Authentication

2008-03-22T13:02:04Z

Add an interface (callback or other) that will enable to override the MD5 authentication (algorithm="MyAlgorithm"). The feature should allow the programmer to receive the challenge (nonce), and all the relevant headers/tags of the 401/407, calculate the response and return it with the ability to add/modify additional headers/tags.

Add variants of NUA request methods that accept a tag array

2007-12-11T13:41:42Z

To allow more flexible programmability, and particularly to enable scripting language bindings for Sofia-SIP NUA API, it would be useful to have variants of NUA request methods such as nua_invite() that accept the tag list as a pointer to an array, similar to the tagi_t[] parameter in event callbacks.

Remote contact handling in nua

2007-10-10T18:25:10Z

NUA does not save remote target in the dialog. If the target refresh request or response (INVITE, UPDATE, SUBSCRIBE, NOTIFY, ...) has bad contact or it is missing, the next request in dialog is not necessarily sent to correct destination.

The remote target should be saved and the application should be able to prevent stack from replacing good contact with bad one.