You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -330,7 +330,7 @@ Incoming calls are received through the application's persistent internal server
330
330
331
331
There are two types of event handlers the SDK provides for a client app to respond to various events: a device-specific listener and a call-specific listener.
332
332
333
-
#### - Device-specific Listener
333
+
#### - Device-specific listener
334
334
335
335
Register a device-specific event handler using the `SendBirdCall.addListener()` method. It is recommended to add the event handler during initialization because it is a prerequisite for detecting an `onRinging()` event. The code below shows the way device-wide events such as incoming calls are handled once device-specific event is added.
|onAudioOutputDeviceChanged | Audio output devices have changed. |
361
361
|onVideoInputDeviceChanged | Video input devices have changed. |
362
362
363
-
#### - Call-specific Listener
363
+
#### - Call-specific listener
364
364
365
365
Register a call-specific event handler by attaching an event handler function directly to the properties of the call object. Responding to call-specific events such as establishing a successful call connection is then handled as shown below.
0 commit comments