Z10 Answering Issue

joecool
2014-03-09
2014-05-07
  • joecool
    joecool
    2014-03-09

    Hey I'd post a ticket but there's no option to start a new one.

    I'm pretty new to BB10, this app is already the best sip client I've used on any mobile phone. Sound quality and reliability is really good.

    The problem I'm having is related to answering, phone rings with a busy signal type noise (might be normal). But then I have to manually turn screen on, touch answer call, switch to taki running in the background, and hit answer in the app. This is a lot of steps to answer call and I usually don't make it before it hits voicemail.

    I am on OS 10.2.1.537. I haven't seen many recent tickets or discussions so it is maybe possible the app hasn't been updated for 10.2 and this is a result of dialer change. Please let me know if the above is by design or if something is messed up in OS update.

     
    • There is a regression in BB10 10.2.1 notification API which prevents
      Taki from processing call Answer / Reject choice when Taki is running in
      the background and receives inbound call. In this case notification
      dialog pops up, but user choice is not properly delivered to Taki process.

      I have ticket open in BlackBerry Bug tracker:
      https://www.blackberry.com/jira/browse/BBTEN-2166

      After it'll be fixed you won't need to focus Taki to answer/reject the call.

      As soon as I get more info from BB I'll post it at:
      http://taki.sourceforge.net

      Regards,
      Dmytro

      On 03/09/2014 12:54 AM, joecool wrote:

      Hey I'd post a ticket but there's no option to start a new one.

      I'm pretty new to BB10, this app is already the best sip client I've
      used on any mobile phone. Sound quality and reliability is really good.

      The problem I'm having is related to answering, phone rings with a busy
      signal type noise (might be normal). But then I have to manually turn
      screen on, touch answer call, switch to taki running in the background,
      and hit answer in the app. This is a /lot/ of steps to answer call and I
      usually don't make it before it hits voicemail.

      I am on OS 10.2.1.537. I haven't seen many recent tickets or discussions
      so it is maybe possible the app hasn't been updated for 10.2 and this is
      a result of dialer change. Please let me know if the above is by design
      or if something is messed up in OS update.


      Z10 Answering Issue
      https://sourceforge.net/p/taki/discussion/general/thread/76b68585/?limit=25#91a7


      Sent from sourceforge.net because arkadiam@users.sourceforge.net is
      subscribed to https://sourceforge.net/p/taki/discussion/general/

      To unsubscribe from further messages, a project admin can change
      settings at https://sourceforge.net/p/taki/admin/discussion/forums. Or,
      if this is a mailing list, you can unsubscribe from the mailing list.

       
      • Iuri
        Iuri
        2014-05-06

        Hey Everybody,

        I'm having almost the same issue here at work, the only difference is that Taki is not working even when the App is focused. Do you have any idea how to fix it?

         
        • On 05/06/2014 03:34 PM, Iuri wrote:

          Hey Everybody,

          I'm having almost the same issue here at work, the only difference is
          that Taki is not working even when the App is focused. Do you have any
          idea how to fix it?

          Please check this article first:
          http://taki.sourceforge.net/blackberry-sip/bb-os-10-2-1-notification-api-regression/

          It's about answering issue when the app is not in focus.

          If that's not the case and the app is in focus please check application
          support window for errors. It can be opened if you pull from the top of
          the screen and select "Support". You can email me this log and I'll be
          able to advise.

          Regards,
          Dmytro

           
  • joecool
    joecool
    2014-03-10

    Thanks for getting back about this. I figured it was likely some sort of regression but hadn't ever run a prior OS version.