Hi,
I've tried to fix issue number 2, but it is more complicated than i
thought as concerning the logical solution, not the
programming one. In the meantime, indeed, the workaround is to call
fix_nated_contact() from the resume route. Also,
if you have time, please open a ticket on GitHub about this issue such
that we won't forget about it.
Regards,
Ionut Ionita
OpenSIPS Developer
On 02/24/2016 01:33 PM, Dragomir Haralambiev wrote:
Hello,
I make a lot of tests with Async radius on Opensips 2.2.
Here I can describe all problems
1. Second Async proccess:
When try to start second Async proces (when return from
adius_send_auth try to start async exec) I receive follow message:
Feb 12 17:19:36 sbc /sbin/mv[21231]: NOTICE:core:io_wait_loop_epoll:
connection closed by the remote peer!
Feb 12 17:19:36 sbc /sbin/mv[21231]: ERROR:core:io_wait_loop_epoll:
[UDP_worker] unexpected event 10 on 1/1, data=0xb77bc29c
In this case process 21231 is dead. When I try to stop opensips this
process does not stop.
2. Contact from location is not fixed.
When use When use Async adius_send_auth, contact from location table
is saved like this:
sip:[email protected]:54618;rinstance=d5d0dd431b9a1ca8;transport=UDP
When I add "fix_nated_contact()" after the return from radius all
working fine.
3. Async radius not generate CDR.
I have follow line in my Opensips script
create_dialog("PB");
setflag(MAKE_CDR);
but CDR is not generated.
Best regards,
Dragomir
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
