<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ES-AR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mark, Rusty,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The proposed config option fixes the problem. I've sent feedback mentioning this in the issue tracker.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Anatoli<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> asterisk-dev-bounces@lists.digium.com [mailto:asterisk-dev-bounces@lists.digium.com] <b>On Behalf Of </b>Mark Michelson<br><b>Sent:</b> Friday, February 20, 2015 14:02<br><b>To:</b> Asterisk Developers Mailing List<br><b>Subject:</b> Re: [asterisk-dev] Possible bug – missing mandatory field Max-Forwards<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Thanks for pointing this out.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have commented on the issue with instructions with what I think is going wrong here.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Feb 19, 2015 at 6:33 PM, Anatoli <<a href="mailto:me@anatoli.ws" target="_blank">me@anatoli.ws</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Hi All,<br><br>I was evaluating the latest Asterisk (13.2.0) with the latest PJSIP (2.3) and found a critical problem (critical if some of the endpoints enforce compliance with the SIP RFC).<br><br>I had a discussion on pjsip mailing list about this (<a href="http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2015-February/018120.html" target="_blank">http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2015-February/018120.html</a>) where the consensus was that there is a bug in res_pjsip code that manages SIP headers. The problem consists in that first the code in res_pjsip.c removes Max-Forwards header from the request generated by PJSIP library, but it doesn't add it later, so Asterisk sends INVITE, ACK, BYE, etc. messages without this mandatory header and RFC enforcing clients reject these messages.<br><br>I've also submitted a bug report in the Asterisk issue tracker: <a href="https://issues.asterisk.org/jira/browse/ASTERISK-24807" target="_blank">https://issues.asterisk.org/jira/browse/ASTERISK-24807</a>. It has a patch for a workaround, but it's not the correct way of addressing the problem (it patches pjsip library when the problem is inside res_pjsip adapter).<br><br>Regards,<br>Anatoli<br><span style='color:#888888'><br><br><span class=hoenzb>--</span><br><span class=hoenzb>_____________________________________________________________________</span><br><span class=hoenzb>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --</span><br><br><span class=hoenzb>asterisk-dev mailing list</span><br><span class=hoenzb>To UNSUBSCRIBE or update options visit:</span><br><span class=hoenzb> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a></span></span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>