- Joined
- Apr 3, 2017
- Messages
- 90
- Reaction score
- 31
We are running 3CX 16 Update 4 on Debian 9.
We have trunks with a call limit set on them. When the max calls are in use if someone tries to call in the carrier receives a "600 Busy Everywhere" code and in turn forwards it on as a 404. According to a thread here a 3CX support rep says it is supposed to send a "486 Busy Here" but that is now what we are experiencing. Is this something that is configurable or is there a way around this as I need it to send 486 instead of 600.
Here the old thread where the tech says it should send a 486:
https://www.3cx.com/community/threads/busy-on-incoming-sip-calls.58455/
Here is a page stating it will send the 600:
https://www.3cx.com/docs/sip-trunk-options/
We have trunks with a call limit set on them. When the max calls are in use if someone tries to call in the carrier receives a "600 Busy Everywhere" code and in turn forwards it on as a 404. According to a thread here a 3CX support rep says it is supposed to send a "486 Busy Here" but that is now what we are experiencing. Is this something that is configurable or is there a way around this as I need it to send 486 instead of 600.
Here the old thread where the tech says it should send a 486:
https://www.3cx.com/community/threads/busy-on-incoming-sip-calls.58455/
Here is a page stating it will send the 600:
https://www.3cx.com/docs/sip-trunk-options/