- Joined
- Jul 16, 2024
- Messages
- 3
- Reaction score
- 0
Hello everyone,
As we currently have a lot of air, we are currently experimenting with how we can connect the VCM from Lancom to the 3CX.
In principle this is possible, but so far we have not managed to get the trunk to work with extensions.
If the trunk in the VCM is configured as a single account, incoming calls, outgoing calls and extensions do not yet work.
When the trunk is changed to "Trunk" in the VCM, we get a permanent busy from the VCM.
We have also tried to implement the information from the thread, but unfortunately without success.
The trunk is set up in the test 3CX as a "Generic SIP Trunk (IP Based)".
The 3CX is on-prem, latest update (Version 20.0 Update 7 (Build 1019 Beta))
As we currently have a lot of air, we are currently experimenting with how we can connect the VCM from Lancom to the 3CX.
In principle this is possible, but so far we have not managed to get the trunk to work with extensions.
If the trunk in the VCM is configured as a single account, incoming calls, outgoing calls and extensions do not yet work.
When the trunk is changed to "Trunk" in the VCM, we get a permanent busy from the VCM.
We have also tried to implement the information from the thread, but unfortunately without success.
The trunk is set up in the test 3CX as a "Generic SIP Trunk (IP Based)".
The 3CX is on-prem, latest update (Version 20.0 Update 7 (Build 1019 Beta))