[OpenSIPS-Users] CP 6.2 drouting Error code 500 (Internal server error)

[Jeff Wilkie]

Running opensips 2.2.3 with CP 6.2

When attempting to enable a GATEWAY in CP under the system/drouting section
using the toggle button under "Memory State", the screen produces an "Error
code 500 (Internal server error)".  The process does appear to execute
properly though.

The httpd logs produce the following warnings only:

PHP Notice:  Undefined index: gateways_search_address in
/var/www/opensips-cp/web/tools/system/drouting/template/gateways.main.php
on line 42, referer:
http://xx.xx.xx.xx/cp/tools/system/drouting/gateways.php?action=disablegw&gwid=2


Opensips logs look like this on enable and disable:


Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: START *** cls=(nil), connection=0x1c83380,
url=/json/dr_gw_status, method=GET, versio=HTTP/1.1, upload_data[0]=(nil),
*con_cls=(nil)

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:getConnectionHeader: Accept=*/*

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: accept_type=[-1]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: normalised_url=[/dr_gw_status]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: START *** cls=(nil),
connection=0x1c83380, url=/dr_gw_status, method=GET, versio=HTTP/1.1,
upload_data[0]=(nil), *con_cls=(nil)

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got command=dr_gw_status

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: command=dr_gw_status accepts parameters

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got string param [2]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got string param [0]

*Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
ERROR:mi_json:mi_json_run_mi_cmd: failed to process the command*

*Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
ERROR:mi_json:mi_json_answer_to_connection: no reply*

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: MHD_create_response_from_data
[0x7f0a7ddcc600:60]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: START *** cls=(nil), connection=0x1c83380,
url=/json/dr_gw_status, method=GET, versio=HTTP/1.1, upload_data[0]=(nil),
*con_cls=(nil)

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:getConnectionHeader: Accept=*/*

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: accept_type=[-1]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: normalised_url=[/dr_gw_status]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: START *** cls=(nil),
connection=0x1c83380, url=/dr_gw_status, method=GET, versio=HTTP/1.1,
upload_data[0]=(nil), *con_cls=(nil)

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got command=dr_gw_status

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: command=dr_gw_status accepts parameters

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: but no parameters were found

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got mi_rpl=[0x7f0a885c4c60]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: building on page
[0x7f0a86dc3318:0]

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_page: start

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_content: start

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_recur_write_tree: Treat as an array

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_recur_write_tree: done

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_build_content: done

Feb 24 15:50:41 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: MHD_create_response_from_data
[0x7f0a86dc3318:445]



Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: START *** cls=(nil), connection=0x1c83380,
url=/json/dr_gw_status, method=GET, versio=HTTP/1.1, upload_data[0]=(nil),
*con_cls=(nil)

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:getConnectionHeader: Accept=*/*

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: accept_type=[-1]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:httpd:answer_to_connection: normalised_url=[/dr_gw_status]

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_answer_to_connection: START *** cls=(nil),
connection=0x1c83380, url=/dr_gw_status, method=GET, versio=HTTP/1.1,
upload_data[0]=(nil), *con_cls=(nil)

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: got command=dr_gw_status

Feb 24 15:50:47 opensips4 /sbin/opensips[31078]:
DBG:mi_json:mi_json_run_mi_cmd: comman

Re: [OpenSIPS-Users] 2.2.x and CP with json

[Jeff Wilkie]

Compiling the 2.2.3, I'm seeing several warnings of similar type below:

lookup.c: In function ‘is_contact_registered’:

lookup.c:559: warning: ‘callid.len’ may be used uninitialized in this
function

lookup.c:559: warning: ‘callid.s’ may be used uninitialized in this function


dlg_replication.c: In function ‘dlg_replicated_profiles’:

dlg_replication.c:838: warning: ‘old_name.s’ may be used uninitialized in
this function

dlg_replication.c:838: warning: ‘old_name.len’ may be used uninitialized in
this function

Is this anything to worry about?

Jeff Wilkie


On Fri, Feb 24, 2017 at 12:21 PM, Jeff Wilkie  wrote:

> Thanks Bogdan,  I will dl 2.2.3 and retest.  This error occurred on the
> following BTW
>
> Array
> (
> [Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
> )
>
>
> Jeff Wilkie
>
> On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Jeff,
>>
>> There was an issue on how the MI output of the address_dump was formated
>> when using JSON. This issue was leading to an invalid JSON being returned.
>> And CP was dropping the returned JSON as not able being able to parse it.
>> If you do the direct web query, there is nothing to parse/validate the
>> JSON, so it is displayed.
>>
>> The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it a
>> try please.
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
>>
>> Ok, question part 2, now that the proper module is loaded :)  From the MI
>> interface in CP, I have 1 small issue.  Using json to interface with
>> opensips, I execute the command "*address_dump" *and execute.  I receive
>> the output of address dump   |  son:127.0.0.1:/json Successfully
>> executed, no output generated.  Other commands like domain_dump work as
>> expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
>> command 127.0.0.1:/json/address_dump I receive the proper output.
>> Not sure why CP provides no output from this command though.
>>
>> The web query directly looks like this as a response when not using MI
>> via CP
>>
>> http://10.10.20.229:/json/address_dump
>>
>> {"part": [{"value":"default", "children":{"dest": [{"value":"   8 
>> <10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":" 19 
>> <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"81 
>> <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
>>
>>
>> It's not a show stopper but bugging me why it doesn't work for that
>> command only from what I can tell from initial testing.
>>
>> Jeff Wilkie
>>
>>
>>
>>> Yes, you did overlook to load the dialplan module into your OpenSIPS
>>> (the dp_reload command is prvided by this modules).
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>>
>>> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>>>
>>> When using the mi_json module combined with CP, it appears that not all
>>> of the functions were ported over for this interaction to complete 100%.
>>> JSON enabled in opensips-cp/config/boxes.global.inc.php only allows
>>> some commands to work.  One particular command that appears to not be
>>> working is under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to
>>> server".  I receive a Sending to *json:127.0.0.1:/json
>>> * : Error code 500 (Command not found) for
>>> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
>>> page "apply to server" returns success for address_reload.   Is this a
>>> known issue?  Did I overlook something small in the config?  How do I
>>> remedy this issue?
>>> Thanks
>>> Jeff Wilkie
>>>
>>> ___
>>> Users mailing 
>>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] 2.2.x and CP with json

[Jeff Wilkie]

Thanks Bogdan,  I will dl 2.2.3 and retest.  This error occurred on the
following BTW

Array
(
[Server] => OpenSIPS (2.3.0-dev (x86_64/linux))
)


Jeff Wilkie

On Fri, Feb 24, 2017 at 4:46 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Jeff,
>
> There was an issue on how the MI output of the address_dump was formated
> when using JSON. This issue was leading to an invalid JSON being returned.
> And CP was dropping the returned JSON as not able being able to parse it.
> If you do the direct web query, there is nothing to parse/validate the
> JSON, so it is displayed.
>
> The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it a
> try please.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
>
> Ok, question part 2, now that the proper module is loaded :)  From the MI
> interface in CP, I have 1 small issue.  Using json to interface with
> opensips, I execute the command "*address_dump" *and execute.  I receive
> the output of address dump   |  son:127.0.0.1:/json Successfully
> executed, no output generated.  Other commands like domain_dump work as
> expected in the SYSTEM/MI interface.  If I bypass CP and use web direct
> command 127.0.0.1:/json/address_dump I receive the proper output.
> Not sure why CP provides no output from this command though.
>
> The web query directly looks like this as a response when not using MI via
> CP
>
> http://10.10.20.229:/json/address_dump
>
> {"part": [{"value":"default", "children":{"dest": [{"value":"8 
> <10.10.10.99,2, 5060, 1, NULL, 151559>"}, {"value":" 19 
> <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"81 
> <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}
>
>
> It's not a show stopper but bugging me why it doesn't work for that
> command only from what I can tell from initial testing.
>
> Jeff Wilkie
>
>
>
>> Yes, you did overlook to load the dialplan module into your OpenSIPS (the
>> dp_reload command is prvided by this modules).
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>>
>> On 02/22/2017 05:56 PM, Jeff Wilkie wrote:
>>
>> When using the mi_json module combined with CP, it appears that not all
>> of the functions were ported over for this interaction to complete 100%.
>> JSON enabled in opensips-cp/config/boxes.global.inc.php only allows some
>> commands to work.  One particular command that appears to not be working is
>> under SYSTEM/DIALPLAN of CP when you attempt to hit "apply to server".  I
>> receive a Sending to *json:127.0.0.1:/json
>> * : Error code 500 (Command not found) for
>> the dp_reload command.  If I do the same thing under the SYSTEM/PERMISSIONS
>> page "apply to server" returns success for address_reload.   Is this a
>> known issue?  Did I overlook something small in the config?  How do I
>> remedy this issue?
>> Thanks
>> Jeff Wilkie
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 1.11.10

[Abdul Basit]

good work team

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On Fri, Feb 24, 2017 at 8:38 PM, Ramachandran, Agalya (Contractor) <
agalya_ramachand...@comcast.com> wrote:

> Thank you Liviu. I will try in the latest version and will update you my
> observation.
>
>
>
> Regards,
> Agalya
>
>
>
> *From:* Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Liviu
> Chircu
> *Sent:* Friday, February 24, 2017 3:44 AM
> *To:* users@lists.opensips.org
> *Subject:* Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3
> and 1.11.10
>
>
>
> Hi Agalya,
>
> There are no specific fixes addressing this issue, since it should be
> working right out of the box - libcurl should be able to handle it.
> Personally, I haven't been able to reproduce it. If problems persist for
> you even in 2.2.3, we are here to help!
>
> Regards,
>
>
> Liviu Chircu
>
> OpenSIPS Developer
>
> http://www.opensips-solutions.com
>
> On 24.02.2017 00:00, Ramachandran, Agalya (Contractor) wrote:
>
> Hi Liviu,
>
>
>
> Its great news. I have a question with respect to rest_client module.
>
> Does async with https support is added in 2.2.3?
>
>
>
> Regards,
>
> Agalya
>
>
>
> *From:* Users [mailto:users-boun...@lists.opensips.org
> ] *On Behalf Of *Liviu Chircu
> *Sent:* Thursday, February 23, 2017 12:57 PM
> *To:* OpenSIPS users mailling list 
> ; OpenSIPS devel mailling list
>  ;
> n...@lists.opensips.org
> *Subject:* [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and
> 1.11.10
>
>
>
> Hi, all!
>
>
>
> We are happy to announce a new set of OpenSIPS minor versions, namely 2.2.3 
> and 1.11.10,
>
> incorporating the last 4 months of backports and no less than 126 commits!
>
>
>
> While roughly half of these commits strictly relate to static code analysis 
> issues
>
> (thank you Răzvan for the Coverity initiative!), the rest of them include
>
> important corner-case fixes in more critical areas such as the TCP layer, 
> usrloc contact management,
>
> dialog replication, dispatcher, drouting, rest_client - to name a few.
>
>
>
> All three releases are ready for production use and even more  
> stable/accurate than before.
>
> Since they contain the latest bug fixes, we strongly recommend you to upgrade 
> your current instances.
>
>
>
> Thank you all for your reports, fixes, pull requests and all other 
> contributions to this project!
>
>
>
> The full ChangeLogs for the newly released versions are:
>
> http://opensips.org/pub/opensips/2.2.3/ChangeLog
>
> http://opensips.org/pub/opensips/1.11.10/ChangeLog
>
>
>
> Get the latest versions from:
>
> http://opensips.org/pub/opensips/
>
>
>
> Enjoy OpenSIPS,
>
> --
>
> Liviu Chircu
>
> OpenSIPS Developer
>
> http://www.opensips-solutions.com
>
>
>
>
> ___
>
> Users mailing list
>
> Users@lists.opensips.org
>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 1.11.10

[Ramachandran, Agalya (Contractor)]

Thank you Liviu. I will try in the latest version and will update you my 
observation.

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Liviu Chircu
Sent: Friday, February 24, 2017 3:44 AM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 
1.11.10

Hi Agalya,

There are no specific fixes addressing this issue, since it should be working 
right out of the box - libcurl should be able to handle it. Personally, I 
haven't been able to reproduce it. If problems persist for you even in 2.2.3, 
we are here to help!

Regards,



Liviu Chircu

OpenSIPS Developer

http://www.opensips-solutions.com
On 24.02.2017 00:00, Ramachandran, Agalya (Contractor) wrote:
Hi Liviu,

Its great news. I have a question with respect to rest_client module.
Does async with https support is added in 2.2.3?

Regards,
Agalya

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Liviu Chircu
Sent: Thursday, February 23, 2017 12:57 PM
To: OpenSIPS users mailling list 
; OpenSIPS devel 
mailling list ; 
n...@lists.opensips.org
Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 1.11.10


Hi, all!



We are happy to announce a new set of OpenSIPS minor versions, namely 2.2.3 and 
1.11.10,

incorporating the last 4 months of backports and no less than 126 commits!



While roughly half of these commits strictly relate to static code analysis 
issues

(thank you Răzvan for the Coverity initiative!), the rest of them include

important corner-case fixes in more critical areas such as the TCP layer, 
usrloc contact management,

dialog replication, dispatcher, drouting, rest_client - to name a few.



All three releases are ready for production use and even more  stable/accurate 
than before.

Since they contain the latest bug fixes, we strongly recommend you to upgrade 
your current instances.



Thank you all for your reports, fixes, pull requests and all other 
contributions to this project!



The full ChangeLogs for the newly released versions are:

http://opensips.org/pub/opensips/2.2.3/ChangeLog

http://opensips.org/pub/opensips/1.11.10/ChangeLog



Get the latest versions from:

http://opensips.org/pub/opensips/



Enjoy OpenSIPS,

--

Liviu Chircu

OpenSIPS Developer

http://www.opensips-solutions.com




___

Users mailing list

Users@lists.opensips.org

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] 2.2.x and CP with json

[Bogdan-Andrei Iancu]

Hi Jeff,

There was an issue on how the MI output of the address_dump was formated 
when using JSON. This issue was leading to an invalid JSON being 
returned. And CP was dropping the returned JSON as not able being able 
to parse it. If you do the direct web query, there is nothing to 
parse/validate the JSON, so it is displayed.


The issue was fixed in latest 2.2, so please grab the 2.2.3 and give it 
a try please.


Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/22/2017 08:24 PM, Jeff Wilkie wrote:
Ok, question part 2, now that the proper module is loaded :)  From the 
MI interface in CP, I have 1 small issue. Using json to interface with 
opensips, I execute the command "*address_dump" *and execute.  I 
receive the output of address dump**  |  son:127.0.0.1:/json 
Successfully executed, no output 
generated.  Other commands like domain_dump work as expected in the 
SYSTEM/MI interface.  If I bypass CP and use web direct command 
127.0.0.1:/json/address_dump 
 I receive the proper 
output.  Not sure why CP provides no output from this command though.


The web query directly looks like this as a response when not using MI 
via CP


http://10.10.20.229:/json/address_dump
{"part": [{"value":"default", "children":{"dest": [{"value":" 8 <10.10.10.99,2, 5060, 1, NULL, 151559>"}, 
{"value":"   19 <10.10.20.193,2, 5060, 1, NULL, 151559>"}, {"value":"  81 <192.168.1.203,1, 5060, 1, NULL, NULL>"}]}}]}

It's not a show stopper but bugging me why it doesn't work for that 
command only from what I can tell from initial testing.


Jeff Wilkie



Yes, you did overlook to load the dialplan module into your
OpenSIPS (the dp_reload command is prvided by this modules).

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com 

On 02/22/2017 05:56 PM, Jeff Wilkie wrote:

When using the mi_json module combined with CP, it appears that
not all of the functions were ported over for this interaction to
complete 100%.  JSON enabled
in opensips-cp/config/boxes.global.inc.php only allows some
commands to work.  One particular command that appears to not be
working is under SYSTEM/DIALPLAN of CP when you attempt to hit
"apply to server".  I receive a Sending to
*json:127.0.0.1:/json * : Error
code 500 (Command not found) for the dp_reload command.  If I do
the same thing under the SYSTEM/PERMISSIONS page "apply to
server" returns success for address_reload.   Is this a known
issue? Did I overlook something small in the config?  How do I
remedy this issue?
Thanks
Jeff Wilkie

___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 and 1.11.10

[Liviu Chircu]

Hi Agalya,

There are no specific fixes addressing this issue, since it should be 
working right out of the box - libcurl should be able to handle it. 
Personally, I haven't been able to reproduce it. If problems persist for 
you even in 2.2.3, we are here to help!


Regards,

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 24.02.2017 00:00, Ramachandran, Agalya (Contractor) wrote:


Hi Liviu,

Its great news. I have a question with respect to rest_client module.

Does async with https support is added in 2.2.3?

Regards,

Agalya

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of 
*Liviu Chircu

*Sent:* Thursday, February 23, 2017 12:57 PM
*To:* OpenSIPS users mailling list ; 
OpenSIPS devel mailling list ; 
n...@lists.opensips.org
*Subject:* [OpenSIPS-Users] [RELEASE] OpenSIPS minor releases: 2.2.3 
and 1.11.10


Hi, all!
We are happy to announce a new set of OpenSIPS minor versions, namely 2.2.3 and 
1.11.10,
incorporating the last 4 months of backports and no less than 126 commits!
While roughly half of these commits strictly relate to static code analysis 
issues
(thank you Răzvan for the Coverity initiative!), the rest of them include
important corner-case fixes in more critical areas such as the TCP layer, 
usrloc contact management,
dialog replication, dispatcher, drouting, rest_client - to name a few.
All three releases are ready for production use and even more  stable/accurate 
than before.
Since they contain the latest bug fixes, we strongly recommend you to upgrade 
your current instances.
Thank you all for your reports, fixes, pull requests and all other 
contributions to this project!
The full ChangeLogs for the newly released versions are:
http://opensips.org/pub/opensips/2.2.3/ChangeLog
http://opensips.org/pub/opensips/1.11.10/ChangeLog
Get the latest versions from:
http://opensips.org/pub/opensips/
Enjoy OpenSIPS,
--
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users