Skip to content

Commit 69ac325

Browse files
authored
Fix acrolinx error
1 parent 6226d48 commit 69ac325

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/communication-services/how-tos/calling-sdk/callkit-integration.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
1111

1212
# Integrate with CallKit
1313

14-
In this document we will go through how to integrate CallKit with your iOS application.
14+
In this document, we'll go through how to integrate CallKit with your iOS application.
1515

1616
> [!NOTE]
1717
> This API is provided as a preview for developers and may change based on feedback that we receive. Do not use this API in a production environment. To use this api please use 'beta' release of Azure Communication Services Calling iOS SDK
@@ -60,7 +60,7 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
6060
options.callKitRemoteInfo = CallKitRemoteInfo()
6161
```
6262

63-
1. Assign value for `callKitRemoteInfo.displayNameForCallKit` to customize display name for call recipients and configure `CXHandle` value. This value specified in `displayNameForCallKit` is exactly how it will show up in the last dialled call log.
63+
1. Assign value for `callKitRemoteInfo.displayNameForCallKit` to customize display name for call recipients and configure `CXHandle` value. This value specified in `displayNameForCallKit` is exactly how it will show up in the last dialed call log.
6464

6565
```Swift
6666
options.callKitRemoteInfo.displayNameForCallKit = "DISPLAY_NAME"
@@ -80,7 +80,7 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
8080

8181
Configure the properties of `CallKitOptions` instance:
8282

83-
Block that is passed to variable `provideRemoteInfo` will be called by the SDK when we receive an incoming call and we need to get a display name for the incoming caller which we need to pass to the CallKit.
83+
Block that is passed to variable `provideRemoteInfo` will be called by the SDK when we receive an incoming call and we need to get a display name for the incoming caller, which we need to pass to the CallKit.
8484

8585
```Swift
8686
callKitOptions.provideRemoteInfo = self.provideCallKitRemoteInfo
@@ -126,7 +126,7 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
126126

127127
### Handle incoming push notification payload
128128

129-
When the app receives incoming push notification payload, we need to call `handlePush` to process it. With this API we can raise the `IncomingCall` event.
129+
When the app receives incoming push notification payload, we need to call `handlePush` to process it. ACS Calling SDK will then raise the `IncomingCall` event.
130130

131131
```Swift
132132
public func handlePushNotification(_ pushPayload: PKPushPayload)
@@ -143,7 +143,7 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
143143
```
144144

145145
We can use `reportIncomingCallFromKillState` to handle push notifications when the app is closed.
146-
`reportIncomingCallFromKillState` API should not be called if `CallAgent` instance is already available when push is received.
146+
`reportIncomingCallFromKillState` API shouldn't be called if `CallAgent` instance is already available when push is received.
147147

148148
```Swift
149149
if let agent = self.callAgent {
@@ -178,8 +178,8 @@ description: Steps on how to integrate CallKit with ACS Calling SDK
178178

179179
## CallKit Integration (within App)
180180

181-
If you wist to integrate the CallKit within the app and not use the CallKit implementation in the SDK , please take a look at the quickstart sample [here](https://github.com/Azure-Samples/communication-services-ios-quickstarts/tree/main/Add%20Video%20Calling).
182-
But one of the important thing to take care of is to start the audio at the right time. Like following
181+
If you wish to integrate the CallKit within the app and not use the CallKit implementation in the SDK, please take a look at the quickstart sample [here](https://github.com/Azure-Samples/communication-services-ios-quickstarts/tree/main/Add%20Video%20Calling).
182+
But one of the important things to take care of is to start the audio at the right time. Like following
183183

184184
```Swift
185185
let mutedAudioOptions = AudioOptions()
@@ -194,7 +194,7 @@ callAgent.startCall(participants: participants,
194194
completionHandler: completionBlock)
195195
```
196196

197-
This will ensure that physical audio devices are not used until the CallKit calls the `didActivateAudioSession` on `CXProviderDelegate`. Otherwise the call may get dropped or no audio will be flowing.
197+
Muting speaker and microphone will ensure that physical audio devices aren't used until the CallKit calls the `didActivateAudioSession` on `CXProviderDelegate`. Otherwise the call may get dropped or no audio will be flowing.
198198

199199
```Swift
200200
func provider(_ provider: CXProvider, didActivate audioSession: AVAudioSession) {
@@ -211,7 +211,7 @@ func provider(_ provider: CXProvider, didActivate audioSession: AVAudioSession)
211211
}
212212
```
213213

214-
NOTE: In some cases CallKit does not call `didActivateAudioSession` even though the app has elevated audio permissions, in that case the audio will stay muted until the call back is recieved. And the UI has to reflect the state of the speaker and microphone. The remote participant/s in the call will see that the user has muted audio as well. User will have to manually unmute in those cases.
214+
NOTE: In some cases CallKit doesn't call `didActivateAudioSession` even though the app has elevated audio permissions, in that case the audio will stay muted until the call back is received. And the UI has to reflect the state of the speaker and microphone. The remote participant/s in the call will see that the user has muted audio as well. User will have to manually unmute in those cases.
215215

216216
## Next steps
217217
- [Learn how to manage video](./manage-video.md)

0 commit comments

Comments
 (0)