Cisco SPA 504G transfer / crash issue with Multi Tenant 3CX

Discussion in '3CX Phone System - General' started by bmwaterton, Jun 21, 2012.

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

    Joined:
    Jun 21, 2012
    Messages:
    4
    Likes Received:
    0
    Please help!

    We have a multi tenant 3cx server installed in a data centre. We have several Cisco SPA504G phones at various sites. All is well except for an issue with making calls after a transfer has taken place.

    The Cisco phones crash with the message "Answering" on the display when an extension, which has had a call transferred to it and the transferred call has finished, tries to make a call out. Like this:

    1. Phone 101 receives a call.
    2. Phone 101 presses "xfer" then dials 102
    3. 102 picks up call and 101 presses "xfer" again to transfer the call
    4. Call is transferred successfully
    5. Once call is finished 102 puts the phone down.
    6. The next time you to try make a call from 102 the phone freezes with the message "answering" on the screen, you can wait 1 minute , 5 minutes or 5 hours, it still won't let you dial out… unless (see 7)
    7. If you do not dial out from 102 after the transferred call has finished but instead receive another inbound (which has not been transferred) you can continue to call out without any issue.

    NBs:
    We have tried latest and recommend firmware
    The issue can be repeated with 2 phones on the same LAN and on different LANS
    It can be repeated with PBX delivers audio ticked or un-ticked for each/both extensions
    It can be repeated with and without STUN
    Cisco to soft phone doesn't not show the issue.

    3CX and Cisco support are doing a great job of blaming each other. Any ideas would be greatly received.
     
  2. bmwaterton

    Joined:
    Jun 21, 2012
    Messages:
    4
    Likes Received:
    0
    Re: Cisco SPA 504G transfer / crash issue with Multi Tenant

    To explain it further it's like the transferred call holds 102 hostage somehow and stops it from making calls. Only a non transferred call into to 102 can release it and allow it to call out again (or a reboot).
     
  3. bmwaterton

    Joined:
    Jun 21, 2012
    Messages:
    4
    Likes Received:
    0
    Re: Cisco SPA 504G transfer / crash issue with Multi Tenant

    Further update - we have now tried it on a non multi-tenant v10 3cx - same problem. We have also tried it on different router equipment (previously we were using Draytek at all sites). Same problem.

    Has no one else had this issue?
     
  4. usernamewithheld

    Joined:
    Oct 30, 2015
    Messages:
    1
    Likes Received:
    0
    I also have this issue. I love that support has not commented on it. My Cisco SPA504G commonly goes to answering instead of calling and freeze causing me to have to restart it almost everyday.
     
  5. bardissi

    bardissi Member

    Joined:
    Jan 31, 2012
    Messages:
    318
    Likes Received:
    0
    We have several deployments with SPA on Multitenant (although we use a 3rd party servers side SBC) and never had these issues.
     
Thread Status:
Not open for further replies.