Author Topic: Is it possible to extend timeout before YATE sends CANCEL?  (Read 5115 times)

Alexey Kononykhin

  • Newbie
  • *
  • Posts: 2
    • View Profile

Sometime our provider doesn't respond in a timely manner. For example:
1) Yate sends INVITE at 00:00
2) provider responds with SIP 100 Trying at 00:00
3) and the next SIP 183 Session Progress will be only around 30 seconds later or more (usually it's for incorrect numbers only).

If provider succeeds to send "183 Session Progress" for less then 30 seconds then all is ok but in the most cases it's not and after 30-32 seconds Yate initiates CANCEL packets and I see the next message in the log:

2019-05-10_16:25:58.463548 <sip/1252:ALL> YateSIPConnection::hangup() state=1 trans=0x7f504001da10 error='noconn' code=408 reason='Request Timeout' [0x7f504001b640]

So the question is it possible to extend the timer so CANCEL will be initiated not after 30 seconds but later? Which configuration setting (if any) is responsible for it?

Thanks ahead.


  • Hero Member
  • *****
  • Posts: 513
    • View Profile
Re: Is it possible to extend timeout before YATE sends CANCEL?
« Reply #1 on: May 12, 2019, 11:48:47 PM »

Try to increase the t1 timer value (default is 500ms).
This timer controls various transaction timers including INVITE timeout.