Search results

  1. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    Thanks for the clarification Nick - I would hate to see the Windows client go... although it does need a couple of cosmetic tweaks as other posts have suggested (including mine) :) To be honest, I won't be sorry to see the CTI mode go... although I'm sure others will feel differently. I've...

  2. Windows 3cx softphone client

    Add an option so that the 3cx client will only connect to devices defined in the PBX's CSTA_USER_AGENTS parameter. This will allow the use of legacy devices which don't support CSTA as 3cx extensions but will prevent them from being targets in the 3cx Windows client. Additionally, if the same...

  3. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    And if the Windows client is not being deprecated - how about changing this feature request..? We have carefully tested several phones on the 3cx supported list and opted to purchase Yealink T46 and T48 models (which obviously DO support CSTA) but we are stuck with the legacy DECT N720 system...

  4. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    I think I might have phrased that a little differently - but cannot help but agree with you on most of the points... which was the whole reason I asked Nick if there were plans to stop development of the Windows client.

  5. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    Does the Windows client not support CSTA then? Will it ever? Is the Windows client being deprecated in favour of the Webclient?

  6. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    Or perhaps the Windows 3cx client could evaluate which of the possible CTI devices is on the current subnet and filter out those that aren't - if that left only one, the client could connect to it without prompting. :)

  7. RTP PORT management

    +1

  8. Improvements To Call Queues

    I know having a "dummy" extension as a queue agent is a workaround - but it does work... not sure why this change would be critical - what is preventing you implementing queues using this workaround out of interest? Personally, I find the 3cx queue way to restrictive for use outside of a call...

  9. Rejected Prevent "multiple CTI devices" dialog being displayed by Windows client

    It would be great if it was possible to "filter" the list of devices for the "Deskphone(CTI)" option. My client has two devices per extension. One is a Yealink T48, the other a DECT handset linked to a Gigaset N720 installation. The Gigaset supports basic CTI, the Yealink "fill" CTI/CSTA. It...

  10. Solved Yealink phone time not updating

    Is the windows server domain-joined or standalone? Non-domain-joined Windows servers don't usually have NTP server enabled by default

  11. Solved Zoiper Linux + 3cx

    I am able to connect Zoiper5 from my windows PC both by FQDN and IP address so it definitely *should* work :(

  12. Solved Zoiper Linux + 3cx

    I don't have Zoiper for Linux - only one thing occurs to me, have you checked to make sure in your attempts to authenticate that the client IP address hasn't been blacklisted by the 3cx server?

  13. Solved Zoiper Linux + 3cx

    Did you leave the SIP port on 3cx as the standard 5060? If not, when you entered the domain in Zoiper, did you append the :<portnumber> to the IP/FQDN?

  14. Solved Outbound Caller ID not working?

    You can also set whether the value comes from the trunk or the extension - you'll need this set right if you need to send different caller IDs per extension. Sorry for the vaguery, I'm fairly new to 3cx and can't think without having the management interface open in front of me. However, if...

  15. Solved Outbound Caller ID not working?

    Check the outbound parameters on your SIP trunk.. the user part determines which number is used for the outbound CID I think (I say think because I can't get to my 3cx and check for you right now)

  16. v.15.5.342.392 - Samsung A3 - correspondents do not hear

    Are the handsets configured to use the tunnel? And you have UDP/RTP set yes? Not TLS/SRTP?

  17. Windows Client set "away" automatically

    It's not exactly what you want but just making sure you know that "Account Settings/Advanced Settings\Auto Change Status when idle" whilst it doesn't go to Away when the PC is locked, it might be close enough for you...

  18. Ring groups to act on SIP_FORKED_ID_BUSY parameter

    OK - I get that few people would even know the SIP_FORKED_ID_BUSY parameter existed. But come on please, someone at 3cx take a quick look at this. Surely it's a bug that calls direct to an extension or calls where the extension is an agent in a queue follow the SIP_FORKED_ID_BUSY setting but...

  19. Implemented Bluetooth compatibility for 3CXphone on Android and iOS to connect to car phone

    I can confirm the issue seems to have been fixed - tested on a Bluetooth headset and two in-car systems

  20. Solved New iOS client 26/06

    No worries chap. A quick play on my test iPhone shows a different behaviour on the last released version - on that one, both the target and source extension immediately turn yellow (without needing to change tabs) but it doesn't display a flashing red "ringing" indicator either. Thanks for all...
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom