| Summary: | ASTERISK-14762: T38 outgoing fax produces RTP error | ||
| Reporter: | Hendrik van der Ploeg (elsto) | Labels: | |
| Date Opened: | 2009-09-03 09:36:19 | Date Closed: | 2009-09-18 11:54:17 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/RTP |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When sending a T38 outgoing fax is produces the error below rtp.c:1631 ast_rtp_read: RTP Read too short | ||
| Comments: | By: Hendrik van der Ploeg (elsto) 2009-09-03 12:19:37 Setting insecure to "port" in sip.conf lets the error disappear. Now it gives this error. chan_sip.c: Maximum retries exceeded on transmission for seqno 2 (Critical Response) -- See doc/sip-retransmit.txt T.38 faxing worked before..... By: Leif Madsen (lmadsen) 2009-09-16 11:14:56 Can you provide some debugging information about the call? I believe a sip debug and sip history from the Asterisk console, along with debug level logging would be useful in this situation. More information about debugging SIP issues is available in the bug guidelines. Thanks! http://asterisk.org/developers/bug-guidelines By: Hendrik van der Ploeg (elsto) 2009-09-16 11:52:20 As you may have noticed I have solved the T38 faxing problem with Asterisk-1.6.1.6 + a Patch for udptl.c. Bug ASTERISK-14531 For me personal, it is not necessary that this bug (15823) is solved. Are you still interested in debugging info? By: Leif Madsen (lmadsen) 2009-09-18 11:54:17 Closing this issue as another issue is actually helping to solve this issue along with Asterisk 1.6.1.6, so additional debugging and work should be done in the issue mentioned by the reporter. Thanks for the feedback! | ||