Pre-release iOS Beta with Latest UI Updates & Fixes

[Norclair]

The device is locked before answer

We have 2 different failed, 1, the device is locked, when answering the call the app close, and the other is when answering the call the call work for 2 seconds and then the call drop on the app (the caller still on the line but the call is drop)

 

[Norclair]

We have 2 different failed, 1, the device is locked, when answering the call the app close, and the other is when answering the call the call work for 2 seconds and then the call drop on the app (the caller still on the line but the call is drop)

And as i said before this behavior happen 1 time on 5

 

[Vali_3CX]

Then I will no longer bother you with reports or crash messages.

No, send the feedback when is something new, or if happen again in a new release - what I wanted to say is we are aware of the crashes, comments, requests reported via TestFlight and we try to solve them, but the primary condition to fix a crash is to be able to reproduce it, and in this case we weren't.

 

[NickD_3CX]

@Norclair
Could you please tell me if you have setup your 3CX PBX using an internal FQDN?
If yes, could you check if in the Extension Settings that you have configured your iOS to, if in the Phone Provisioning tab, you have selected the internal FQDN or the Local IP of the Server?

 

[Norclair]

@Norclair
Could you please tell me if you have setup your 3CX PBX using an internal FQDN?
If yes, could you check if in the Extension Settings that you have configured your iOS to, if in the Phone Provisioning tab, you have selected the internal FQDN or the Local IP of the Server?
View attachment 16312

It is our internal IP address.

 

[NickD_3CX]

It is our internal IP address.

I think we have have identified the problem which you were facing, we will probably be releasing a new version later today or tomorrow which you could try.

 

[Norclair]

@Norclair
Could you please tell me if you have setup your 3CX PBX using an internal FQDN?
If yes, could you check if in the Extension Settings that you have configured your iOS to, if in the Phone Provisioning tab, you have selected the internal FQDN or the Local IP of the Server?
View attachment 16312

Oh some are with internal IP and other extension are with our FQDN... (what should it be!??)

 

[Norclair]

I think we have have identified the problem which you were facing, we will probably be releasing a new version later today or tomorrow which you could try.

It will be awesome!!!

 

[NickD_3CX]

Oh some are with internal IP and other extension are with our FQDN... (what should it be!??)

It can be either IP or FQDN, but I think you will find that this happens only on the clients that you have selected the FQDN in the extension settings. That is something we identified on Friday and we will be addressing.

 

[Norclair]

It can be either IP or FQDN, but I think you will find that this happens only on the clients that you have selected the FQDN in the extension settings. That is something we identified on Friday and we will be addressing.

It make sense, (our extension with the problem is related are actually with the FQDN, other without problem are not), do you suggest to try it with my internal IP adress today, and revert the change when the app will be available?

 

[NickD_3CX]

It make sense, (our extension with the problem is related are actually with the FQDN, other without problem are not), do you suggest to try it with my internal IP adress today, and revert the change when the app will be available?

You could do that, yes. If you select IP it should work fine, but for next release we intend to have fixed the issue so that it also works with Internal FQDN.

 

[Norclair]

I did change the Network to use our internal IP for all of our extension, i did manage to go on every one's phone to be sure to reaprovisionned all the phone... for now the problem still happen. I do not know if the the "reapprovisionning" option did not exactly what it is supposed so now I am going to delete the account on the mobile and rescan the QR code to be sure the Network ID will be OK!

 

[Vali_3CX]

You can check if client has been configured as you expected - just open account settings and look for server (PBX) address(es)

 

[Norclair]

You can check if client has been configured as you expected - just open account settings and look for server (PBX) address(es)

On the client side, there is no difference between the one that have the Network adress on the FQDN and the one that have the Network adress on the internal IP, on the mobile option we see Internal as our internal and External as our FQDN...

 

[Ompie00]

We have the same issue as Norclair since the last 2 beta updates. . It happens only with the beta app not with the normal app in the appstore. Our pbx is deployed on AWS Ligthsail

 

[Norclair]

We have the same issue as Norclair since the last 2 beta updates. . It happens only with the beta app not with the normal app in the appstore. Our pbx is deployed on AWS Ligthsail

The next BETA will adress those issue, they find 2 differents problem, the FQDN, and the Connexion waiting. For now we seam to see a amilioration of the failed call by replacing our FQDN by our internal IP, but the connexion waiting is still an issue, they are going to change the way the connexion is made to make it work. Now, we wait for the next BETA to find if the change will work!

 

[complex1]

Great that you were able to solve the issue in the latest release (16.1.1.323)
Thx.