V16 Update 5 Beta - New PUSH Support for Seamless Remote Working with iOS App

[nitrox]

Ed

@nitrox, what John was referring is the following edit the extension which has RPS enabled and press OK. Go to Dashboard, Event Log do you see some error related to this extension? Are you using Snom Devices can you check for me. Thanks

Probably I understood what happen. The RPS feature is working when I have phones configured in direct sip call. In my extension I had 2 Snom phones. The first behind the sbc and the second in stun Mode. I deleted the one in stun mode and moved to a different 3cx Pbx, configured it To the new Pbx in stun mode but the phone was still pointing to the old Pbx. At the moment I discovered that the old Pbx didn’t send the rps update . Is it possible that when you have 2 phones under the same extension and there is one configured behind the sbc the Pbx doesn’t send the rps update?

 

[paradigm1]

New install for testing... set our email server for our exchange. worked great installed the alpha's then beta. messed around with scheduling meetings and from the web client. I needed the schedule to go directly into outlook. messed arround woth it some more and switch the the email setting to use 3cx smtp. then tried to switch back to custom email server. now it getting the error:
An error occurred while attempting to establish an SSL or TLS connection. The SSL certificate presented by the server is not trusted by the system for one or more of the following reasons: 1. The server is using a self-signed certificate which cannot be verified. 2. The local system is missing a Root or Intermediate certificate needed to verify the server's certificate. 3. The certificate presented by the server is expired or invalid. See https://github.com/jstedfast/MailKit/blob/master/FAQ.md#InvalidSslCertificate for possible solutions.


verified my exchange cert was valid. could this be a bug?

 

[JohnS_3CX]

I installed Yealink firmware 66.84.0.125 on my T48S. 3cx is telling me that it is not supported? Thanks

You got that message because you are not using 3CX supported firmware. Check here to see the latest supported version, or use the Firmware+ button in the Phones section to allow the system to install the latest version we currently support:
https://www.3cx.com/support/phone-firmwares/

 

[JohnS_3CX]

Ed

Probably I understood what happen. The RPS feature is working when I have phones configured in direct sip call. In my extension I had 2 Snom phones. The first behind the sbc and the second in stun Mode. I deleted the one in stun mode and moved to a different 3cx Pbx, configured it To the new Pbx in stun mode but the phone was still pointing to the old Pbx. At the moment I discovered that the old Pbx didn’t send the rps update . Is it possible that when you have 2 phones under the same extension and there is one configured behind the sbc the Pbx doesn’t send the rps update?

No, each phone is independently configured. You can have 3 Yealink T46S for example, all 3 under the same extension, 1x Direct SIP then 1x Local and one SBC and there will be no problem at all. You can add another 3 and another 3 etc etc and they will all still work because they are independently configured per unique MAC address.

For STUN phones, when you add the phone and press OK to save, you will see a message appearing on the front page Event Log that an RPS entry has been successfully sent - or that the RPS entry failed. If you get no message at all, then probably you did not configure it as Direct SIP / STUN and you should check your configuration again.

 

[JohnS_3CX]

New install for testing... set our email server for our exchange. worked great installed the alpha's then beta. messed around with scheduling meetings and from the web client. I needed the schedule to go directly into outlook. messed arround woth it some more and switch the the email setting to use 3cx smtp. then tried to switch back to custom email server. now it getting the error:
An error occurred while attempting to establish an SSL or TLS connection. The SSL certificate presented by the server is not trusted by the system for one or more of the following reasons: 1. The server is using a self-signed certificate which cannot be verified. 2. The local system is missing a Root or Intermediate certificate needed to verify the server's certificate. 3. The certificate presented by the server is expired or invalid. See https://github.com/jstedfast/MailKit/blob/master/FAQ.md#InvalidSslCertificate for possible solutions.


verified my exchange cert was valid. could this be a bug?

Since you are on beta, I would recommend to check the steps mentioned above first. Then if those turn out to be ok, stay on 3CX SMTP, and restart the machine. Once the system is up and running, switch back you your own SMTP and see if it will connect. Exchange has a number of settings that must be aligned before it allowed to relay messages. Can you confirm that when it worked originally, 3CX managed to send at least 1 email using that server (with TLS on)? You should be able to confirm from your Exchange logs.