![]() |
Ensuring e.164 compliance in Telephone Number fields
The e.164 standards for telephone numbers dictate s strict length resriction
of something less that 16 characters. The default contact form in Outlook allows for a telephone number that is not e.164 compliant. This impacts applications that interact with Outlook such as Office Communicator and how phone number normalization works. If I were able to modify the default form to ensure compliancy then the normalization issues dissappear. -- Henry Goodrow |
Ensuring e.164 compliance in Telephone Number fields
You'd have to hack into the Outlook code to do that. All of that sort of
thing is hard coded into Outlook. If you can provide intermediate code between Outlook and whatever telephony app is being used you can use your own code to make the numbers compliant, otherwise you'd need to wait for MS to change Outlook to make it compliant, if MS ever does that. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007. Reminder Manager, Extended Reminders, Attachment Options. http://www.slovaktech.com/products.htm "Henry Goodrow" wrote in message ... The e.164 standards for telephone numbers dictate s strict length resriction of something less that 16 characters. The default contact form in Outlook allows for a telephone number that is not e.164 compliant. This impacts applications that interact with Outlook such as Office Communicator and how phone number normalization works. If I were able to modify the default form to ensure compliancy then the normalization issues dissappear. -- Henry Goodrow |
All times are GMT +1. The time now is 11:18 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2006 OutlookBanter.com