[cisco-voip] Outbound SIP connection failing in CUBE due to some timer... maybe.
Carlo Calabrese
carlo_calabrese2006 at yahoo.com
Fri Apr 16 12:04:37 EDT 2021
Was this working before?I had problems before on a 4331 CUBE. I had to redo the password on the CUBE to Lumen.it was the same password that was already there. and a reboot didn't fix it.
On Friday, April 16, 2021, 08:32:22 AM PDT, Sreekanth Narayanan (sreenara) via cisco-voip <cisco-voip at puck.nether.net> wrote:
Nick,
What's the disconnect cause from the CUBE? 102?
Do you have logs for this call? Would be clear which timers are expiring, causing the problem.debug ccsip messagedebug ccsip errordebug ccsip info
-sreekanthFrom: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Nick Barnett <nick at barnett.email>
Sent: Friday, April 16, 2021 6:53 PM
To: cisco-voip <cisco-voip at puck.nether.net>
Subject: [cisco-voip] Outbound SIP connection failing in CUBE due to some timer... maybe. Yes, very vague subject. Sorry about that. Some calls to certain wireless carriers on our ITSP connections have started failing.
Win10 Jabber client (off of 12.5.su3) -> CUBE -> ITSP
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.
If we don't receive a 18X response within 7 Seconds, the, the CUBE sends a cancel. Yes, the CUBE.
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.
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. 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.
Please tell me there is something simple I'm missing. Pointers?
Thanks,
Nick
p.s. : some possibly relevant config and the timers and retries from my sip-ua
retry invite 2
retry response 6
retry bye 10
retry cancel 10
retry prack 10
retry update 6
retry rel1xx 6
retry notify 10
retry refer 10
retry info 6
retry register 6
retry subscribe 6
retry keepalive 6
retry options 6
timers trying 500
timers expires 180000
timers connect 500
timers connection aging 5
timers disconnect 500
timers prack 500
timers update 500
timers rel1xx 500
timers notify 750
timers refer 500
timers hold 2880
timers info 500
timers register 500
timers buffer-invite 0
timers keepalive down 30
timers keepalive active 120
timers dns registrar-cache 3600
timers options 500
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20210416/98c4c50c/attachment.htm>
More information about the cisco-voip
mailing list