Solved Cannot make call using Android App while on LTE

Status
Not open for further replies.

ZoloN

Free User
Advanced Certified
Joined
Jun 26, 2020
Messages
30
Reaction score
3
hi all,

I have a strange problem:
when I'm not on WiFi at home, I can't make any call. Receivig call works fine

3CX: appliance v 16.0.619 running on ESXi (installed from the Debian ISO)
Android App: 16.3.0.81 installed from Google Play Store
Mobile: Xiaomi Mi A3 running Android One, version 10 (on lastest security level)

when I open the 3CX App, it reports connected, showing green presence square, switching to Status tab: all online extensions are green (tunnel port 5090 for login and port 5001 for presence is working fine, I assume...)
when someone calls me, all is fine, call connected, audio comes thru
when I call someone (even 3CX internal extension), call isn't connected - small error message popup comes up "destination not found" - and in 3CX Management Console call log is in "To:" field following info: " type: 11, dn: DirectSIP"

what is going on?

/BR
ZoloN
 
Was it working previously?
Did you give extension right to be used outside LAN ?
 
hi aws2p,

Disallow use of extension outside the LAN checkbox is unchecked - it's the default value.
not sure, if it ever worked with my current installation, I had to solve some FW setup problems (and port collisions with my Internet provider) first.
I've tried it with another extension on Nokia 6.1 (again Android One, ver 10 on latest security patches) too - unfortunately with the same result......

all is working fine - I have succesfully configured RaspPBX on Raspberry Pi 3B with Huawei K3765 HSPA USB dongle as GSM gateway via SIP trunk, SPA3102 as PSTN gateway (and to connect analogue fax machine), some local number via Telnyx and Gigaset A510 IP as gateway to my DECT phones.

all is working fine in both directions - except that I can't make any call from Android App via tunnel!!!

/BR
Zoltan
 
***UPDATE***
I've performed 3CX backup of the Debian instance config, installed the windows version on Win2016 server, performed restore during installation, so I'm using the same config, IP and ports, changed nothing on network settings (firewall) - and, surprise-surprise, calls via Tunnel are working!

conclusion: there must be some bug in tunnel implementation on Debian distro.
looking to SIP capture, the incoming Invite message from the tunnel is routed to public FQDN instead of local IP causing quite strange loop, which the distro apparently cannot handle

/BR
ZoloN
 
****UPDATE 2****
initiating calls from 3CX Android App via LTE isn't working again - the problem isn't in tunnel itself or on 3CX side, but in App itself - see my other posting here

/BR
ZoloN
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK