![]() ![]() Select SignalWire from the options, then click Save. On the New Trunk configuration page, give it a friendly name, then choose the Profile you wish to associate your trunk with by dropping down Select Trunk Type and selecting Connect. In thinq.io > Outbound > Trunks > Add New Configuring SignalWire for thinQ Outbound Call Routing ![]() Leave the sip: prefix off of the URI, it should just be the full URL. Select “DNS A” for Type and enter the full SignalWire App URL from above. Be sure your naming system is descriptive so you recognize what it matches within SignalWire. ![]() ![]() You may want to create multiple SIP Domains on SignalWire for different applications, which would allow you to create additional routing profiles. In thinq.io > Inbound > Routing Profiles > Inbound ProfilesĬlick to Add a new profile, and in the pop-up, configure the name to be SignalWire-YourCompanyName or just SignalWire. Name your app thinQBYOC, set the App URL with BYOC in the custom URL slot, then Save.Ĭopy the full App URL before proceeding, as you’ll need it during your inbound routing profile setup inside thinQ.Ĭreate an Inbound Routing Profile at thinQ Leave default settings in place, then Save. We’ll move between both portals throughout these instructions. To start, open both your your SignalWire and thinQ io accounts in two browser tabs. Following these steps will also eliminate the need for hardcoding a SIP URI to route outbound calls initiated from your application to thinQ, meaning no changes will be needed inside your application. SignalWire can be easily enhanced with a minimum of development lift to augment your inbound and outbound voice with thinQ’s Bring Your Own Carrier (BYOC) solution.Īfter following these directions, inbound voice calls to your thinQ phone numbers (DIDs) will route to SignalWire, and outbound calls initiated from SignalWire will route through your thinQ outbound voice profile. ![]()
0 Comments
Leave a Reply. |