The Phone Number Library provides phone number library functionality for managing phone numbers.
Purchased phone numbers can have many features, depending on the country, number type, and assignment type. Examples include inbound and outbound SMS and inbound and outbound PSTN. 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 location-based telephone numbers, whose area codes are associated with a geographic location. Toll-free telephone numbers are not location-base. 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 searche the best creatives for performance marketing through the Search Creation API by providing a phone number type. Assignment type , calling and SMS capabilities, area code. And number of phone numbers. The provide number of phone numbers will be reserve for 15 minutes. This phone number search can be cancel or purchase. If the search is cancel, the phone numbers will be available to other users. If the search is purchase, the phone numbers are acquire 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.
It’s important to consider the type of assignment your phone number has. Some features are restrict to a specific assignment type.
SIP Routing Client
The Direct Routing feature allows our best selling database you to connect customer-provide 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.
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 select. The regular expression matching order is the same as the route order in the configuration. So the route order matters. Once a route is match, the call is routed to the first trunk in the route’s trunk list. If the trunk is unavailable, the next trunk in the list is select.
