-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected BYE, 408 "Session timeout" with Aastra 400 #284
Comments
I have attached console logs and captures of the problem. BehaveVanillaReproConsole.txt.gz |
From my investigation, it looks like the session timer parameters may not be set correctly during initialization:
and
The
The issue seems to be fixed with that change.
I'm doing further testing now. |
Version:
FreeSWITCH version: 1.10.12-release+git~20240802T210227Z~a88d069d6f~64bit (git a88d069 2024-08-02 21:02:27Z 64bit)
Sofia:
sofia-sip-1.13.17
An Aastra 400 calls FreeSWITCH as a client. Less than 120 seconds later, FreeSWITCH hangs up with an unexpected BYE, and "Session timeout" for the reason. The problem only occurs when the UAC is outside the local network.
I have reproduced this using a test script, and the error happens only when the NAT is in use from an external address. To reproduce the error under test, I connect a Raspberry PI through my cell phone, and then run a Python Behave script against my test server. The error will not reproduce when the UAC is on the same network as the server.
From fs_cli:
nua_session.c:1564 nua_session_usage_refresh() nua(0x7a56ec0509a0): session almost expired, sending BYE before timeout.
In mod_sofia.c, I found that commenting out the check for Aastra in
sofia_receive_message()
(line 2071) allows the call to complete normally.What sets off the unexpected action is a 200 OK to an UPDATE, with "
Session-Expires: 1800;refresher=uas
". IfSession-Expires
does not have the "refresher", then the premature BYE does not occur.The text was updated successfully, but these errors were encountered: