My customer is using the old SDK 3.6.2, now they have compatibility issue with iOS 16.x, is it possible we fix it on top of SDK version 3.6.2? Learned from customer App developer, it may not be a big task.
Below is the suggestion from customer:
The possible reason is "iOS 16 with XCode 14 no longer support VOIP socket".
The possible solution is "Linked against modern SDK, VOIP socket will not wake. Use Local Push Connectivity instead"

"

dear support,

May I have an update? Thanks!

dear support,

Thanks for your reply!

This has been identified as an improvement which will be added in release 4.0.1, currently customer is using SDK 3.6.1.

If release new SDK 4.0.1 to customer, this could be a big problem to them because we need:
1, provide the simplified new SDK file, because App size is a concern;
2, customer will ask a meeting to review the code;
3, function test in UAT and then PRD system;

I want to know if this defect can be fixed by certain parameter, configuration or hot fix on top of version 3.6.1? Thanks!

dera support,

It's Reference Client version 3.6.1.0-2

dear support,

any feedback from Ref Client team? Thanks!

dear support,

May I have your answer on this query? This is a critical question from the biggest commercial bank of GC. Thanks!

dear support,

this is a log file downloaded from Avaya Refrence Client, not customer application, we found the "NullHostNameVerifier" in the Ref Client log. I don't know how to explain to customer it does not belongs to CSDK code.

May I trouble you again? and identify if our CSDK has "NullHostNameVerifier" code?

Thanks!

dear support,

In the SDK log, you can see the "NullHostNameVerifier" actually been used during the HTTPS session, please find the details in attahced picture.

Customer wants to know the reason and what "NullHostNameVerifier" actually did.

Thanks!

Customer noticed "NullHostNameVerifier" in our SDK, wants to know if and how this "NullHostNameVerifier" will be used, and in which scenario it will be used?
Thanks!

dear support,

I made a HTTP call through CSDK 3.6.1.0, attached pls find the log file.

May I know if the client log is necessary for troubleshooting. Customer uses certain security tool to scan our SDK, and find such issue.

Problem Description
we received a reporting from customer, the CMB bank, that our CSDK ver 3.6.1.0 is NOT verify hostname when establish HTTPS connection. As analyzed by customer developer team, CSDK is accepting any hostname when receiving identity cert from server side, which is recognized as a vulnerability. Customer suggested an article for reference, "http://pingguohe.net/2016/02/26/Android-App-secure-ssl.html"

The Topology
CSDK is embed into customer mobile App to provide WebRTC based voice communication, after requesting AAWG Token service in UAT system, or customer provided token service in production system, CSDK send HTTPS to SBC, and then to Breeze to save related call info to CS, then AAWG set up voice channel through SIP with participant of SBC/SM, then CSDK can talk with SBC.

Suggestion from Customer
Customer is suggesting Avaya to double check the “com/avaya/ocs/Base/Rest/NullHostNameVerifier” , and the article linked in above URL, to understand what they identified.

I found error code 8019, seems Ref Client only retrieve the prefix "24e0" of IPv6 address as remote address (for media), which is not a real IP address.

Dear experts,

I setup a IPv6 system, Internet--IPv6---F5/SBC-B1-IPv6-----SBC-A1-IPv4----AAWG(IPv4), when place a WebRTC call from Ref client to SBC, Ref client access SBC through IPv6, I can see at last the Media IP (public IPv6 address of SBC) received on Ref Client, but get error message "Start Media Failure" on Ref Client.

Per my understanding, HTTPS signaling is success, and Media IP (IPv6) received by Ref client, it should start to send UDP stream to the MediaIP+UDP Port to exchange audio.

Any suggestion? Thanks!

Dear all,

a bank customer setup WebRTC call on mobile App embeded with Avaya Oceana WebRTC SDK, now customer wants to have co-browsing feature to make agent can "see" what page the client is looking at, so that agent can instruct what and how to do.

At the client side, all operation is within mobile App, it's not using browser to open a Internet Web page.

May I know if our CoBrowsing snapin can support this requirement? Thanks!