3CX Client for iOS - BETA IPv6 Support

[StefanW]

Verizon and T-Mobile have switched their networks to IPV6. This BETA version of the 3CX client for iOS supports IPV6, including IPv6 to IPv4 (NAT64) mappings. We would like to invite you to sign-up as a pre-release user for our iOS client to get the latest builds before the official release. Users that are already subscribed to the beta program do ...

Continue reading the Original Blog Post.

 

[xero9]

But how do we enable IPv6 support in the 3CX phone system?

 

[Sopock]

They will use it only for Out of Office?
Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking. Most apps will not require any changes because IPv6 is already supported by NSURLSession and CFNetwork APIs.

 

[xero9]

The beta iOS app supports IPv6, but the server refuses connections on it. Not sure how much clearer one can be!

 

[craigreilly]

IPv6 to IPv4 NAT Mappings...
It works. I haven't had any issues.
Where exactly are you having issues? Calls? Presence?

 

[xero9]

So on the iOS client, what IP to I put in? I'm not familiar with NAT64 so I assumed I could put in my native IPv6 address (both my ISP and wireless carrier support dual stack).

Basically, I can't get the client to connect to the server. If I use my IPv4 address it works fine, but then that isn't IPv6

 

[craigreilly]

I do not put in any address. I send a welcome email from the 3cx Console to the user. They tap the attachment and it sets up the client automatically.

 

[somertech]

I can't say for certain but it seems like since running the beta build (15.2.5.13x and up) that battery life on my test phone has suffered appreciably.
Has anyone else observed reduced battery performance on their devices?

 

[tratz]

I am having issues with the beta where i get no audio when using the 4g LTE cell network. I am using Tmobile. If i am on wifi the audio works fine.

--Tracy

 

[Steele Burgess]

I have the same problem as Tracy. Nobody seems to know what the solution is. Thanks

 

[Vali_3CX]

@Steele Burgess
That issue was almost one year ago, IPv6-related, on client version 15.2.4. Current released version is 15.2.12, IPv6-ready. Nobody seems to have this problem any longer.