The CSDK components require to check system information. It happens every 1 minute for foreground mode and every 30 min for background. These logs will be added every time. It is required for debugging and it is regular behavior.

The crash in AvayaClientServices -[CSLocalContactMac initializeAddressBook] method. This method checks access to address book using next code:

_localAddressBook  = [ABAddressBook sharedAddressBook];

	

if (_localAddressBook)

{

	self.addressBookAccessGranted = YES;

}

else

{

	LOG(DEBUG) << "Access to addressbook is not granted";

}

The MacOS method ABAddressBook should return nil if user denies access to the Address Book database. Could you please provide access and repeat testing?

Could you please also collect client logs and I will open a JIRA to track this issue.

Could you please provide client logs or call stack to investigate the crash.

btw, you can check documentation how to configure SIP server:
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/macos/communication/tech/initializing_sdk.gsp

The code is also available in the sample app, so you can find the difference.

Unfortunately we don't have MeiZu Pro5, so we are waiting for logs to continue investigation.

When the call will be answered from MDA extension, the User will receive "Established" event:
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/windows/communication/api_refs/html/E_Avaya_ClientServices_Call_Established.htm

You can check "Remote" property of the call and it will be true. It means that the User will be able only accept this call. Because the call has been accepted from related extension:
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/windows/communication/api_refs/html/P_Avaya_ClientServices_Call_Remote.htm

Could you please collect and attach client logs? I will open a JIRA to track this issue.

I have tested Android Sample app on Meizu m1 note and I'm able to set speaker and headphones to play audio.

AudioInterface.getDevices() has simple interface. It returns audio devises available on your Android phone.
Could you please provide more info?
Do you have HANDSET device connected? Is this reproducible for all your Android phones?

From logs I see that you don't have configured video for the call. Did you set video mode and video channels before start?
Please check this doc:
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/ios/communication/guide/making_a_video_call.gsp

When the user has been successfully unregistered, it receives didUnregisterWithServer event if you have set CSUserRegistrationDelegate delegate.
If you are not able to receive this event from background, then you can check services status. For example, you can check callServiceStatus that available from the user object.

Let's continue discuss in https://www.devconnectprogram.com/forums/posts/list/0/21674.page#p152085

Could you please provide more info about your environment? Do you use Headset API for interaction with handset or it is different device (Avaya phone) that has been registered om the same extension as Client SDK application (MDA) or you have registered Client SDK in shared control mode to control your device?

If you want to control a desk phone to accept the call remotely, then you need to connect Client SDK in shared control mode:
https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/windows/communication/api_refs/html/T_Avaya_ClientServices_SharedControlService.htm
If you place the call from Client SDK then it will be placed on controllable device. If you end the call on Client SDK, then it will be ended on the controllable device also.

When you get the second incoming call you can save call object in the call map and process with new call object like with regular call. You can create new view with call appearances to show for the User that he has many calls. Then you can create the button to merge the calls.

The limitation in the Sample app exists because it has simple design without call appearances and hold /unhold/merge buttons.

You can find how to merge calls in the following guide - https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/android/communication/tech/developing_conf_app.gsp

Hi,

I will try to reproduce this using our environment. Could you please attach your logs meanwhile?

AMM server has default limit - 15 messages, but you can get older messages using retrieveMessagesBefore method of Conversation object. To check capability use getOlderContentCapability method.