Difference between revisions of "Call was billed incorrectly"
| Line 23: | Line 23: | ||
<br><br> | <br><br> | ||
= Call duration does not match with Clien/Provider = | |||
It can happen, if option "Media control – can reinvite/transfer" is set to "YES" on Device or Provider settings. | |||
Why it is so? | |||
Lets say that for some reasons client lost connection with internet. Usualy (when media goes through Asterisk), Asterisk would hangup such call because media is not received, but in the case of "can reinvite", Asterisk cannot see that connection is lost and it assumes that the call is active, while it is hanged up on client side. Than causes mismatching on billing. | |||
<br><br> | |||
= See also = | = See also = | ||
* [[I have a problem with Calls]] | * [[I have a problem with Calls]] | ||
Revision as of 10:51, 17 April 2012
'Wrong' rate was applied to the call
If you think that not correct rate was applied to the call, you should use Call Tracing to investigate such Calls.
Call was ANSWERED but billsec = 0
When Asterisk version >= 1.4.33.1:
Copy cdr.conf from /usr/src/mor/asterisk-conf/ folder to /etc/asterisk/ and restart Asterisk.
Call was ANSWERED but marked as UNKNOWN and not billed
If your Asterisk version is 1.4.18.1 you need to recompile core with such line:
#define AST_VER_14241 0
not:
#define AST_VER_14241 1
Call duration does not match with Clien/Provider
It can happen, if option "Media control – can reinvite/transfer" is set to "YES" on Device or Provider settings.
Why it is so?
Lets say that for some reasons client lost connection with internet. Usualy (when media goes through Asterisk), Asterisk would hangup such call because media is not received, but in the case of "can reinvite", Asterisk cannot see that connection is lost and it assumes that the call is active, while it is hanged up on client side. Than causes mismatching on billing.
