Unable to successfully place call from one client to another..

Status
Not open for further replies.

pacpac

Forum User
Joined
Jan 12, 2012
Messages
87
Reaction score
1
Hi, I am unable to place a call from one client (iPad with 3CX app) connected to wi-fi, ext 201, to another client (iPhone with 3cx app), ext 200, connected to the cellular network. The iPhone rings, when I answer, I hear nothing and the client on the iPad continues to ring. Using 3CX v 15.5. I see this in the activity log:

11/17/2018 8:47:01 AM - [CM503003]: Call(C:19): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

11/17/2018 8:47:09 AM - Call to T:Extn:200@[Dev:local] from L:19.1[Extn:201] failed, cause: Cause: BYE from 127.0.0.1:5080

The firewall checker is OK. When I initiate the call from the iPhone (still on the cellular network) to the iPad (still on the wi-fi network), all is fine. But, the other way, no luck. Also, when both clients are on the same wi-fi, calls both ways are fine.

Ideas?
 
Hi @YiannisH_3CX,

Any update on this, This is affecting a few of our customers and we'd like to be able to give a timeline to fix this.

Kind regards.
 
Any update on this, This is affecting a few of our customers and we'd like to be able to give a timeline to fix this.
We have been able to identify the source of the issue and we are currently working on possible solutions to fix this. Unfortunately i cannot provide an ETA since the fix is not final and more testing needs to be done.
 
  • Like
Reactions: Matt_MTech
Is it possible to have an update on this please. We have a new customer, that's very keen to be using inbound calls to his 3CX app whilst out and about on his mobile.

As a work around, we set his extensions AWAY profile to Call his mobile. He then dials *31 when he leaves the Office, then *30 on is return. Then he can use the 3CX app (or from the 3CX for Windows. If he needs to he can also change the profile from the 3CX app too. THis also works if the extension is in the Call Group, but make sure you select that option on the AWAY profile page.
 
Please note that we have released a new Beta version that should fix the issue you are facing. You can enrol in the Beta program from here: https://www.3cx.com/blog/releases/uc-android-client-beta/
Please install the latest version and provide us with some feedback so we can try and improve the client even more.
 
Hi YiannisH_3CX

You have posted a link to the Android App - BUT the problem identified only affects the Apple IOS APP, where it is running on an iPhone/iPad that has an IPV6 IP address (e.g. EE network in the UK). Androids phones with an IPV6 on EE did not appear to be affected.
 
Problem exists on Android aswell.

I've just tried the beta:

  • Unable to pick up calls on the android client.
  • When I dial out the recipient answers but the call ends immediately for them.

UK using EE.
 
Ah, OK sorry JonathanA, I didn't spot your survey saying you had both - we tested here and 3CX Android was OK on a new looking Samsung phone (curved style screen - Sorry not sure of exact model number) where it's on EE SIM card and when you google for IP, it returns an IPV6 IP address.
 
I've just tried the beta:

  • Unable to pick up calls on the android client.
  • When I dial out the recipient answers but the call ends immediately for them.
UK using EE.
Thank you for the feedback. We will look into the outbound calls issue.
 
Ah, OK sorry JonathanA, I didn't spot your survey saying you had both - we tested here and 3CX Android was OK on a new looking Samsung phone (curved style screen - Sorry not sure of exact model number) where it's on EE SIM card and when you google for IP, it returns an IPV6 IP address.
We are working on a iOS client as well but it is a longer process. For now we have the Android client.
 
Hi there,

Is there any further news on an iOS fix please?

Thank you
 
3CX Support team - EE has one of the largest market shares of the UK mobile market. iPhone shares the market with Android as the largest mobile software firmware. Your software is not compatible when the two things are married together. Needless to say - this isn't even remotely good enough.

This issue was flagged in November last year, 7 months ago. You still haven't resolved it.

When is the fix going to be available?
 
Status
Not open for further replies.

Forum statistics

Threads
112,089
Messages
590,697
Members
165,056
Latest member
PANAMERICANAGLOBAL