Branch: refs/heads/1.11
Home: https://github.com/OpenSIPS/opensips
Commit: 17c5990ee35691451008380f13b2ffcbc59ccf79
https://github.com/OpenSIPS/opensips/commit/17c5990ee35691451008380f13b2ffcbc59ccf79
Author: Razvan Crainea
Date: 2015-01-14 (Wed, 14 Jan 2015)
Changed paths:
Closed #398 via bb7f121202bb4215a388dcff75e0abcea8ec23ed.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/398#event-218771135___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: bb7f121202bb4215a388dcff75e0abcea8ec23ed
https://github.com/OpenSIPS/opensips/commit/bb7f121202bb4215a388dcff75e0abcea8ec23ed
Author: Razvan Crainea
Date: 2015-01-14 (Wed, 14 Jan 2015)
Changed path
On 01/14/2015 02:55 PM, Saúl Ibarra Corretgé wrote:
Hi Razvan!
I understand it’s just the beginning, hence my comments, targeted at
(hopefully) improving things :-)
- If TLS is taken out of the core it would be best to rewrite it without
looking at the current code. If we want to get OpenSIP
Hi Razvan!
I understand it’s just the beginning, hence my comments, targeted at
(hopefully) improving things :-)
>> - If TLS is taken out of the core it would be best to rewrite it without
>> looking at the current code. If we want to get OpenSIPS as an official
>> Debian package, the TLS code
Hi Ovidiu!
Fixed the typo, thanks!
As I said the the previous mail, this is not the final version of the
API, and most likely it will suffer a set of changes during the
implementation. But it stands as a starting point.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.c
Hi, Saul!
You have my answers inline.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 01/13/2015 01:12 PM, Saúl Ibarra Corretgé wrote:
Hi Razvan (and all!),
Sorry for not having participated earlier. Hopefully I can do that more now!
I had a look at the API, and
