Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Directed to Vmail

Discussion in 'iOS' started by Mick101, Oct 31, 2016.

Thread Status:
Not open for further replies.
  1. Mick101

    Joined:
    Oct 31, 2016
    Messages:
    6
    Likes Received:
    0
    Device Info
    -------------------------------------------------------
    Phone Model: iPhone
    Generation: 6
    Firmware Version: [ios 10.1]
    Jailbreak: [NO]
    Cydia Installed: [NO]

    Issue Info
    -------------------------------------------------------
    Handset: [Phone]
    Contacts: [Local]]
    Connection: [WiFi]
    Server: [Internal]

    Observing a strange behavior on the iPhone App with V15.

    When making an internal call from an ATA phone (ext 2001) to a 3CX iphone app (ext 1978), I answer the call on the on the iPhone but seconds later, the iPhone app opens a second line and calls the voicemail.

    Have tried with a few extensions so far but the same behavior. Has anyone seen this before and how do I solve this?

    FYI, this is only my 3rd day with trying 3CX.

    Thank you,
     
  2. Mick101

    Joined:
    Oct 31, 2016
    Messages:
    6
    Likes Received:
    0
    New Update:

    I managed to get a test Android phone and installed the 3CX client on it.
    Calls received on the Android client doesn't have that behavior.

    I am assuming that this a unique issue on the iPhone. I will uninstall and reinstall.

    Update: No change after uninstalling and reinstalling. Definitely something wrong with the iPhone app.
    Tried installing on an iPad Mini with iOS 9. Same behavior but I also don't get a Presence Status. it flashes "Forbidden"
    Log shows:
    11/01/2016 9:27:33 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 127.0.0.1:5080 tid=PjiMb...
    Although I can make and receive calls.

    iOS Client seems to be very buggy.
     
Thread Status:
Not open for further replies.