- Joined
- Jul 5, 2017
- Messages
- 12
- Reaction score
- 0
Hi,
Im having an issue with using the CLI Mode in the 3CX Windows Client.
We are using Yealink T42G handsets and our 3CX Server is running on a Debian Virtual server in the cloud as we have 2 sites connected to it. Each site is running a local SBC Controller using Debian.
The issue is the Windows client is registered and detects the CLI Mode on the phone however when trying to dial from it the phone does not do anything. The only was i have managed to get it to work is when the phones are registered using Direct SIP mode instead of through the proxy.
From what i can tell the phone registers via the SBC perfectly fine however the Windows client always registers using the WAN Address even though i have forced it to register via the SBC controller.
The phone, PC and SBC controller are all on the same IP network\Range.
Does anyone know why the CLI mode wont work in this mode?
Thanks
John
Im having an issue with using the CLI Mode in the 3CX Windows Client.
We are using Yealink T42G handsets and our 3CX Server is running on a Debian Virtual server in the cloud as we have 2 sites connected to it. Each site is running a local SBC Controller using Debian.
The issue is the Windows client is registered and detects the CLI Mode on the phone however when trying to dial from it the phone does not do anything. The only was i have managed to get it to work is when the phones are registered using Direct SIP mode instead of through the proxy.
From what i can tell the phone registers via the SBC perfectly fine however the Windows client always registers using the WAN Address even though i have forced it to register via the SBC controller.
The phone, PC and SBC controller are all on the same IP network\Range.
Does anyone know why the CLI mode wont work in this mode?
Thanks
John