| Summary: | ASTERISK-25539: 488 Not acceptable here sent after T.38 re-invite accepted | ||
| Reporter: | David Cunningham (dcunningham) | Labels: | |
| Date Opened: | 2015-11-10 20:43:12.000-0600 | Date Closed: | 2015-11-11 05:48:07.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 1.8.22.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Debian 6.0.7, 64 bit. | Attachments: | ( 0) ticket-3992-asterisk-2.log.gz |
| Description: | We have an issue where:
14:19:08 Fax machine makes call to Asterisk 14:19:08 Asterisk dials SIP termination provider 14:19:23 SIP termination provider accepts call 14:19:28 SIP termination provider sends T.38 re-invite 14:19:28 Asterisk sends T.38 re-invite to fax machine 14:19:28 Fax machine accepts re-invite 14:19:33 Asterisk appears to do nothing for 5 seconds and then sends "488 Not acceptable here" to SIP termination provider This is in the attached Asterisk trace, where the call from the fax machine has ID BC3FB901-81AF11E5-8D388D32-AD053ED@BB.BB.46.68 and the call to the SIP termination provider has ID 026a9cbd104dbb311dc9963a05702766@AA.AA.224.228:5060. Could you please advise why after getting the 200 OK at 14:19:28 it takes 5 seconds for Asterisk to send the "488 Not acceptable here", and why the 488 is sent? I notice there are a lot of "Bridge still active. Delaying destroy of SIP dialog" messages relating this call, but I think they're harmless? Thanks for your help. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-11-10 20:43:14.223-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: David Cunningham (dcunningham) 2015-11-10 20:44:02.362-0600 Apologies for the gzipped file - the log is quite large. By: David Cunningham (dcunningham) 2015-11-10 20:46:39.827-0600 T.38 settings in sip.conf: t38pt_udptl = yes t38_udptl = yes t38pt_rtp = no t38pt_tcp = no By: Joshua C. Colp (jcolp) 2015-11-11 05:47:57.165-0600 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: i2045 (i2045) 2015-11-15 13:47:54.863-0600 You could try to apply the patch in ASTERISK-21955 to Asterisk 1.8. | ||