Phone number data type
The phone number data type can be a useful tool in helping flow authors easily obtain property details about a phone number. In Architect, a phone number includes one of three schemes:
Scheme | Description |
---|---|
tel | This scheme is a tel URI in a format as specified in RFC 3966 and followed by a phone number optionally formatted according to E.164 formatting specifications. E.164 is the international standard for how global phone numbers are allocated and used. For more information, see About the tel scheme. |
sip | This scheme is followed by a SIP URI formatted address of the user’s SIP phone number. The standard format for a SIP URI is: USER@ADDRESS. Note: You can also specify “sips” to allow resources to specify that they should be reached securely. Architect does not differentiate between sip or sips when classifying the scheme. |
For example, let’s examine the following phone number string:
tel: +13175551286
In this string:
- The + indicates that this is a global phone number.
- Immediately following the + in a global phone number is the “international dialing code” (sometimes called the “country code”), which can be 1 to 3 digits. In our example, it is 1.
- The remaining digits are known as the “subscriber number”.
Note: Most international dialing codes are associated with one or more countries. For example, dialing code 1 is used for Canada, the United States, and 23 other countries and territories near North America (but not Mexico), dialing code 44 reaches the United Kingdom, 49 reaches Germany, and 31 reaches the Netherlands. Architect allows you to refer to the appropriate codes using the two-letter country abbreviations such as System.Regions.US.dialingCode (the United States dialing code of 1) or System.Regions.CA.dialingCode (Canada also shares the value 1) or System.Regions.NL.dialingCode (the Netherlands dialing code of “31”).
For more information, click to expand a section below.
[NEXT] Was this article helpful?
Get user feedback about articles.