Appendix A – Supported SMS Characters
Unicode | IAS | Unicode | IAS | Unicode | IAS | Unicode | IAS | Unicode | IAS | Unicode | IAS |
64 | 0 | 928 | 22 | 44 | 44 | 66 | 66 | 88 | 88 | 110 | 110 |
163 | 1 | 968 | 23 | 45 | 45 | 67 | 67 | 89 | 89 | 111 | 111 |
36 | 2 | 931 | 24 | 46 | 46 | 68 | 68 | 90 | 90 | 112 | 112 |
165 | 3 | 952 | 25 | 47 | 47 | 69 | 69 | 196 | 91 | 113 | 113 |
232 | 4 | 926 | 26 | 48 | 48 | 70 | 70 | 214 | 92 | 114 | 114 |
233 | 5 | SP | 27 | 49 | 49 | 71 | 71 | 209 | 93 | 115 | 115 |
249 | 6 | 198 | 28 | 50 | 50 | 72 | 72 | 220 | 94 | 116 | 116 |
236 | 7 | 230 | 29 | 51 | 51 | 73 | 73 | 167 | 95 | 117 | 117 |
242 | 8 | 223 | 30 | 52 | 52 | 74 | 74 | 191 | 96 | 118 | 118 |
199 | 9 | 201 | 31 | 53 | 53 | 75 | 75 | 97 | 97 | 119 | 119 |
10 | 10 | SP | 32 | 54 | 54 | 76 | 76 | 98 | 98 | 120 | 120 |
216 | 11 | 33 | 33 | 55 | 55 | 77 | 77 | 99 | 99 | 121 | 121 |
248 | 12 | 34 | 34 | 56 | 56 | 78 | 78 | 100 | 100 | 122 | 122 |
13 | 13 | 35 | 35 | 57 | 57 | 79 | 79 | 101 | 101 | 228 | 123 |
197 | 14 | 164 | 36 | 58 | 58 | 80 | 80 | 102 | 102 | 246 | 124 |
229 | 15 | 37 | 37 | 59 | 59 | 81 | 81 | 103 | 103 | 241 | 125 |
916 | 16 | 38 | 38 | 60 | 60 | 82 | 82 | 104 | 104 | 252 | 126 |
95 | 17 | 39 | 39 | 61 | 61 | 83 | 83 | 105 | 105 | 224 | 127 |
934 | 18 | 40 | 40 | 62 | 62 | 84 | 84 | 106 | 106 | ||
915 | 19 | 41 | 41 | 63 | 63 | 85 | 85 | 107 | 107 | ||
923 | 20 | 42 | 42 | 161 | 64 | 86 | 86 | 108 | 108 | ||
937 | 21 | 43 | 43 | 65 | 65 | 87 | 87 | 109 | 109 |
Appendix B – Tokens: An Advanced Feature
The standard usage and pricing plan for use of DOTS Telephone Verification is based on Transactions as the aggregated and charged for unit. Transactions in this context are defined as: any DOTS Telephone Verification procedure call made to the Service Objects web service, regardless of returned information or use of returned information.
There is an advanced feature of DOTS Telephone Verification for more sophisticated users called Tokens. A Token is a unit of cost where different DOTS Telephone Verification Procedure calls are weighted differently resulting in a variable cost per different transaction type. Transactions pricing is therefore variable, reflecting differing Token costs for less complex Transactions, and therefore the plan is based on
purchasing an amount of Tokens per month, not Transactions. If a user desires closer accounting and measurement of specific Procedures used by their application and a payment plan that reflects this through variable pricing then the use of Tokens may provide added value. The Token cost structure is listed in the following table.
Per Procedure Token Costs | Tokens |
---|---|
PlaceCall | 70 |
SendSMS | 85 |
GetExchangeInfo | 15 |
GetPhoneInfo | 65 |
GetTransactionalDetail | 0 |
If you decide that use of the Token based structure and pricing plan may be an advantage for you please contact Service Objects Sales
Team for assistance: sales@serviceobjects.com or 1-805-963-1700