2

My iPhone (running iOS 8) and my MacBook (running OS 10.10.3) are in the same WiFi network, and I can answer incoming calls from my MacBook.

Initiating calls from the Contacts application on the MacBook also works - I click the phone symbol next to the phone number and it opens the call:

enter image description here

This works perfectly fine unless the phone number contains more than one hash character (#). When using conference systems, the hash sign is used to terminate input, e.g. after entering the conference or leader code.

Example:

  • This number works fine: +112345678,,,1234#
  • This number does not work: +112345678,,,1234##

The only difference is the second hash sign at the end. I've simplified that here, in real life, there are a couple more digits between the two hash signs, but the above also reproduces the error for me.

What happens is that as soon as there is a second hash sign in the number, clicking the phone symbol next to the number will not have any result.

The strange thing is that I can open FaceTime, click on audio, then start typing the name of the contact in question and call from there, including the second hash sign, and it will work fine.

One more note: The same can be reproduced by trying to open the number from the terminal:

open tel://+112345678,,,1234#

works, while the following will not work - it will open FaceTime, but will not dial...

open tel://+112345678,,,1234##

Is this a known issue with FaceTime/OS X - or am I missing something?

-1

Confirming that this bug is still present in El Capitan. Frustrating. Curious if anyone has come up with a workaround using AppleScript, Keyboard Maestro, or other tool.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .