<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi there!</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">We have a situation, primarily with specific numbers, where freeswitch executes a T.38 INVITE and our SIP provider is responding with a 408 Request Timeout, and Freeswitch responds with an ACK. </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">However, no BYE is sent and our SIP provider thinks the call is still active, and ends up billing us for a lot of dead air. Thankfully they have a timeout and stop billing us after 6 hours, but its still costing us a lot of money.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">The error Freeswitch is giving us in the cdr for this call is: RECOVERY_ON_TIMER_EXPIRE</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">We've used the latest code from git as well as 1.2, and the issue persists.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
Furthermore, the SIP provider claims this is not correctly following the RFC:If the response for a request within a dialog is a 481<br>(Call/Transaction Does Not Exist) or a 408 (Request Timeout), the UAC<br>SHOULD terminate the dialog. A UAC SHOULD also terminate a dialog if<br>
no response at all is received for the request (the client<br>transaction would inform the TU about the timeout.)<br><br>For INVITE initiated dialogs, terminating the dialog consists of<br>sending a BYE.</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks!</div></div>