Android Mobile SDK to easily integrate communication features (WebRTC, messaging, presence, voice, video, screensharing) based on RestComm into native Mobile Applications
When trying to issue https requests towards RC/8443 for push related stuff, if RC presents self-signed cert it fails. We need to have a way to use this on our test servers where self-signed certs are used.
Here are the impacts:
Update all http domain SDK parameters (i.e. PUSH_NOTIFICATIONS_PUSH_DOMAIN and PUSH_NOTIFICATIONS_HTTP_DOMAIN) so that they can also can also accept the http(s):// prefix. If it's left out we can default to https, but if it is passed we should use what is passed
Rename RCDevice.ParameterKeys.DEBUG_JAIN_DISABLE_CERTIFICATE_VERIFICATION to RCDevice.ParameterKeys.DEBUG_DISABLE_CERTIFICATE_VERIFICATION and make sure it affects both JainSip and https calls made from FcmConfigurationClient towards Restcomm Connect and Push Server.
When trying to issue https requests towards RC/8443 for push related stuff, if RC presents self-signed cert it fails. We need to have a way to use this on our test servers where self-signed certs are used.
Here are the impacts:
PUSH_NOTIFICATIONS_PUSH_DOMAINandPUSH_NOTIFICATIONS_HTTP_DOMAIN) so that they can also can also accept thehttp(s)://prefix. If it's left out we can default to https, but if it is passed we should use what is passedRCDevice.ParameterKeys.DEBUG_JAIN_DISABLE_CERTIFICATE_VERIFICATIONtoRCDevice.ParameterKeys.DEBUG_DISABLE_CERTIFICATE_VERIFICATIONand make sure it affects both JainSip and https calls made from FcmConfigurationClient towards Restcomm Connect and Push Server.