Message |
[+]
Avaya Client SDK - General
» guest access mode support for CSDK 3.2, 30/07/2017 20:04:09
» Go to message
|
|
Hi Guys,
From CSDK 3.2, it support guest access mode, and I have tried it on Equinox 3.2 base on AVAYA office environment. How can we enable this feature and setup the call request for CSDK 3.2, and which kind of specific configurations are required for SBC and Equinox Management?
I suppose the topology for the guest access mode should be: CSDK 3.2(Android/iOS)---SBCE---Equinox Management---Equinox Media Server. Is is the right topology?
-Roger
|
|
[+]
Avaya Client SDK - General
» XCODE 8.x support, 21/06/2017 19:28:24
» Go to message
|
|
Hi Experts,
Do we have the plan to natively support XCODE 8.x? Since the latest version is 8.3, and Apple will release iOS 11 officially in the next couple of months. Our customer is wait for the native XCODE 8.x support, or they have to stay on XCODE 7.x to support background working mode and this is not a long term acceptable solution because they cannot leverage the advantages of XCODE 8 and iOS 10/11.
-Roger
|
|
[+]
Avaya Client SDK - General
» How to support background mode on iOS9,10?, 17/04/2017 20:52:25
» Go to message
|
|
Our customer is encounter the same kind of problem. For workaround, they use Xcode 7 to build their existing app for iOS 9 and 10 support. But it is just a workaround, because Xcode 7 is not designed to support iOS 10. Since the CSDK 3.1 can not be used in Xcode 8 for background mode supporting, I just want to confirm if the next release(3.2) may support this on Xcode 8?
|
|
[+]
Avaya Client SDK - General
» CSDK building issue for background mode support, 10/04/2017 19:29:02
» Go to message
|
|
Hi Experts,
We have tested if we want the background mode working on iOS 9 or 10 app with CSDK, we have to build the app by XCODE 7.x, if we build the app by XCODE 8.x with the same codes, it does not work any more. I just want to make sure if the XCODE edition leads this problem. If it does, when we may support XCODE 8?
-Roger
|
|
[+]
Avaya Client SDK - General
» CSDK iOS network transition issue, 10/04/2017 19:23:41
» Go to message
|
|
Hi Experts,
Has anyone encountered connection issue when the CSDK iOS transition from a network to another network? I have implemented background procession codes as our documents suggestion. I found when I put the demo app into background mode, and take the iOS device from one place to another, around half an hour later, it cannot get any incoming call. But if I put the iOS device onto the desktop for the same duration, it can work properly. I am not quite sure if it is a coding issue or CSDK bug. Can you give me some guide or advice to solve this problem?
-Roger
|
|
[+]
Avaya Client SDK - General
» Incoming Call Tone Playing issue, 09/04/2017 05:59:23
» Go to message
|
|
Hi Experts,
In most of the scenarios, the demo app can play incoming call tone when receives a incoming call. But for the below 2 kind of scenarios, the app do not play the tone. Please give me some advice how to fix the tone playing issue.
1st scenario, when the app completes registration to the Aura. It cannot play the incoming call tone for the first incoming call.
I caught the output from console:
2017-04-09 15:00:51.100 CommunicationSampleApp[4206:1882080] -[SDKManager callService:didReceiveIncomingCall:] (null) call(Call 1 (Alerting): 810228, 810228 <sip:810228@106.75.23.75:5080>)
2017-04-09 15:00:51.100 CommunicationSampleApp[4206:1882080] SCPAPI: -[CSAudioFilePlayerImpl startPlaying]
2017-04-09 15:00:51.100 CommunicationSampleApp[4206:1882080] CWebRTCAudioEngine[0x0x125808f30]::StartPlayingTone : tone:1 sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 15:00:51.101 CommunicationSampleApp[4206:1882080] CWebRTCAudioEngine[0x0x125808f30]::StartPlayingFileOnEventLoop : file:'ringinside.wav' sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 15:00:51.101 CommunicationSampleApp[4206:1882132] CWebRTCAudioEngine[0x0x125808f30]::StartPlayingFileOnEventLoop : file:'ringinside.wav' sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 15:00:51.420 CommunicationSampleApp[4206:1882132] CWebRTCAudioEngine[0x0x125808f30]::CreateFilePlayCall : m_nPlaybackChannelId: 0
2017-04-09 15:00:51.421 CommunicationSampleApp[4206:1882131] : WARNING ; (15: 0:51:421 | 1) TRANSPORT: 1 0; 25367; _localIP was not specified. RTP socket will be bound to all interfaces. IP = 0.0.0.0
2017-04-09 15:00:51.422 CommunicationSampleApp[4206:1882131] : WARNING ; (15: 0:51:422 | 1) TRANSPORT: 1 0; 25367; _localIP was not specified. RTCP socket will be bound to all interfaces. IP = 0.0.0.0
2017-04-09 15:00:51.440 CommunicationSampleApp[4206:1882132] 15:00:51.439 ERROR: [Avaya Media Services Event Loop] 1233: AUIOClient_StartIO failed (-66637)
2017-04-09 15:00:51.440 CommunicationSampleApp[4206:1882131] : ERROR ; (15: 0:51:440 | 17) AUDIO DEVICE: 1 99; 25367; StartPlayout: Failed to start playout. Error code: -66637. Line: 1549
2017-04-09 15:00:51.440 CommunicationSampleApp[4206:1882132] CWebRTCAudioEngine[0x0x125808f30]::DestroyFilePlayCall : m_nPlaybackChannelId: 0
2017-04-09 15:00:51.440 CommunicationSampleApp[4206:1882131] : ERROR ; (15: 0:51:440 | 0) VOICE: 1 99; 25367; StartPlayout() failed to start playout
2017-04-09 15:00:51.441 CommunicationSampleApp[4206:1882131] : ERROR ; (15: 0:51:440 | 0) VOICE: 1 99; 25367; StartPlayout() failed to start playout, error = 10028
2nd scenario, when I put the app to background for 15 min or longer, it cannot play the incoming call tone for the next incoming call. I have already implemented background code to wake up the app every 10 min for re-registration.
Here is my codes:
- (void)applicationDidEnterBackground:(UIApplication *)application {
NSLog(@"KeepAlive?????%f?",UIMinimumKeepAliveTimeout);
[application setKeepAliveTimeout:UIMinimumKeepAliveTimeout handler:^{
[self.client prepareForBackgroundInterval:UIMinimumKeepAliveTimeout];
}];
}
I caught the xocde console output for this scenario and found it indicates "Failed to initialize Audio Unit". Console output:
2017-04-09 18:36:32.099 CommunicationSampleApp[4319:1931665] -[SDKManager callService:didReceiveIncomingCall:] (null) call(Call 1 (Alerting): 810228, 810228 <sip:810228@106.75.23.75:5080>)
2017-04-09 18:36:32.101 CommunicationSampleApp[4319:1931665] SCPAPI: -[CSAudioFilePlayerImpl startPlaying]
2017-04-09 18:36:32.102 CommunicationSampleApp[4319:1931665] CWebRTCAudioEngine[0x0x1265e1c10]::StartPlayingTone : tone:1 sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 18:36:32.102 CommunicationSampleApp[4319:1931665] CWebRTCAudioEngine[0x0x1265e1c10]::StartPlayingFileOnEventLoop : file:'ringinside.wav' sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 18:36:32.102 CommunicationSampleApp[4319:1931930] CWebRTCAudioEngine[0x0x1265e1c10]::StartPlayingFileOnEventLoop : file:'ringinside.wav' sessionId:-1 loop:1 durationMs:0 gain:255 speaker: 1 callback:1
2017-04-09 18:36:32.329 CommunicationSampleApp[4319:1931930] 18:36:32.328 ERROR: [Avaya Media Services Event Loop] >aurioc> 807: failed: '!int' (enable 1, outf< 1 ch, 0 Hz, Float32> inf< 1 ch, 16000 Hz, Int16>)
2017-04-09 18:36:32.329 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:329 | 226) AUDIO DEVICE: 1 99; 27667; InitializeAudioUnit: Failed to initialize Audio Unit. Line: 512
2017-04-09 18:36:32.330 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:329 | 0) AUDIO DEVICE: 1 99; 27667; int webrtc::AudioDeviceIOS::InitializeRecordingAudioUnit(): Failed to create recoriding audio unit instance. Line: 464
2017-04-09 18:36:32.330 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:329 | 0) VOICE: 1 99; 27667; StartRecording() failed to start recording. Will deregister monitor module
2017-04-09 18:36:32.330 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:330 | 1) VOICE: 1 99; 27667; failed to start recording
2017-04-09 18:36:32.330 CommunicationSampleApp[4319:1931930] CWebRTCAudioEngine[0x0x1265e1c10]::CreateFilePlayCall : m_nPlaybackChannelId: 0
2017-04-09 18:36:32.334 CommunicationSampleApp[4319:1931929] : WARNING ; (18:36:32:333 | 1) TRANSPORT: 1 0; 27667; _localIP was not specified. RTP socket will be bound to all interfaces. IP = 0.0.0.0
2017-04-09 18:36:32.334 CommunicationSampleApp[4319:1931929] : WARNING ; (18:36:32:334 | 1) TRANSPORT: 1 0; 27667; _localIP was not specified. RTCP socket will be bound to all interfaces. IP = 0.0.0.0
2017-04-09 18:36:32.349 CommunicationSampleApp[4319:1931930] 18:36:32.349 ERROR: [Avaya Media Services Event Loop] >aurioc> 807: failed: '!pla' (enable 2, outf< 2 ch, 16000 Hz, Int16, inter> inf< 1 ch, 0 Hz, Float32>)
2017-04-09 18:36:32.349 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:349 | 14) AUDIO DEVICE: 1 99; 27667; InitializeAudioUnit: Failed to initialize Audio Unit. Line: 512
2017-04-09 18:36:32.349 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:349 | 0) AUDIO DEVICE: 1 99; 27667; int webrtc::AudioDeviceIOS::InitializePlayoutAudioUnit(): Failed to create playout audio unit instance. Line: 442
2017-04-09 18:36:32.350 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:350 | 1) VOICE: 1 99; 27667; StartPlayout() failed to start playout
2017-04-09 18:36:32.350 CommunicationSampleApp[4319:1931929] : ERROR ; (18:36:32:350 | 0) VOICE: 1 99; 27667; StartPlayout() failed to start playout, error = 10028
|
|
[+]
Avaya Client SDK - General
» CSDK iOS entering background mode issue, 07/04/2017 23:29:55
» Go to message
|
|
Thank you! It works. I added some codes as following:
AppDelegate.h
@property (nonatomic, strong) CSClient *client;
AppDelegate.m
- (void)applicationDidEnterBackground:(UIApplication *)application {
// Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later.
// If your application supports background execution, this method is called instead of applicationWillTerminate: when the user quits.
[application setKeepAliveTimeout:UIMinimumKeepAliveTimeout handler:^{
[self.client prepareForBackgroundInterval:UIMinimumKeepAliveTimeout];
}];
MediaManager.h
#import "AppDelegate.h"
MediaManager.m
- (id)initWithClient: (CSClient *)client {
if (self = [super init]) {
_appDelegate = (AppDelegate*)[[UIApplication sharedApplication] delegate];
_appDelegate.client = self.client;
}
return self;
}
But I found, when the iOS demo app went to background for a while, it can receive SIP invite message, but it do not ring anymore. Is it a bug? Because for at the first minute it turns to background, it do ring when receive SIP invite. Can anyone give me some advice?
|
|
[+]
Avaya Client SDK - General
» CSDK iOS entering background mode issue, 05/04/2017 23:10:04
» Go to message
|
|
I have checked the solution, it looks a common solution for VoIP backgroundtask implementation. I am not quite sure if there is any specific code I should implement for the CSDK connection to Aura CM/SM. Customer plan to put the solution on production from next Monday, so the time is very limited for us to guide our customer how to implement CSDK background working mode. Can you give me some example code for our CSDK implementation, so that I may try it as soon as possible in our lab environment?
|
|
[+]
Avaya Client SDK - General
» CSDK iOS entering background mode issue, 28/03/2017 06:50:07
» Go to message
|
|
I have ever tried to enable voip capability for the background mode. But in the customer environment, the problem stays the same as before. Please check the attached screenshot. Do you have any advice?
|
|
[+]
Avaya Client SDK - General
» CSDK iOS entering background mode issue, 25/03/2017 03:23:58
» Go to message
|
|
Hi Experts,
I am encountering a very strange issue about CSDK iOS background mode. When I push the home button on my iPhone 6(iOS9.2), from this time, I cannot receive any incoming call, even I cannot get any incoming call event on my Xcode console. The mobile application for my testing is sampApp for CSDK iOS, release 3.0.0.1, which is downloaded from Devconnect. Can anyone give some advice for this issue? Here I post the Xcode console output at the time I push the home button.
By the way, I noted that there is one function in CSDK API may be related about the background mode support. I attached the screenshot for the API reference to this post. If this is the way to solve the problem, is there any specific configuration should be done on CM or SM?
2017-03-24 16:25:29.250 CommunicationSampleApp[4634:1386355] CSSystemEventsMonitor::enteredBackground()
2017-03-24 16:25:29.250 CommunicationSampleApp[4634:1386355] CSystemEventsProvider::NotifyApplicationNotVisible()
2017-03-24 16:25:29.250 CommunicationSampleApp[4634:1386355] CSCellularCallMonitor::enterBackground
2017-03-24 16:25:29.253 CommunicationSampleApp[4634:1386805] CCollaborationManager::OnApplicationNotVisibleNotificationReceived() this[0x174365880] :
2017-03-24 16:25:29.253 CommunicationSampleApp[4634:1386805] CCallServiceImpl::OnApplicationNotVisibleNotificationReceived()
2017-03-24 16:25:29.253 CommunicationSampleApp[4634:1386805] ThreadId[0x16e687000] COperatingMeasurementsCollector::OnApplicationNotVisibleNotificationReceived()
2017-03-24 16:25:29.253 CommunicationSampleApp[4634:1386805] ThreadId[0x16e687000] COperatingMeasurementsCollector::OnApplicationNotVisibleNotificationReceived() OM: Collection Timer has been adjusted to backgound mode : 1800 (s)
2017-03-24 16:25:29.254 CommunicationSampleApp[4634:1386805] CPresenceServiceImpl::OnApplicationNotVisibleNotificationReceived()
2017-03-24 16:25:29.254 CommunicationSampleApp[4634:1386805] CSIPPresenceManager::OnApplicationNotVisibleNotificationReceived()
2017-03-24 16:25:29.254 CommunicationSampleApp[4634:1386805] CSIPPresenceManager::ApplicationVisibilityChanged()
2017-03-24 16:25:29.260 CommunicationSampleApp[4634:1386805] CPresenceServiceImpl::StartAwayPollingTimer()HasCalls:false SelfPresence:0 ForceStart:false
2017-03-24 16:25:29.260 CommunicationSampleApp[4634:1386805] CPresenceServiceImpl::StartAwayPollingTimer()started with timeout:600000 ms
2017-03-24 16:25:29.278050 CommunicationSampleApp[4634:1386355] Cannot snapshot view (<UIKeyboardImpl: 0x102b24ac0; frame = (0 0; 320 216); layer = <CALayer: 0x174031940>>) with afterScreenUpdates:NO, because the view is not in a window. Use afterScreenUpdates:YES.
|
|