This repository was archived by the owner on Jan 15, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 86
chore: Updating tests and adding documentation for error handling in … #1220
Merged
carlosscastro
merged 4 commits into
microsoft:feature/telephony
from
vanshu86:vasinha/calltransfer
Jul 19, 2021
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,19 +13,18 @@ Like any other channel, Telephony channel allows you to transfer call to an agen | |
| * PhoneNumber | ||
|
|
||
| #### Usage | ||
| * Phone Number is not empty and in the E.164 format. | ||
| * Phone Number should not be empty and should be in the E.164 format. | ||
| * The call transfer action is only valid when called in a conversation on the Telephony channel. The action can be considered a No-op for all other channels. | ||
|
|
||
| #### Dialog Flow | ||
| * Once the call transfer is completed, the bot is removed from the current conversation and control is transferred to the extenal phone nunber. | ||
| * [Open] Do we get back a handoff status on success? Should we wait for the status in our package? | ||
| * Once the call transfer is completed, the bot is removed from the current conversation and control is transferred to the external phone number. | ||
| * The bot will not get any handoff status on success. | ||
| * Any actions specified after call transfer will not be executed. Treat it like a call end. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will the subsequent actions be executed after a failed call transfer?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, will will add that in failure flow too. |
||
|
|
||
| #### Failures | ||
| * [Open] How should the package fail when Phone Number is Empty - should we throw an exception? How can we make sure that the exception message is localize properly? | ||
| * [Open] When the phone number is not in a valid E.164 format, how does the call transfer fail? | ||
| * [Open] Do we get back a handoff status on failure? | ||
|
|
||
| * For all failure cases where the connection is not established, either due to Phone Number being empty, invalid, bogus or just connection failure, an asynchronous "handoff.status" event is sent with value "failed". More details [here](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-design-pattern-handoff-human?view=azure-bot-service-4.0). | ||
| * This can be handled either in code as per [this](https://github.com/microsoft/botframework-telephony/blob/main/TransferCallOut.md) or in Composer by adding a trigger -> Activities -> Event Received (Event Activity), with this condition, turn.activity.name == "handoff.status", following which @turn.activity.value can be used for handling the failure case. | ||
| * In the failure case, subsequent actions will be executed. | ||
|
|
||
| ## **Call Recording** | ||
| The call recording commands enable bots to request that calls are recorded by the phone provider. The bot can control when to start, stop, pause and resume the recording with these commands. For more information about the call recording capabilities, see [Telephony Advanced Features - Call Recording](https://github.com/microsoft/botframework-telephony/blob/main/CallRecording.md). | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15 changes: 15 additions & 0 deletions
15
...Tests/Integration/CallTransferTests/CallTransfer_IgnoredInNonTelephonyChannel.test.dialog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| { | ||
| "$schema": "../../../tests.schema", | ||
| "$kind": "Microsoft.Test.Script", | ||
| "dialog": "CallTransfer_BaseScenario.test", | ||
| "script": [ | ||
| { | ||
| "$kind": "Microsoft.Test.UserSays", | ||
| "text": "Hello I'm Calculon" | ||
| }, | ||
| { | ||
| "$kind": "Microsoft.Test.AssertReply", | ||
| "text": "Transfer Initiated!" | ||
| } | ||
| ] | ||
| } |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current behavior is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes added in failure flow