Recent content by NetVu IT

  1. Issue with extensions and no inbound rules

    Yes it's normal behaviour and something I've seen in both V14 and V15 with trunking. The only time the incoming rules don't appear to be needed is for 3CX to 3CX bridges. I don't know why it's required; I'd have thought it relatively simple to allow an extension match based on an incoming...

  2. Annoyances with Debian V15

    @YiannisH_3CX Quoting you quoting me is going to get complicated, so I'm going to try to respond in order. I'm referring to local handsets on the same subnet/VLAN as the server. The only time the handsets update the firmware and provision correctly is if I select the FQDN as the interface...

  3. Annoyances with Debian V15

    The phones and server need to be on the same VLAN/Subnet. Then for me the rest of the process is: Plug the phone in and wait for it to appear in 3CX's 'Phones' list. Select the phone in the list then click 'Add Ext' to create a new extension, or 'Assign Ext' to add the phone to an existing...

  4. Password policy

    Hi, I'd like to see an option to define a minimum password length for SIP accounts and voicemail. For one of the sites I maintain, SIP accounts have to use passwords of at least 16 characters, consisting of mixed case and numbers. For voicemail these have to be at least 6 digits. It'd be nice...

  5. Annoyances with Debian V15

    I suspect some of this may want to be listed under "3CX Ideas", other than that this is a list of bugbears I've encountered with my first deployment of the Debian version. My last implementation was a Windows v14 install. Plug and Play Provisioning only working when selecting FQDN and not IP...

  6. Firmware Location for Linux Install?

    Hey, I think you're looking for /var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/xxxxxxxxxxxxx/

  7. 3CX - Windows VS Linux

    I can't comment on all aspects of system performance, but I can tell you re-installing Debian based 3CX from scratch on Friday took me about 15 minutes. For it to be this quick under Windows I'd probably have to be using a pre-installed VM image. As others have pointed out it most likely...

  8. Secure SIP with REAL certificate

    I did the same with the FQDN as I couldn't figure out an easy way of presenting a valid SSL certificates for internal and external traffic. I've not had any issues with Secure RTP as that seems to just accept all certificates, even when I'd entered the CA's certificate rather than the key. It...

  9. V15 - Snom D315 Direct SIP provisioning

    I've got this working on Local LAN (sic), it turns out my problem was due to using the IP address on the Interface selection rather then the FQDN.

  10. Secure SIP with REAL certificate

    Had a bit of an realisation last night. There are two different connection settings in the 3CX Client; one for In Office and the other for Out of Office. The reason I couldn't get Secure SIP running is that the In Office setting defaults to the IP address rather then the FQDN so, of course...

  11. V15 - Snom D315 Direct SIP provisioning

    And that's how it works once I've got the firmware to a supported version. I've tested it with a few, new out of the box, phones using the 8.9.3.28 FW they've arrived with. With each one I've had the issue where the STUN server setting is populated and prevents registration until it's removed...

  12. V15 - Snom D315 Direct SIP provisioning

    That's looking better, thanks. Is there anyway of streamlining this? As it stands at the moment I have to first provision the phone. Then remove the STUN server setting from the phone to get it to appear as provisioned in the 3CX phone list. Then upgrade the firmware. This may not seem like...
See more
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom