Azure Communication Phone Numbers Client Library for JavaScript – Version 1.3.0

The Phone Number Library phone number library provides functionality for managing phone numbers.

Purchased phone numbers can have many functionalities, depending on the country, number type, and assignment type. Examples of functionalities include inbound and outbound SMS usage, PSTN inbound and outbound usage. Phone numbers can also be assigned to a bot via a webhook URL.

Telephone numbers come in two types; Geographic and Toll-Free. Geographic telephone numbers are phone numbers associated with a location, whose area codes are associated with the area code of a geographic location. Toll-Free telephone numbers are not associated with a location. For example, in the United States, toll-free numbers may have area codes such as 800 or 888.

Find and acquire numbers

 

Phone numbers can be searched through how to create an ai chatbot for your business the Create Search API by providing a phone number type (geographic or toll-free), assignment type (person or app), calling and sms capabilities, area code, and number of phone numbers. The provided number of phone numbers will be reserved for 15 minutes. This phone number search can be cancelled or purchased. If the search is cancelled, the phone numbers will be made available to other users. If the search is purchased, the phone numbers are purchased for the Azure resource.

Phone numbers can have a combination of functionalities. They can be set to support incoming or outgoing calls, or neither if you won’t be using the phone number for calling. The same applies to SMS functionalities.

SIP Routing Client

 

The Direct Routing feature allows you changsha mobile phone number list to connect customer-provided telephony infrastructure to Azure communication resources. To successfully configure the routing settings, the customer must provide SIP trunk configuration and SIP routing rules for calls. The SIP Routing Client provides the interface required to configure these settings.

When a call is made, the system attempts to match the destination number with regex number patterns from defined routes. The first route to match the number will be selected. The regex matching order is the same as the order of the routes in the configuration, so the order of the routes matters. Once a route is matched, the call is routed to the first trunk in the route’s trunk list. If the trunk is not available, the next trunk in the list is selected.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top