Cisco Phones Unable to Call Out Post Upgrade

Discussion in '3CX Phone System - General' started by CaspMR, Mar 2, 2018.

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

    Joined:
    Oct 9, 2017
    Messages:
    3
    Likes Received:
    0
    Hi,

    Has anyone run into an issue with the Cisco SPA303, SPA504G, and SPA525s where they show as registered to the system and can accept calls but get the "Temporarily Unavailable" error when dialing out? We recently updated one of our servers to 15.5.6354.2 to better support our new Yealink T42S phones but started encountering this issue with the Ciscos.

    The end goal is to replace all the Ciscos but our in-office and remote users who still have a Cisco are finding this frustrating.

    Thanks
     
  2. eddv123

    eddv123 Well-Known Member

    Joined:
    Aug 15, 2017
    Messages:
    1,218
    Likes Received:
    174
    Firstly i would always use a supported phone model with 3CX (Yealink are my preference). And I would never run Cisco's remotely except perhaps maybe across a VPN as they were never designed for this purpose with 3CX.

    I have however worked with Cisco's in the past and find they are very sensitive to firmware (see below guide for version). Also that they need to be setup either via DHCP option 66 provisioning or manual entry of the provisioning link in the phone:

    https://www.3cx.com/sip-phones/cisco-spa/

    https://www.3cx.com/sip-phones/cisco-spa501g/
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,754
    Likes Received:
    286
    Is this an issue with sets that are on the same LAN (as the server), remote (SBC, STUN?), or both? I assume that sets are showing as registered since they can receive calls. Is there a 3CX Activity Log when a call is placed? if so, that might provide a clue as to what is happening.
     
Thread Status:
Not open for further replies.