Cisco SPA303 Won’t Ring For More Than 60 Seconds

Home » Asterisk Users » Cisco SPA303 Won’t Ring For More Than 60 Seconds
Asterisk Users 6 Comments

Hi all,

I’ve got a user with a couple of Cisco SPA303’s. When I dial their phones with a dial string like:


The phone rings, as expected.

However after exactly 60 seconds, I get:

[Aug 21 02:09:56] — Got SIP response 480 “Temporarily not available”
back from a.b.c.d:5062
[Aug 21 02:09:56] — SIP/phone-a-00006a9d is circuit-busy
[Aug 21 02:09:56] == Everyone is busy/congested at this time (7:0/6/1)

Clearly I’m asking the phone to ring for 5 minutes, but it’s giving up after 1. Does anyone know how to fix this?



6 thoughts on - Cisco SPA303 Won’t Ring For More Than 60 Seconds

  • Asterisk is not timing out. The phone is rejecting the call after 60 seconds. This is a phone configuration issue.

    —–Original Message—

  • Does anyone know what knob I need to turn to adjust how long the phone will ring before giving up?


  • At first I also thought this might be a phone setting. But then I found the same 60s to be true for a variety of SIP phones (Snom, Cisco, …), despite the 300s timeout value in the Dial cmd. So it is likely to be Asterisk. The Asterisk Admin Guide says that the default value is 136
    years, so there must be something that sets this timeout value.


  • I just checked the Snom phone on my desk and it turned out that the phone has an internal timing value of 120s for invitations (ringing_time). This value cannot be set using the web interface for my phone. I also checked a Cisco phone, but I did not find a similar setting. It doesn’t matter, but the the Snom phone returned .

    Now, I do think it is a phone setting and it might be hard coded.


  • On 8/21/2013 1:35 PM, Mike Diehl said:
    I know it’s not what you’re asking for, but

    call.offeringTimeOut on Polycoms has a default of 60 seconds. My google-fu however fails me this afternoon.

    Page A – 64: