Handle automated-attendant DTMF phone extensions (iCloud pause/wait and RFC3966 phone extensions) #67

Open
bertrand-lupart opened this Issue Sep 10, 2012 · 6 comments

Comments

Projects
None yet
3 participants

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.

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.

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,

@eofster eofster modified the milestones: 1.1.5, 1.1 Sep 14, 2015

@eofster eofster added the enhancement label Sep 14, 2015

Owner

eofster commented Mar 28, 2016

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)

Do you mean that when you try to send DTMF manually, it is not received?

@eofster eofster removed this from the 1.1.5 milestone Mar 29, 2016

Do you mean that when you try to send DTMF manually, it is not received?

I'm not sure. I guess at this time i was expecting some graphical keyboard to be available, and didn't noticed it was possible to enter the digit with the keyboard.

I guess this was a pointless side remark.

Owner

eofster commented Apr 22, 2016

Yeah, the current way of sending DTMF is impossible to find. The future UI updates should make this feature more obvious. Do I understand correctly, that the original problem was that this feature was nowhere to be seen, and not that you tried to send DTMF, but it didn’t work?

Hello,

The original problem was to handle automated-attendant :
https://en.wikipedia.org/wiki/Automated_attendant

iOS allows to register numbers with soft pause and hard pause, using comma or semicolon :
https://support.apple.com/en-us/HT202176

+1-555-438-3732,1234

  • compose +1-555-438-3732
  • wait for the callee to answer
  • automatically send '1234' DTMF

+1-555-438-3732;1234

  • compose +1-555-438-3732
  • wait for the callee to answer
  • "dial 1234" button appears on iPhone screen for the caller to send '1234' DTMF

You end up with this kind of numbers in iCloud contacts, and Telephone don't know how to handle them : it compose all the numbers in a row without pausing, and the call fails.

Apple way doesn't seem to be the standard way described in RFC3966 :
<a href="tel:+1-555-438-3732;ext=1234">1-555-IETF-RFC</a>
This would allow to compose +1-555-438-3732 by clicking on a link, wait for the call to answer and automatically send 1234 DTMF.

I can provide a french automated-attendant number for testing purpose.

Thank you,

@bertrand-lupart bertrand-lupart changed the title from Allow RFC3966 phone extensions to Handle automated-attendant DTMF phone extensions (iCloud pause/wait and RFC3966 phone extensions) Aug 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment