@@ -584,12 +584,12 @@ callSession.on("disposed", () => {
584
584
585
585
### CallSession Events
586
586
587
- ### ` answered ` event
587
+ #### ` answered ` event
588
588
589
589
- Triggered when the call is answered.
590
590
- Note: There is a [ known issue] ( #known-issue ) affecting outbound calls.
591
591
592
- ### ` disposed ` event
592
+ #### ` disposed ` event
593
593
594
594
- For answered calls, this event is triggered when either you or the remote peer
595
595
hangs up.
@@ -598,7 +598,7 @@ callSession.on("disposed", () => {
598
598
- For outbound calls, if call failed (for example, invalid callee number), it
599
599
will be disposed automatically. So, this event will be triggered.
600
600
601
- ### ` failed ` event
601
+ #### ` failed ` event
602
602
603
603
- This is for outbound call only. It means the outbound call was not successful
604
604
- It may be caused by invalid target number
@@ -643,6 +643,22 @@ if (callSession.state === "failed" || callSession.state === "disposed") {
643
643
Failed call sessions will be disposed automatically, so the state will become
644
644
"disposed". "failed" is just a temporary state.
645
645
646
+ #### ` mediaStreamSet ` event
647
+
648
+ This is triggered when ` callSession.mediaStream ` is set. An interesting use case
649
+ is to apply noise reduction to this object.
650
+
651
+ ``` ts
652
+ callSession .on (" mediaStreamSet" , (mediaStream ) => {
653
+ console .log (" a new mediaStream object is set" );
654
+ });
655
+ ```
656
+
657
+ When you make an outbound call: ` const callSession = await webPhone.call(...) ` ,
658
+ at the time that you get the ` callSession ` object, ` callSession.mediaStream ` is
659
+ already set. It would be too late to subscribe for ` mediaStreamSet ` event. In
660
+ such case you can access ` callSession.mediaStream ` directly.
661
+
646
662
#### Where is the ` ringing ` event?
647
663
648
664
` ringing ` event is implicit.
0 commit comments