One touch conference call dialing

[Harr2969]

On many phones (BlackBerry, Apple) you can do one-touch dialing which can include a lengthy conference code. I don't seem to get that in aquamail, but I'm not sure if it's an aquamail parsing challenge, or perhaps an OS level challenge?

At any rate, it would be ideal if some of these worked.

BlackBerry standard (which means it's widely used in business circles)
324-343-3434 x34234#
324-343-3434x34234#

Non-platform specific
324-343-3434,,,343#
324-343-3434 ,,343#
324-343-3434, 343#

Apple standard
324-343-3434;23443#
324-343-3434 ;23443#

It would be ideal if all of these were able to be processed, for the widest compatibility.

Right now, only the main numbers are touchable, the conference codes (which can be 7-13 digits) are not highlighted and must be memorized for manual entry for each conference call...

Thanks!

[Kostya Vasilyev]

Wonder why those aren't sent as proper links in the first place (with the "tel:" scheme)

Is there always a # at the end?

How many digits (min / max)?

[Harr2969]

Based on your question - I take it you are parsing the info for the dialer?

I've never seen tel: as a standard anywhere, which I should (would?) have as I have a focus on messaging.

Conference codes may vary. I've heard of 4-digit codes, but usually the big ones are 7-13 digits for uniqueness.

Almost all conference bridges use or respect a # sign as signifying the end of the code, however, it's not mandatory.  Some (european) use *XXXXX* instead of XXXX#

I would suggest picking up the "x" or "," or ";" as indicating that all following digits (plus (#/*) are tied to the number.

Malformed / unchecked / bad regex:
xxx-xxx-xxxx [,x;]{1-3} [\*]?x{7-13}[\*#]?

Maybe this makes sense?


ps.  Note a comma is a 3 second pause, to allow for the conference bridge connection. I'm unsure of the delay that's inserted when using a "x" or ";" -- maybe would want to use ,, (6 seconds) as a default to ensure the connection is established. 

[Kostya Vasilyev]

"I've never seen tel: as a standard anywhere, which I should (would?) have as I have a focus on messaging."

RFC 3966 from 2004:

http://www.rfc-base.org/txt/rfc-3966.txt

RFC 2806 from 2000 (superseded by 3966):

https://www.ietf.org/rfc/rfc2806.txt

Supported by iOS:

https://developer.apple.com/library/ios/featuredarticles/iPhoneURLScheme_Reference/PhoneLinks/PhoneLinks.html

And Android:

https://developer.android.com/guide/components/intents-common.html#Phone