<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Yes, very vague subject. Sorry about that. Some calls to certain wireless carriers on our ITSP connections have started failing. <br></div><div><br></div><div>Win10 Jabber client (off of 12.5.su3) -> CUBE -> ITSP</div><div><br></div><div>The call goes out Lumen, the 401 auth and challenge response are fine, the INVITE is then sent with SDP. We get a TRYING response which we immediately ACK. Up until this point, the entire call flow is NORMAL. <br></div><div><br></div><div> If we don't receive a 18X response within 7 Seconds, the, the CUBE sends a cancel. Yes, the CUBE.<br></div><div><br></div><div>It appears that the far end is taking too long to send the 18X message. we involved our carrier and they can see the 18X come back a split second later (sometimes), but our side has already closed the connection.<br></div><div><br></div><div>I looked at all of the sip-ua timers and retry settings. nothing adds up to 7 seconds. Most timers are set to 500 msec. I'm not sure where to look? It's not on the sip profile.<span style="color:var(--pageTextColor);"> </span><span style="color:var(--pageTextColor);">i tried bumping up the connect, update, info and trying timers (one at a time), but it didn't make any difference. Maybe I was supposed to do something to make sip-ua changes "kick in" like bounce the sip service which I didn't do... not sure on that part.</span><br></div><div><br></div><div>Please tell me there is something simple I'm missing. Pointers?</div><div><br></div><div id="sig91721560"><div class="signature">Thanks,<br></div><div class="signature">Nick<br></div><div class="signature"><br></div><div class="signature"><br></div><div class="signature">p.s. : some possibly relevant config and the timers and retries from my sip-ua<br></div><div class="signature"><br></div><div class="signature">retry invite 2<br></div></div><div>retry response 6<br></div><div>retry bye 10<br></div><div>retry cancel 10<br></div><div>retry prack 10<br></div><div>retry update 6<br></div><div>retry rel1xx 6<br></div><div>retry notify 10<br></div><div>retry refer 10<br></div><div>retry info 6<br></div><div>retry register 6<br></div><div>retry subscribe 6<br></div><div>retry keepalive 6<br></div><div>retry options 6<br></div><div>timers trying 500<br></div><div>timers expires 180000<br></div><div>timers connect 500<br></div><div>timers connection aging 5<br></div><div>timers disconnect 500<br></div><div>timers prack 500<br></div><div>timers update 500<br></div><div>timers rel1xx 500<br></div><div>timers notify 750<br></div><div>timers refer 500<br></div><div>timers hold 2880<br></div><div>timers info 500<br></div><div>timers register 500<br></div><div>timers buffer-invite 0<br></div><div>timers keepalive down 30<br></div><div>timers keepalive active 120<br></div><div>timers dns registrar-cache 3600<br></div><div>timers options 500<br></div></body></html>