This bug was fixed in the package telepathy-qt5 - 0.9.3-0ubuntu15
---------------
telepathy-qt5 (0.9.3-0ubuntu15) vivid; urgency=medium
[ Tiago Salem Herrmann ]
* debian/patches/11-fix-requested.patch: Don't set "Requested" based on
initiatorHandle and selfHandle (LP: #1423193)
-- Timo Jyrinki <timo-jyri...@ubuntu.com> Thu, 19 Feb 2015 15:08:55 +0200
** Changed in: telepathy-qt5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1423193
Title:
Dialer doesn't know call is connected over bluetooth
Status in Dialer app for Ubuntu Touch:
New
Status in telepathy-qt5 package in Ubuntu:
Fix Released
Status in telepathy-qt5 package in Ubuntu RTM:
New
Bug description:
Attempt 1:
Phone was locked
Initiated a call to a conference line using the phone book on the car as
provided from the phone
The call connected and the dialer was shown but it said Emergency call in
the header and the UI was ready to make a call, not showing a cal in progress
Attempt 2:
Unlocked the phone and opened the dialer
Initiated call with the car UI
the call connected but the dialer stayed in the state to make a call
Attempt 3:
Same as 2 but the dialer showed the call was connected
Entered the conference number and #, the tones were echoed and numbers shown
in the phone UI
The conference service did not receive the numbers
Mako running rtm 195
I have been using this scenario for 6 months and two different cars
without ever having a problem. Last time was probably a month ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1423193/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
