Sinch Community

Here are the top reasons Sinch may reject your campaign, and what you should do to avoid them:   Insufficient opt-in: This means that you failed to convey how you get consent from the end user to send messages. Make sure you show the opt-in from the end-user's perspective. For example, if your opt-in happens online, you must specify where on the website the opt-in occurs. Brand name mismatch: This means the registered brand name or DBA doesn't match the name on the brand website or in the messages. You can use a shortened brand name in your messages, but it can't be so different that it's not clear who the sender is. If the brand names are different, make sure you explain why in the campaign description. Insufficient privacy policy: This means it's not clear in your privacy policy that you won't share or sell the end user's personal info to a third party for marketing purposes. If you don't have a privacy policy, then you need to create one. If Sinch rejects your 10DLC campaign, we will provide a rejection code with a description. In most cases, after addressing the reason for the rejection, you can resubmit your campaign to Sinch for review. Refer to the 10DLC Campaign Rejection Codes article for a detailed explanation of these rejection codes.  ... View more

Sinch Elastic SIP Trunking can easily integrate with your favorite IP-PBXs and SBCs, and we offer the following guides to show you how: 3CX FusionPBX Ribbon SBC Twilio BYOC Trunk VitalPBX Vodia PBX ... View more

There are two ways a Sinch Elastic SIP Trunking customer may authenticate themselves to the service. The first is IP authentication using Access Control Lists. With an ACL, a customer provides the IP or range of IP addresses that they will be sending traffic from to the provider. The second is the use of digest authentication challenges to SIP Requests. When digest authentication is in place, every SIP Invite sent to the Elastic SIP Trunk will be challenged with a SIP `407 Authentication Required` response. The client then must send the Invite again with the proper credentials.   If both ACLs and Digest Authentication are configured on your SIP Trunk, then both will be enforced.  Before placing a call, the client will need its IP Address added to the Access Control List and its username and password configured.  If either of these are not done the call will be rejected.   Before you begin setting up your Sinch Elastic SIP trunk for Digest Authentication make sure you have done the following:   Sign up for a free account at https://www.sinch.com/ and request access for Elastic SIP Trunking. Need help? Click here for instructions. If you have not already done so, configure and create your Elastic SIP trunk.  Instructions on how to do this can be found here. Ensure you note the FQDN that was created on your SIP Trunk. You will need this while setting up your IP-PBX or SIP Application.   Configuring Digest Authentication   Log into the Sinch Customer Dashboard and navigate to Credential Lists underneath the Elastic SIP Trunking sub menu option:     Click CREATE NEW CREDENTIAL LIST.   The Create new Credential List dialog is displayed:     This allows you to create the list as well as the first entry.  Credential Lists may contain many Username/Password credentials.  When the list is assigned to a SIP Trunk, any credential found in the list may be used to authenticate calls.   Enter a friendly name for the Credential List and create your first credential by supplying a Username and Password. Click CREATE.   You may now select the Credential List name to be brought to its configuration page.  Here you can add new credentials, change the name of the Credential List, change the password for a credential, or remove a credential entirely.     Finally, you must assign the credential list to the SIP Trunk. To do this, navigate to your SIP Trunk’s configuration page and add it underneath the Outbound Call Settings.  Save your changes and the configuration for Digest Authentication is complete. ... View more

Detailed analytics for your call traffic can be found in the Analytics section beneath the Elastic SIP Trunking category in the navigation menu.  Here you can use various search criteria to get a good view of your traffic.     Notable Search Options Call Status – The final disposition of the call. This can have any of the following statuses: Completed – The call completed successfully without any problem. The call was connected through with duration. Busy – The call was routed to the end party, but we received back a SIP 486 Busy Here response. Failed – The call was unable to be completed. This could be due to system error, network congestion, or simply because the number was misdialled. Cancel – The call was routed to the user but was rejected with something other than a User Busy. No Answer – The caller hung up before the call was answered. Origin Country Destination Country Trunk Call Type Emergency Call Status Data and Time ... View more

To locate your Application Key and Secret, please log in to the Sinch Customer Dashboard. Once logged in, you can access the Verification Apps page directly or navigate to the Apps section within the Verification drop-down in the panel located on the left side of the screen:     If you have only one App, as is the case for new accounts, you'll be directed to the App details page. The Application Key and Secret can be found in the Your summary section on the right-hand side of the page:       In the Settings section all values may be left blank, as the defaults work for the vast majority of situations. These settings only need to be modified in advanced scenarios.   If you have multiple Apps you'll encounter a list of them. However, the Keys and Secrets can be accessed directly from this level. Alternatively, you can retrieve them from the details view of the respective Apps:         ... View more