Solved Latest Android beta 16.2.0.37 cant make any call

[nobody]

Any number, even internal ones like echo test will be responced with "not found". pbx is 16.0.3.676, Client is 16.2.0.37
I restarted mobile phone, pbx, uninstalled 3cx client, reinstalled. No change.

In the log the following line appears - making a call from the mobile (13) to the extension 10.:

10/18/2019 1:29:33 PM - Call(C:4) is terminated

10/18/2019 1:29:33 PM - [CM503020]: Call(C:4): Normal call termination. Call originator: Extn:13. Reason: Not found

10/18/2019 1:29:33 PM - [CM503016]: Call(C:4): Attempt to reach <sip:[email protected]:0> from Extn:13 has failed. Reason: Not Found

10/18/2019 1:29:33 PM - [CM503014]: Call(C:4): No known route from Extn:13 to target: <sip:[email protected]:0/UDP>

10/18/2019 1:29:33 PM - Call(C:4): from Extn:13 to 10 doesn't match any known extension number.

10/18/2019 1:29:33 PM - [Flow] Call(C:4): Direct SIP call to <sip:[email protected];tag3cx=6f105eb6-df86-4aa7-b12f-3e47ce969683>

10/18/2019 1:29:33 PM - [CM503010]: Call(C:4): Making route(s) from Extn:13 to <sip:[email protected]:0/UDP>

10/18/2019 1:29:33 PM - [CM505001]: Endpoint Extn:13: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 16.2.0.37] PBX contact: [sip:[email protected]:5060]

 

[nobody]

followup: incoming calls work fine.

 

[nobody]

Please Moderators: I seem to have missed to anonymize my public ip in the first post of this thread. It would be great if this can be fixed! [moderator: edited as per your request]

Calling works again with new Version 16.2.0.44:

10/19/2019 12:08:53 PM - [Flow] Endpoint Extn:10 has no forwarding rule on reason 'All calls'
10/19/2019 12:08:53 PM - [Flow] No office hours set, office hours assumed
10/19/2019 12:08:53 PM - [Flow] Call(C:14): has built target endpoint: Extn:10 for call from L:14.1[Extn:13]
10/19/2019 12:08:53 PM - [Flow] Target endpoint for 10 is Extn:10
10/19/2019 12:08:53 PM - [Flow] Building target endpoint to 10 from "Some Username" <sip:[email protected]:0>
10/19/2019 12:08:53 PM - [CM503010]: Call(C:14): Making route(s) from Extn:13 to <sip:[email protected]/UDP>
10/19/2019 12:08:53 PM - [CM505001]: Endpoint Extn:13: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 16.2.0.44] PBX contact: [sip:[email protected]:5060]

 

[nobody]

I have to admit, i was wrong when I found out making calls is now possible.
Instead it behaves rather like in this post:

https://www.3cx.com/community/threads/v16-0-3-new-android-app-request-failed-on-calls.68575/unread

Making a call using the wifi Inside the perimeter of the pbx network is fine. But any call which connects through the wan of the pbx fails.

 

[Vali_3CX]

One of the major differences between the new and the legacy client is that the new client ALWAYS use tunnel, so be sure to verify in the Management Console extension's "Disallow use of remote tunnel" (or something like this) options parameter.

 

[nobody]

I checked these, and everything is ok, also I can receive calls fine using the encrypted tunnel.
Even if the logs will be the same as previous, to be safe, I made two new calls with logs.
I attached these instead of posting direct. From the logs I think one can see the tunnel works fine.
And also from the logs I cannot even guess why the call cannot be made.
One interesting point is:
From the Failed-call.log
Direct SIP call to <sip:[email protected];tag3cx=6f105eb6-df86-4aa7-b12f-3e47ce969683>

This does not occur in the Success-call.log. Instead here it reads:
Building target endpoint to 10 from "Some Username" <sip:[email protected]:0>

I replaced my personal data as follows:
MY.PUBLIC.IP.ADDR = public IP Address of the phone system
"my Extension Name" = Name of the Extension
PBX.PRIVATE.IP.ADDR = internal Lan Address of the pbx
MOBILE.PRIVATE.IP.ADDR = mobile phone internal Lan Address

 

[JohnS_3CX]

Hi @nobody

To save time, can the official non-beta app, on the exact same phone, with the exact same provisioning file work as intended via the same PBX?

 

[nobody]

Yes, the official Version works ok (did not use the provisioning file, but scanned the code - how would one manage to skip the setup assistant without scanning a barcode?) with Wifi or LTE . On the same phone. Last reset of the account I made was at the 18th Oct, after 16.2.0.37 showed this problem.

 

[JohnS_3CX]

Ok I ran a test now, using V16U3 + app V16.2.0.44

External access via FQDN works fine, calls made successfully on an LTE connection

 

[nobody]

But not here. Something must be different.
What do you think about those two logfiles? Why does the pbx in the case of the failed call thinks a direct SIP call is happening(for testing i also tried to enable this feature, but did not help)?

 

[nobody]

Additional:
Reinstalled Beta: Problem is there again
Used a vpn to connect to the pbx network, then tried the beta: Problem is gone (as expected)

 

[nb]

This not found is related to a DNS resolution issue.
My assumption is that you are using DYN DNS or some other service to try to keep your newly changed IP Address in sync with your FQDN.

Can you confirm that my analysis is correct?

1. Are you on Dynamic ip or static (on server)
2. Did the public ip change recently?
3. Restart the 3c;x services, rep=rovision the phone and try and see if it works or not after this change keeping the 3CX android version the same.

Thanks

 

[nobody]

I use a static ip, dns has not changed. I use my own fqdn.
However, I have set the configuration of 3cx to dynamic ip. This will enable at least a little redundancy if my primary line goes down (pbx will still work in case of outage, but will be not reachable from the internet for remote phones).
I can give you access to the pbx if you think that will help.

 

[nb]

Send me a welcome email on [email protected] and send me an email on same address to start a conversation.

 

[nobody]

you mean I should create an extension on the pbx for you. Correct?

 

[nb]

you mean I should create an extension on the pbx for you. Correct?

yes create an extension - i'll get the welcome email to provision a client whereby I will connect to your pbx. Then we can discuss via email. [email protected]

 

[nb]

New build in beta - we found an issue that occurs either when you have 2 ips on the firewall or when you have dual nics..
Check it out - not found should be fixed.

 

[nb]

New build in beta - we found an issue that occurs either when you have 2 ips on the firewall or when you have dual nics..
Check it out - not found should be fixed.

 

[nobody]

Fine! I can confirm the problem is gone.