the dialog. Thank you for your help with this issue.
Ben Newlin
*From: *Bogdan-Andrei Iancu
*Date: *Monday, October 8, 2018 at 7:10 AM
*To: *Ben Newlin , OpenSIPS users mailling
list
*Subject: *Re: [OpenSIPS-Users] Accounting BYE response
HI Ben,
Could you re-test with the flow I had
received response terminates the dialog. Thank you for
your help with this issue.
Ben Newlin
From: Bogdan-Andrei Iancu
Date: Monday, October 8, 2018 at 7:10 AM
To: Ben Newlin , OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Accounting BYE response
HI Ben,
Could you re-test with the
Iancu
*Date: *Tuesday, October 2, 2018 at 4:59 AM
*To: *Ben Newlin , OpenSIPS users mailling
list
*Subject: *Re: [OpenSIPS-Users] Accounting BYE response
Hi Ben,
OK, my experiment with 2.4 :
* Have a call up between two endpoints
* kill the end points, without allowing them to send any BYE or
. Perhaps when an
actual failure response is received instead of a local timeout the operation is
different in OpenSIPS?
Ben Newlin
From: Bogdan-Andrei Iancu
Date: Tuesday, October 2, 2018 at 4:59 AM
To: Ben Newlin , OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Accounting BYE
not being set. This seems to
indicate the dialog is being terminated prior to the call to the
failure route.
Ben Newlin
*From: *Bogdan-Andrei Iancu
*Date: *Friday, September 21, 2018 at 5:31 AM
*To: *Ben Newlin , OpenSIPS users mailling
list
*Subject: *Re: [OpenSIPS-Users] Accounting BYE
is being terminated prior to the call to the
failure route.
Ben Newlin
*From: *Bogdan-Andrei Iancu
*Date: *Friday, September 21, 2018 at 5:31 AM
*To: *Ben Newlin , OpenSIPS users mailling
list
*Subject: *Re: [OpenSIPS-Users] Accounting BYE response
Hi Ben,
The Dialog is not terminated (as
dialog is being terminated prior
to the call to the failure route.
Ben Newlin
From: Bogdan-Andrei Iancu
Date: Friday, September 21, 2018 at 5:31 AM
To: Ben Newlin , OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Accounting BYE response
Hi Ben,
The Dialog is not terminated (as status
: *Thursday, September 20, 2018 at 11:42 AM
*To: *OpenSIPS users mailling list , Ben
Newlin
*Subject: *Re: [OpenSIPS-Users] Accounting BYE response
Hi Ben,
The issue is a bit more complex. When generating the BYE requests, the
dialog module triggers the event of call terminated when it gets back
the
mailling list , Ben Newlin
Subject: Re: [OpenSIPS-Users] Accounting BYE response
Hi Ben,
The issue is a bit more complex. When generating the BYE requests, the dialog
module triggers the event of call terminated when it gets back the first final
reply (to any of the BYEs). And ACC module generates
*Subject: *Re: [OpenSIPS-Users] Accounting BYE response
I think you should take care of this on your gateway. For example,
using freeswitch or asterisk, you can check for rtps, and when the
other end stops sending rtps for 30 seconds (configurable) it will
tear down the call properly.
Unless
based on the response to a BYE, whether generated from OpenSIPS or not.
Ben Newlin
From: Users on behalf of David Villasmil
Reply-To: OpenSIPS users mailling list
Date: Friday, September 7, 2018 at 5:53 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Accounting BYE response
I
I think you should take care of this on your gateway. For example, using
freeswitch or asterisk, you can check for rtps, and when the other end
stops sending rtps for 30 seconds (configurable) it will tear down the call
properly.
Unless you're using a rtp-proxy with opensips which can do this (mos
Hi,
I am having an issue trying to add values to accounting based on the response
to the BYE request.
We use the dialog timeout mechanism to terminate long calls in our system. In
some cases, these are “valid” calls that remained connected for too long due to
some error elsewhere in the applic
Hi Jan,
By default, the acc module records only successful transaction (2xx
replied). To account failed transactions (like Bye which are not
replied), you need to set the failed_transaction_flag. See:
http://www.opensips.org/html/docs/modules/1.5.x/acc.html#id271012
Regarding the records fo
On Jul 17, 2009, at 12:19 PM, Jan D. wrote:
Hi,
> if(is_method("BYE"))
> {
> #setflag(25); # account successful transactions
> acc_db_request("200 OK", "acc");
> }
Why not set the flag that also accounts unsuccessful transactions in
case of a BYE? Then it's just a matter of picking out the BY
Alex,
I will trie setting an AVP an/or t_check_trans().
The reason is that we use opensips to connect clients to an Cisco endpoint.
Is ie. the connection from the client drops the Cisco sents a BYE. The
client does not react with an O.K. and the call is not accounted with an
endtime (so its seem
Jan,
You could set an AVP or a branch parameter. Those persist for the
lifetime of a transaction. Since subsequent BYEs are retransmissions
within the same transaction, you should be able to check if an AVP or
branch flag indicating that the BYE has already been accounted is set
before running
I have a problem with accounting the BYE in my mysql database (acc table).
Sometimes a BYE is sent more than one time, or sometimes the other site does
not respond with an O.K. on the BYE.
Here is a peace of my config (example):
if(loose_route())
{
...
if(is_method("BYE"))
{
#setflag(25); # ac
18 matches
Mail list logo
