Hello,

in the Android Client SDK there are options to set different modes for AutomaticGainControl and NoiseSuppression. There are some mdoes to set, but none of them are documented in the JavaDoc. I tried to set the different modes using

client.mediaEngine?.audioInterface?.noiseSuppressionMode = NoiseSuppressionMode.NATIVE

and equivalent to this the other modes
And:

client.mediaEngine?.audioInterface?.automaticGainControlMode = AutomaticGainControlMode.NATIVE

But I did not notice any effect. Could you please provide some information what the different modes should do and how they should be used?
Thanks!

Regards

Børge Grunicke

Hello,

there is no "RegistrationEndedByServer"-event. In the first post I already described:

When we test the same situation with our CSDK based app the new instance registeres and the old one receives some "onUserRegistrationFailed()" follwed by an "onUserAllRegistrationsFailed()".

Then it seems that it automatically tries to reconnect to the second SessionManager (described incl. logs in post #3) and the new registered devicve then also receives multipe times "onUserRegistrationFailed()" and then "onUserAllRegistrationsFailed()" as well.
The events for user unregistraion (onUserUnregistrationComplete, onUserUnregistrationSuccessful, onUserUnregistrationInProgress) events But all this are events that firing from SDK. This is only information i receive and nothing where i could block the reregistration. Again it looks to me like the ClienSDK does it automatically and I do not know how to prevent this. I talked to our specialists for the Aura system and they did not know anything to change a retry delay on server side.

Regards

Børge Grunicke

Hello,

the logs from the csdk are in the third post in this thread. i already posted ervything i have.

Regards

Børge

Hello,

thanks for explaining the documentation.
This method gets invoked by the sdk. so this is only an information i get from the sdk. i cant change this parameter to prevent it from misbehaving.
What can be done to prevent the sdk from doing reconnects where they should not be?

Regards

Børge

Hello,

I am using the UserRegistrationListener to observe the state. There are lots of events that could happen like "onUserUnregistrationSuccessful" and "onUserUnregistrationComplete" and so on. But as I noticed in the situation where another station takes the registration, none of them are called. the only thing i receive are some "onUserRegistrationFailed" for each SessionManager, with the message "SERVER_ENDED_ERROR" followed by an "onUserAllRegistrationsFailed". So what I am now doing is to collect the messages and if the "onUserAllRegistrationsFailed" appears i check if there was an "SERVER_ENDED_ERROR", to know if the extension was logged out by another device.

I/d.a.p.p.PhoneImpl: [main                ] onUserRegistrationFailed Registration failed: SERVER_ENDED_ERROR on server x.x.x.105

E/AvayaClientServices: CCertificateInformationLogger::CCertificateInfoLogger(): No certificates are available in certificate validation request.

I/d.a.p.p.PhoneImpl: [main                ] onUserRegistrationFailed Registration failed: SERVER_ENDED_ERROR on server x.x.x.125

I/d.a.p.p.PhoneImpl: [main                ] onUserAllRegistrationsFailed

    [main                ] ERROR-BUFFER : SERVER_ENDE_ERROR

I/d.a.p.p.PhoneImpl: [main                ] logged out by server -> flushing and notifying

But then it seems that the ClientSDK tries to automatically login again but only on the second SessionManager

I/d.a.p.p.PhoneImpl: [main                ] login credentials: <ext.> - <password>}

I/d.a.p.p.PhoneImpl: [main                ] login credentials: <ext.> - <password>}

I/d.a.p.p.PhoneImpl: [main                ] login credentials: <ext.> - <password>}

I/d.a.p.p.PhoneImpl: [main                ] login credentials: <ext.> - <password>}

I/d.a.p.p.PhoneImpl: [main                ] onCredentialAccepted: x.x.x.125 - our.uc.domain

I/d.a.p.p.PhoneImpl: [main                ] onCredentialAccepted: x.x.x.125 - our.uc.domain

I/d.a.p.p.PhoneImpl: [main                ] onCredentialAccepted: x.x.x.125 - our.uc.domain

I/d.a.p.p.PhoneImpl: [main                ] onAgentFeatureListChanged

I/d.a.p.p.PhoneImpl: [main                ] onAgentCapabilitiesChanged

I/d.a.p.p.PhoneImpl: [main                ] onCredentialAccepted: x.x.x.125 - our.uc.domain

I/zygote64: System.exit called, status: 0

I/AndroidRuntime: VM exiting with result code 0, cleanup skipped.

This results in the behaviour, that the client is still receiving call events even it should not be registered anymore.
What to do, to prevent the ClientSDK from loggin in again automatically?


Regards

Børge

Hello,

we have a situation where our customer wants to login an extension on a softphone but the same extension is already active on another device. Block new registrations is disabled and max registrations is set to 1, so the old instance should be logged out, when the new one registeres. It is configured to register with two regular and one survival SessionManager connections. We tested the behaviour using a 9611 phone and everything worked as expected. When we test the same situation with our CSDK based app the new instance registeres and the old one receives some "onUserRegistrationFailed()" events follwed by an "onUserAllRegistrationsFailed()".
It seems that there is only one registration canceled but the other registrations remain active. This results in call signaling even after the device was kicked off and some other strange logoff behaviour.
What is the proper way to detect that the extension was registered on a different device inside of the Android ClientSDK?

Regards

Børge

Hello,

this answer does not help me. I already read this thread a couple of times but it does not contain any helpful sample code. The second post contains a link to another thread where there is written:

CSDK has no built-in functionality to retrieve configuration from server, parse it and configure itself.
This functionality should be implemented by UI side.
The only thing that can provide CSDK to help you is to actually download file from server.
CSDK has DownloadService and the methods inside: DownloadFile, RetrieveDataFromUrl, RetrieveTextFromUrl.

So my current state is: I set the params in the autoconfiguration file, used the DownloadService to download the configuration but now it need to be processed. As already mentioned, I had a look at the "ConfigurationFileParser" which is an abstract class and needs to override the "setVariable()" manually.
So the question remains: how can I get the params received from autoconfiguration file into the instance of Client SDK?

Regards

Børge

Hi,

yes I am using the Android Client SDK (Version 4.15.0).
I tried to set these parameters in the auto configuration file but as far as I know, there is no option to automatically process the configuration file. I downloaded the configuration-file using "client.downloadService.retrieveTextFromUrl(downloadConfiguration, url, downloadCompletionHandler)". Within the SettingsFileParser i have to manually override the "setVariable()" method. So I have to set the variable manually or is there an option to automatically process the configuration-file?

Regards

Børge

Hi,

thanks for the reply. Where should I set these settings?


Regards

Børge

Hello,

in the Client SDK I found the new classes for elite agents. The AgentService is always null. The "user.agentServiceStatus" always returns

ServiceStatus {disabled - NOT_CONFIGURED}

For the station I configured the "agnt-login", "aux-work", "autoin", "manual-in" and "add-rem-sk" buttons.
What else is needed to get the clientservice configured?

Kind regards

Børge

Hello,
I'am working on a ClientSDK based Softphone on Android. After I prepared the client-object, I call

client.createUser(userConfiguration, createUserCompletionHandler)

.
In the

CreateUserCompletionHandler

always the

onSuccess()

gets invoked. Even if i pass in a wrong extension or password. As far as I understand the

onError(UserCreatedException)

should be invoked if the login does not work. So if I always get

onSuccess()

, how should I detect if the User is successfully logged in?


Regards


Børge.

Hi,
during the post waited to get accepted by an admin, i found the solution.
When setting the Userconfiguration the ppmConfiguration must be set as enabled even if no ppm is used.
After enabling and setting the same credentialProvider as for the sipUserConfig everything works fine.

Regards

Børge

Hi,

I have got some problems using the CallFeatureService. The CallService is working, so I can createCalls and so on. But when I try to use the

user.callFeatureService

i get a "true" when i check

user.callFeatureServiceStatus.isEnabled

and "NONE" for

user.callFeatureServiceStatus.disabledReason

But

user.callFeatureService.availableFeatures.size

is 0 and when i check the Capabilities for sendAllCalls or parkCall / unparkCall i always get "Capability {not allowed - INVALID_STATE}" The Buttons "Send all Calls" and "call-park" as well as "call-unpark" are administered for the station. When I test "call-park" with the same extension but using Equinox it works. Additionally I administered 2 Teambuttons but when check

user.callFeatureService.teamButtons.size

the result is 0. In the Equinox App I can see both administred Teambuttons. I think there is something wrong with the CallFeatureService. Can someone give me tips how to solve this?

Regards,


Børge

Hi,

i have got a problem with the android ClientSDK (CommunicationPackage). I cannot make a new call using the ClientSDK. I tried it on the Vantage Device and on my MobilePhone (Huawei P9 / Android 7.0).
Everytime I get:

E/AvayaClientServices: Call[4]: CSDPAudioHandler::SetLocalCapabilities(): There is no codec match between local and remote caps. Unable to proceed with call setup

Call[4]: CSDPOfferAnswerManager::SetLocalCapabilities(): Unable to initialize audio connection

The VantageBasic Application works but my own application as well as the sample application shipped with the ClientSDK always throws this error and no call is created.
Can anyone help me?

Regards,
Børge

Hi Dmitry,

I am using the same extension on my hardphone and in the ClientSDK. I also tested it with the Equinox application and it seems to work. When I check the ParkCallCapability it sais that it is Denied because of

InvalidState

.
When I try to execute the ParkCall method there appears no log output except my own.

Regards
Børge