I don't get the answers to this question - I think the're wrong. The correct link would look like this:
<a href="tel:+441234567,88">+44-1234-567 ext. 88</a>
Seems the proper way to do it is use a comma:
<a href="tel:441234567,88">+44-1234-567 ext.88</a>
Just tested with iPhone and Android OS 2.1. Using ;ext=88
converts the ext bit into a number that is dialed with the extension (so it dials something like 35888 instead of 88).
Standards at thenewcode from 3 months ago suggest using a microdata pause.
<a href="tel:+13235798328p22">
Related: Different standards persist across different external platforms and may change the processing of URIs. Click to call features on Google Developers docs do not specify
Example: Office's Skype uses x to represent extension within skype.
According to the documentation, you can add what you want like so tel:12345678;ext=123
See RFC 3966
I feel like this is kind of a cop-out answer, but if this is not implemented consistently across devices yet, probably best to just not include the extension and let people dial it by hand:
<a href="tel:+441234567">+44-1234-567 ext. 88</a>
or
<a href="tel:+441234567">+44-1234-567</a> ext. 88
Better to make the user do more work than to send 1/2 your users to the wrong extension.
For those still wondering about this problem: I've found it best to use this format:
<a href="tel:+13235798328;22">