Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Allow RFC3966 phone extensions #67

Open
bertrand-lupart opened this Issue · 2 comments

2 participants

@bertrand-lupart

RFC3966 describes phone extensions to be used with tel: URI schemes that don't seem to work (1.0.4 tested)

<a href="tel:+1-555-438-3732;ext=1234">1-555-IETF-RFC</a>

iOS unofficial address book way to handle such extensions (+1-555-438-3732,1234) doesn't seem work either.

@fulldecent

Hello, there have been several releases of Telephone since this issue was created. Could you please download and run the latest version to confirm this issue still exists.

Sorry for the template response, just trying to clean up and close old issues here.

@bertrand-lupart

Hello,

Below are the results from my tests using 1.1.4 which seems the latest stable version.

RFC3966 (eg +1-555-438-3732;ext=1234) phone extensions won't work:

  • if typed into the dial field, +1-555-438-3732 is called but 1234 is never sent to the remote phone system (and there's no way to manually enter it)
  • if a HTML link is clicked Call, a phone call to +1-555-438-3732 is placed, but 1234 is never sent to the remote phone system

Obsolete RFC2806 (eg +1-555-438-3732w1234) almost work:

  • if typed into the dial field, +1-555-438-3732 is called and then 1234 is sent to the remote phone system
  • if a HTML link is clicked Call, Telephone.app get the focus but no phone call is placed.

Note : +1-555-438-3732;ext=1234 is a placeholder phone number found in RFC3966 which won't work. I can provide a (french) demo number if you like.

Thank you,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.