Azure Communication Phone Numbers Client Library for JavaScript – version 1.3.0

The Phone Number Library provides phone number library functionality for phone number administration.

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

All geographic phone numbers in the same country are groupe into a phone plan group with a geographic phone number type. All Toll-Free phone numbers in the same country are group into a phone plan group.

Search and acquisition of numbers

Phone numbers can be search through the another example is these two Create Search API by providing a phone number type , assignment type , calling and SMS capabilities, area code, and a quantity of phone numbers. The provide quantity of phone numbers will be reserved for 15 minutes. This phone number search can be cancele or purchase. If the search is cancel, the phone numbers will be available for other people to use. If the search is purchase. The phone numbers are acquire for the Azure resource.

Phone numbers can have a combination of features. They can be configure to support incoming and/or outgoing calls, or whether you will not use the phone number to call. The same applies to sms features.

SIP Routing Client

Direct Routing is a feature that connects b2c fax customer-provide telephony infrastructure to Azure communications resources. To properly configure the routing configuration, the customer must provide the SIP trunk configuration and SIP routing rules for calls. The SIP Routing client provides the interface to set this configuration.

When a call is made, the system attempts to match the destination number with the regex number patterns of the defined routes. The first route to match the number will be select. The order of regular matches is the same as the order of the routes in the configuration. Therefore the order of the routes matters. Once a route is match, the call is routed to the first trunk in the list of trunks in the route. If the trunk is not available, the next trunk in the list is select.

Leave a Comment

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

Scroll to Top