Solved FIXED Android beta 16.2.0.57 error "no matching transport found"

[dsi-infologic]

Hi,
since the last beta version 16.2.0.57 (11/01/2019) , the application can't make or receive a call ; it display the error message "no matching transport found"
all android phones in beta version have this issue (~20 phones).
Saumsung J9 or A20 Android 9
reboot tested and don't solve the issue.

revert to the stable version 16.1.0.41 solve the issue , but we loose a lot of functions ( roaming , contact search improvement , etc )

PBX version : 16.0.676 with static IP

BR
Stéphane

 

[Evolute IT]

Hi,
since the last beta version 16.2.0.57 (11/01/2019) , the application can't make or receive a call ; it display the error message "no matching transport found"
all android phones in beta version have this issue (~20 phones).
Saumsung J9 or A20 Android 9
reboot tested and don't solve the issue.

revert to the stable version 16.1.0.41 solve the issue , but we loose a lot of functions ( roaming , contact search improvement , etc )

PBX version : 16.0.676 with static IP

BR
Stéphane

Have you tried simply reprovisioning the app after update? This looks like a settings that isn't working anymore.

 

[dsi-infologic]

yes , re-provisionned but same problem
also an complete app reinstall does the same thing -> "no matching transport found"

 

[Evolute IT]

yes , re-provisionned but same problem
also an complete app reinstall does the same thing -> "no matching transport found"

What is the account transport config? UDP, TCP or TLS? Check also that the extension's config for 3CX App (under Phone Provisioning) is the same as the app.

 

[dsi-infologic]

transport config is UDP under the users extension. tested with TCP/TLS + re-provisionning : same problem

I do not find the transport settings under the 3CX app profile...

info : also tested as external ( through 4G + the tunnel ) and connected directly on internal wifi : same problem.

 

[Evolute IT]

transport config is UDP under the users extension. tested with TCP/TLS + re-provisionning : same problem

I do not find the transport settings under the 3CX app profile...

info : also tested as external ( through 4G + the tunnel ) and connected directly on internal wifi : same problem.

Have you tried deleting app data? Reinstalling the app generally keeps userdata present.

Try provisioning the same extension on another Android phone using the same app version. See if the error is reproduced.

 

[Pixelmatsch]

Another datapoint from me:
PBX 16.0.676 on static IP and 3cx FQDN
App 16.2.0.57 installed, UDP as transport
both on a Xiaomi A1 (Android one), Android 9 and Mi 9 (MIUI), Android 9.
Tried both on internal Wifi, same network as the PBX and through tunnel on 4G.
App data cleared, then uninstalled, then reinstalled and reprovisioned through QR.
Result is always "No matching transport found". Reverting to stable (41) solves the issue.

 

[dsi-infologic]

good idea !
Just tested : under applications->3CX-> storage, deleted cache and applicationdata.
deteled application then re-install : same problem :-(

installed on a new phone , with another google account and another profile to my pre-prod 3CX server : same issue.

 

[snits35m]

Same problem here.

 

[pasor1]

Same issue here.

 

[dsi-infologic]

same issue with 16.2.0.77

 

[nb]

We are checking as we speak.. We should have results in the next 1-2 hours. Top priority on this one.

 

[nb]

Guys Can you confirm that you have a non default sip port - NOT EQUAL to 5060?

 

[dsi-infologic]

yep , our SIP port is not 5060 for us; for security reasons we have decided to use another one ( I can give you it by private message )

but anyway , for internet and from the android app , we must use the tunnel , our SIP port is not public isn't it ?

 

[nb]

Yes the problem is with pbx's running on non default ports. We are working on it.
For your question: Internet I don't understand. You mean Web interface and Webclient - Yes.
Android app yes 5090 is enough. But only if you do not use any other phones.

So if you use Android clients only, you essentially need 5090 TCP And UDP and 443 (or your equivalent https port). But if you use any other phone that cannot use tunnel - example a hardphone, then you need to open sip port from the outside.

## The real problem is this:
When the android client connects, it contacts 5090.
But then after 5090 is reached, the tunnel acts like a proxy and bounces traffic from 5090 to the sip port.
The bug is here - the tunnel was patched to bounce traffic to sip port taken from provisioning.
If sip port = default, we hardcode it from the code.
Unfor if sip port is not equal to 5060, we use the port in provisioning, which is correct, but one of the sip fields is wrong. Should be without a port.

We are working on it. This issue was raised because of a fix we made for 1 way audio. Apparently it need ed more testing on different networks and setups / configuration.

Can others confirm about their sip port?

 

[dsi-infologic]

Android app needs https and tunnel only , ok with that and we are in this case.
we don't have external other phone on internet , so our SIP port is not opened.

so problem identified , we are waiting our next beta release with enthusiasm !
BR
Stéphane

 

[Pixelmatsch]

Yup, our SIP port is not 5060.

 

[nb]

Fix is on the way.. coming shortly..

 

[pasor1]

You're on the right way ... my system also is not on the default SIP port.

 

[nb]

Guys fix is in beta.. go get it from there.
version ends in 81.
Thank you all for reporting