Hi -
we've had a basic .net program that uses the calltriggercmd.exe command to enable simple click to dial via the windows 3cx client.
its been working since day 1 for months, then suddenly on tuesday morning it stops working - no environment changes, no software changes, no 3CX changes, no windows updates.
The phones all work OK manually (SNOM hardphones and Windows client) inbound and outbound are all fine.
I figured it was the .net app - but then I just ran the makecall command in a cmd.exe and that failed.
no error, it runs but just doesn't envoke the 3CX windows client
C:\ProgramData\3CXPhone for Windows\PhoneApp>calltriggercmd.exe - cmd makecall:01**********67
I'm at a loss as to why calltriggercmd has suddenly stopped working.
Can anyone suggest where I can start looking for answers...
We're running latest 3CX windows client build on 15.5.5 Pro
we've had a basic .net program that uses the calltriggercmd.exe command to enable simple click to dial via the windows 3cx client.
its been working since day 1 for months, then suddenly on tuesday morning it stops working - no environment changes, no software changes, no 3CX changes, no windows updates.
The phones all work OK manually (SNOM hardphones and Windows client) inbound and outbound are all fine.
I figured it was the .net app - but then I just ran the makecall command in a cmd.exe and that failed.
no error, it runs but just doesn't envoke the 3CX windows client
C:\ProgramData\3CXPhone for Windows\PhoneApp>calltriggercmd.exe - cmd makecall:01**********67
I'm at a loss as to why calltriggercmd has suddenly stopped working.
Can anyone suggest where I can start looking for answers...
We're running latest 3CX windows client build on 15.5.5 Pro
