Sasmita, A negative response to an in-dialog request does not automatically terminate the call. If the rejection of the re-INVITE is not acceptable to either party, they must still send a BYE if they desire to disconnect the call.
After the 500 response, it is correct that there are no transactions as the re-INVITE transaction has been responded and closed. But the lack of active transactions does not mean the dialog/call is not still active. Based on your description the accounting seems correct. Any UAs involved that believed the call was disconnected based on the 500 response are not operating correctly. Ben Newlin From: Users <[email protected]> on behalf of Sasmita Panda <[email protected]> Date: Tuesday, October 31, 2023 at 4:21 AM To: OpenSIPS users mailling list <[email protected]> Subject: [OpenSIPS-Users] Need some information regarding accounting module . EXTERNAL EMAIL - Please use caution with links and attachments ________________________________ Hi All , I just got an wired call example on which the ACC information is not as for my expectation . I have Opensips 1.11 version . Example : Call started at : Oct 17 19:24:40:512 Re-Invite on this session : Oct 17 19:24:40:810 For the Re-Invite The client got " 500 Server Internal Error " which Opensips gave . After that there was no transaction in the session . The call got disconnected due to the error message . But The ACC info for that call : Oct 18 07:33:32 (After 12 hr ) Although Opensips created the 500 error message still the session did not get cleaned and Acc was printed after so long with a bigger talktime : duration=43729 . Which is totally beyond my expectation . I have attached the opensips config file as well . I am not sure . Do I need to call drop_accounting while in an error scenario ? Thanks & Regards Sasmita Panda Senior Network Testing and Software Engineer 3CLogic , ph:07827611765
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
