-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: Unable to set correct account code on forwarded calls #530
Comments
Can confirm we're seeing the same thing; the injected dialplan uses |
Hi @kguptasangoma. Do you have plans to fix this issue soon? |
Hi @JoseGoncalves We do have plan to take a look but not immediately so might can take 2 to 3 weeks easily. |
Hi @kguptasangoma. Thanks for the quick reply. I will eagerly await your fix. Meanwhile, I need to find a way to fix my billing extract for the current month... |
Any updates on a fix for this issue? |
core version 17.0.18.11 |
hi @JoseGoncalves can you please try with above fixed core and accountcodepreserve module and let us know if its good for you? thanks |
Hi @kguptasangoma. I'm going to do that. |
Hi again. I've tested your fix and I confirm that it's working fine now. Thanks! |
FreePBX Version
FreePBX 17
Issue Description
The module
Preserve Accountcode
seems not to be working in FreePBX 17, because in my system, if the callee forwards a call, the account code that is used is from the caller, which is not the correct behavior.Operating Environment
Debian: 12
accountcodepreserve: 17.0.0.1
core: 17.0.17
framework: 17.0.19.16
Relevant log output
No response
The text was updated successfully, but these errors were encountered: