On Twilio I configured a Sip Domain and I created a flow in Twilio Studio. I want to connect them so when I call the number registered in the SIP Domain I want the call connected to the flow in Twilio Studio.
How can I do that?
Twilio staff here. You should be able to do this using your Studio Flow's webhook URL.
To find the webhook for your flow, click on the flow's trigger:
Then copy and paste the webhook URL into your SIP domain's voice configuration:
Click "Save" at the bottom of the SIP domain configuration page and incoming calls will trigger your Studio Flow.
Related
I have setup the following:
Azure B2C
Standard user flow
MFA turned on
Twilio account
a US number
a messaging service with web hook
Rest API
Accept POST call from Twilio web hook
I want Azure B2C MFA to send SMS to Twilio and Twilio then trigger a call with the message content to my Rest API.
I have tried this setup and it worked the first two times. However, all subsequent attempts were not successful. I cannot see the received message count in Twilio increase, after MFA SMS is sent from Azure B2C.
Is there any way to find out why this stopped working and is there any settings to configuration that I may have missed configuring?
Any help would be much appreciated.
I am creating an MS Teams messaging bot through Developer Portal and just relying on the bot messaging bot endpoint of my bot to send/receive messages. I also need OAuth flow for users to login to my website and map that login to the MS Teams user
Documentation:
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/authentication/auth-flow-bot
I have some questions:
It looks like the 'start OAuth page' and 'callback OAuth page' both utilize MS Teams libraries/packages to call initialize and microsoftTeams.authentication.notifySuccess("{{verificationCode}}"); Is there any rest API endpoint we can call to replicate this behavior or execute these flows? Or is there a java equivalent if we don't want to do all this in javascript?
Can we host the 'start OAuth page' and 'callback OAuth page' in our servers (i.e. not on Azure or Microsoft resources but on our website domain like mywebsite.com/start_oauth and mywebsite.com/callback_oauth)? And if so, is there any documentation for this?
If yes to #2, is there any additional work to be done for hosting these pages in our servers?
Quick update on answer. It looks like I can host these pages anywhere. The MS Teams OAuth flow opens a pop-up for sign-in in MS Teams and as long as that pop-up can redirect to these pages, then these libraries can be called/used regardless of where it's hosted
We're using Twilio Connect to allow our users to connect their Twilio accounts to ours. We provision a number for their subaccount, and set the messaging webhook to POST to our server.
We try to validate the request using the Twilio node library validateRequest method but validation always fails. I think that's because we're passing our client secret to validate a request that's coming from our user's Twilio account.
How should validate Twilio webhook calls that come from accounts we're authorized to use (but are not our own accounts)?
This might be a permissions thing! There are two permissions available for Twilio Connect Apps -- Read all account data & Charge account for usage! You would only be able to have full autonomy over a users account & subaccounts if you use the "Read all account data" permission when setting up the Connect App.
Is there a way for the Microsoft bot framework to get access to the web API methods in the Slack API (channel read for example)?
If your bot needs access to Slack specific APIs, it should call the Slack API directly using the bot credentials (Client ID and Client Secret) that Slack provided when you created the app. Going through BotFramework would add additional hops making your bot less performant.
I noticed that there is a Client noun in the Twilio documentation. Is Client a Sip product? Would I use Client to connect to a Sip phone?
The <Dial><Client> verb is for dialing from the Twilio Computer Telephony Integrated (CTI) VoIP solution, or what is called Twilio Client. Twilio Client can be integrated into a browser, an iOS application and/or an Android application. Twilio Client is different from Twilio Sip. Twilio Client is used for calling to or from in-app soft phones whereas Twilio Sip is for calling to or from a PBX (physical or hosted) and/or a Sip enabled device. In Twilio, calling Sip endpoints is accomplished by using the <Dial><Sip> verb.
Sip and Client usage in Twilio is a little different. For example, to call a Twilio Client soft phone, you could write:
<Dial>
<Client>Agent1</Client>
</Dial>
On the other hand, to call a Twilio Sip endpoint, you could write:
<Dial>
<Sip>sip:agent1#example.com</Sip>
</Dial>
Twilio Client is useful for building solutions where you don't have a PBX or SIP hardware already in place. Twilio SIP can be used to add new functionality or extend an existing SIP setup.