Update 6 Final is out - with new WebRTC softphone!

This looks like a really cool update. I would like to draw your attention to a few things that still impact my use case:

  1. BLF for DND needs more consideration. Users set it, don't realize it's still set, and cannot unset it without using a dial code (which they also never remember). There are no logs showing when it's set or unset, and I have one user in particular who is seemingly always on DND, and claims they are not using the button on their phone. I have even replaced their Cisco SPA phone with a fully supported Yealink T21P E2, and it's continuing to happen.
  2. Outbound fax support - I know the official line is that you'll never support this, but it is still crucial to some businesses and will likely be for a long time to come.
Please give me more confidence in this product! I would love to start selling it, as the other features and functionality are great, but cannot as of now because of these show-stopping issues.
 
Agreed.... where is OPUS for T4X series.....

After trying out the new update I see the new opus codec listed on the template for the Yealink T5x series but not the T4x series, which is shame because that's what we have deployed. Fingers crossed opus makes it to the T4x series template soon!

In the mean time I might try a custom template and add in the opus codec...
 
Whew....I was worried about having to reconfigure the passwords on over 2000 extensions. Luckily, I just did about 500 extensions with no issues by using the 'regenerate' button on the extensions page. It worked like a charm and was easier than expected.
 
  • Like
Reactions: YiannisH_3CX
Whew....I was worried about having to reconfigure the passwords on over 2000 extensions. Luckily, I just did about 500 extensions with no issues by using the 'regenerate' button on the extensions page. It worked like a charm and was easier than expected.

There is one problem I discovered with this 'regenerate' ... it also resets the voicemail PIN :(
 
  • Like
Reactions: rfcomms
There is one problem I discovered with this 'regenerate' ... it also resets the voicemail PIN :(
oh CRAP i suppose i'm now going to have to confuse the hell out of everybody and resend their welcome emails....
Bummer. This should have been better thought out by 3CX
 
How to change the ports range? I have a Debian 8 server on OVH.
 
oh CRAP i suppose i'm now going to have to confuse the hell out of everybody and resend their welcome emails....
Bummer. This should have been better thought out by 3CX

Yep .. tell me about it.... I discovered it after I already regenerated a few hundred extensions
 
I have two issues... One if I delete a "Q" that has a DID the number is no longer available for selecting if I build a new "Q". The number has gone away to the dark side.

Two... I am no longer able to log into "Q's". I try *62 or the web client or a soft phone. No Matter what it will say it logs me in but then never does.
 
I have two issues... One if I delete a "Q" that has a DID the number is no longer available for selecting if I build a new "Q". The number has gone away to the dark side.

Two... I am no longer able to log into "Q's". I try *62 or the web client or a soft phone. No Matter what it will say it logs me in but then never does.

1. Can you do the following go to Inbound Rules, search for the DID and delete it, recreate the Queue again and select on "Add a DID/DDI" button will you see the DID there?

2. Due that your agent was in "Logged out" state and you created a Queue and added this agent we will add this agent in logged out state. Can you ensure that for this Queue this agent is Logged IN?
 
  • Like
Reactions: N_G
1. Can you do the following go to Inbound Rules, search for the DID and delete it, recreate the Queue again and select on "Add a DID/DDI" button will you see the DID there?

2. Due that your agent was in "Logged out" state and you created a Queue and added this agent we will add this agent in logged out state. Can you ensure that for this Queue this agent is Logged IN?


Ok point one is resolved with me blowing away the inbound route. On logging into the "Q" it wont let me. I have tried the softphone, the phone dialing *62 and the web client. Additionally I have tried forcing the user in.

No matter what it will never change to logged in status.
 
Existing extensions will keep their password but will be marked with an exclamation mark until the passwords are updated.
New extensions will have random passwords generated that meet the new requirements. You can still use a less complex password but that will also be marked with an exclamation mark.

Aside from the voicemail pin, that someone has mentioned, the other issue I see is what about Windows Client or Android/IOS extensions?

See if I'm missing something or misunderstanding anything in this thought:

The desk phones are always connected and I can do those after hours, but softphones are not always on and registered.

With many PBX's to manage, I do not know what all extensions are utilizing their softphones as well. Also I have some PBX's that are all softphone only. I assume for this to go flawlessly, these Windows/Android/IOS clients need to be online and showing in phones node when I regenerate so I can send a reprovision to them as well? Otherwise they will likely blacklist themselves if I do a regenerate for the deskphone while they are offline, then I'll have to clear blacklists, and manually reprovision them with the Welcome email and QR code?
 
Ok point one is resolved with me blowing away the inbound route. On logging into the "Q" it wont let me. I have tried the softphone, the phone dialing *62 and the web client. Additionally I have tried forcing the user in.

No matter what it will never change to logged in status.

OK, can you check if you edit the agent extension properties and go to Forwarding Rules Tab, the profile which the extension is currently set, "Log out from queues" is it enabled?
 
  • Like
Reactions: N_G
Aside from the voicemail pin, that someone has mentioned, the other issue I see is what about Windows Client or Android/IOS extensions?

See if I'm missing something or misunderstanding anything in this thought:

The desk phones are always connected and I can do those after hours, but softphones are not always on and registered.

With many PBX's to manage, I do not know what all extensions are utilizing their softphones as well. Also I have some PBX's that are all softphone only. I assume for this to go flawlessly, these Windows/Android/IOS clients need to be online and showing in phones node when I regenerate so I can send a reprovision to them as well? Otherwise they will likely blacklist themselves if I do a regenerate for the deskphone while they are offline, then I'll have to clear blacklists, and manually reprovision them with the Welcome email and QR code?

For those Clients which are not running you dont need to worry about, because when 3CX Clients start they always subscribe and reload the config file.
 
does the SSL updates affect the customer who uses its own SSL certification of the installation?

Yes, and we recommend that all users to update to SP6 to ensure safe operation and secure communications.
 
  • Like
Reactions: N_G
@mariosM_3CX:
This sounds (really) good :)
Can you say something to Snom (where the actual state is "experimental")?
Can a Snom (d345) be configured with the update for Opus or not..?

If state is "experimental" I would recommend to wait :)
 
  • Like
Reactions: N_G
In terms of the ports. Do they always use port 9000, then 9001, then 9002, ...? i.e. Do the RTP ports increment from 9000 per consecutive call that is in progress? Therefore, if I have ports 9000 to 9255 open on my firewall, but don't expect more than say 30 external SIP trunk calls, do I still need to open the extra ports?
 
In terms of the ports. Do they always use port 9000, then 9001, then 9002, ...? i.e. Do the RTP ports increment from 9000 per consecutive call that is in progress? Therefore, if I have ports 9000 to 9255 open on my firewall, but don't expect more than say 30 external SIP trunk calls, do I still need to open the extra ports?

When we first started 3cx, the person who programmed our router opened up 64 RTP ports for our 32 call 3cx license. I started getting complaints of no audio. Did some digging and found random ports were used within the range. So, my router had to match 3cx.
But open RTP ports shouldn't be an issue - just make sure 5060 is hardened.
 
  • Like
Reactions: James Clowes
Is the Linux IP tables rule automatically updated to allow 9000-10999?
 
Is there going to be any concept of BLF's on the webclient?
 
  • Like
Reactions: YiannisH_3CX

Forum statistics

Threads
111,990
Messages
590,165
Members
164,928
Latest member
blackacoustic