+2020-06-09 09:02 +0000 Asterisk Development Team <asteriskteam@digium.com>
+
+ * asterisk 17.5.0-rc3 Released.
+
+2020-06-04 01:50 +0000 [dd5fb6dad1] Pirmin Walthert <infos@nappsoft.ch>
+
+ * res_pjsip_logger: use the correct pointer when logging tx_messages to pcap
+
+ When writing tx messages to pcap files, Asterisk is using the wrong
+ pointer resulting in lots of wasted space. This patch fixes it to use
+ the correct pointer.
+
+ ASTERISK-28932 #close
+
+ Change-Id: I5b8253dd59a083a2ca2c81f232f1d14d33c6fd23
+
2020-06-02 08:58 +0000 Asterisk Development Team <asteriskteam@digium.com>
* asterisk 17.5.0-rc2 Released.
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><title>Release Summary - asterisk-17.5.0-rc
2</title><h1 align="center"><a name="top">Release Summary</a></h1><h3 align="center">asterisk-17.5.0-rc2</h3><h3 align="center">Date: 2020-06-02</h3><h3 align="center"><asteriskteam@digium.com></h3><hr><h2 align="center">Table of Contents</h2><ol>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><title>Release Summary - asterisk-17.5.0-rc
3</title><h1 align="center"><a name="top">Release Summary</a></h1><h3 align="center">asterisk-17.5.0-rc3</h3><h3 align="center">Date: 2020-06-09</h3><h3 align="center"><asteriskteam@digium.com></h3><hr><h2 align="center">Table of Contents</h2><ol>
<li><a href="#summary">Summary</a></li>
<li><a href="#contributors">Contributors</a></li>
<li><a href="#closed_issues">Closed Issues</a></li>
<li><a href="#diffstat">Diffstat</a></li>
-</ol><hr><a name="summary"><h2 align="center">Summary</h2></a><center><a href="#top">[Back to Top]</a></center><p>This release is a point release of an existing major version. The changes included were made to address problems that have been identified in this release series, or are minor, backwards compatible new features or improvements. Users should be able to safely upgrade to this version if this release series is already in use. Users considering upgrading from a previous version are strongly encouraged to review the UPGRADE.txt document as well as the CHANGES document for information about upgrading to this release series.</p><p>The data in this summary reflects changes that have been made since the previous release, asterisk-17.5.0-rc
1.</p><hr><a name="contributors"><h2 align="center">Contributors</h2></a><center><a href="#top">[Back to Top]</a></center><p>This table lists the people who have submitted code, those that have tested patches, as well as those that reported issues on the issue tracker that were resolved in this release. For coders, the number is how many of their patches (of any size) were committed into this release. For testers, the number is the number of times their name was listed as assisting with testing a patch. Finally, for reporters, the number is the number of issues that they reported that were affected by commits that went into this release.</p><table width="100%" border="0">
+</ol><hr><a name="summary"><h2 align="center">Summary</h2></a><center><a href="#top">[Back to Top]</a></center><p>This release is a point release of an existing major version. The changes included were made to address problems that have been identified in this release series, or are minor, backwards compatible new features or improvements. Users should be able to safely upgrade to this version if this release series is already in use. Users considering upgrading from a previous version are strongly encouraged to review the UPGRADE.txt document as well as the CHANGES document for information about upgrading to this release series.</p><p>The data in this summary reflects changes that have been made since the previous release, asterisk-17.5.0-rc
2.</p><hr><a name="contributors"><h2 align="center">Contributors</h2></a><center><a href="#top">[Back to Top]</a></center><p>This table lists the people who have submitted code, those that have tested patches, as well as those that reported issues on the issue tracker that were resolved in this release. For coders, the number is how many of their patches (of any size) were committed into this release. For testers, the number is the number of times their name was listed as assisting with testing a patch. Finally, for reporters, the number is the number of issues that they reported that were affected by commits that went into this release.</p><table width="100%" border="0">
<tr><th width="33%">Coders</th><th width="33%">Testers</th><th width="33%">Reporters</th></tr>
<tr valign="top"><td width="33%">1 Pirmin Walthert <infos@nappsoft.ch><br/></td><td width="33%"><td width="33%">1 nappsoft <infos@nappsoft.ch><br/></td></tr>
-</table><hr><a name="closed_issues"><h2 align="center">Closed Issues</h2></a><center><a href="#top">[Back to Top]</a></center><p>This is a list of all issues from the issue tracker that were closed by changes that went into this release.</p><h3>Bug</h3><h4>Category: Resources/res_pjsip_logger</h4><a href="https://issues.asterisk.org/jira/browse/ASTERISK-289
21">ASTERISK-28921</a>: Wrong return value check for fwrite when writing to pcap file<br/>Reported by: nappsoft<ul>
-<li><a href="https://code.asterisk.org/code/changelog/asterisk?cs=cb6b700ae344ef8d4ba79606906a8b3e78febb58">[cb6b700ae3]</a> Pirmin Walthert -- res_pjsip_logger.c: correct the return value checks when writing to pcap</li>
+</table><hr><a name="closed_issues"><h2 align="center">Closed Issues</h2></a><center><a href="#top">[Back to Top]</a></center><p>This is a list of all issues from the issue tracker that were closed by changes that went into this release.</p><h3>Bug</h3><h4>Category: Resources/res_pjsip_logger</h4><a href="https://issues.asterisk.org/jira/browse/ASTERISK-289
32">ASTERISK-28932</a>: res_pjsip_logger writing too big packets<br/>Reported by: nappsoft<ul>
+<li><a href="https://code.asterisk.org/code/changelog/asterisk?cs=dd5fb6dad1b1256108598aabfd0a2b7b8497c551">[dd5fb6dad1]</a> Pirmin Walthert -- res_pjsip_logger: use the correct pointer when logging tx_messages to pcap</li>
</ul><br><hr><a name="diffstat"><h2 align="center">Diffstat Results</h2></a><center><a href="#top">[Back to Top]</a></center><p>This is a summary of the changes to the source code that went into this release that was generated using the diffstat utility.</p><pre>0 files changed</pre><br></html>
\ No newline at end of file
Release Summary
- asterisk-17.5.0-rc2
+ asterisk-17.5.0-rc3
- Date: 2020-06-02
+ Date: 2020-06-09
<asteriskteam@digium.com>
to this release series.
The data in this summary reflects changes that have been made since the
- previous release, asterisk-17.5.0-rc1.
+ previous release, asterisk-17.5.0-rc2.
----------------------------------------------------------------------
Category: Resources/res_pjsip_logger
- ASTERISK-28921: Wrong return value check for fwrite when writing to pcap
- file
+ ASTERISK-28932: res_pjsip_logger writing too big packets
Reported by: nappsoft
- * [cb6b700ae3] Pirmin Walthert -- res_pjsip_logger.c: correct the return
- value checks when writing to pcap
+ * [dd5fb6dad1] Pirmin Walthert -- res_pjsip_logger: use the correct
+ pointer when logging tx_messages to pcap
----------------------------------------------------------------------
projects / thirdparty / asterisk.git / commitdiff
