<div dir="ltr"><div dir="ltr">On Sun, Jan 19, 2020 at 10:45 AM Administrator <<a href="mailto:admin@tootai.net">admin@tootai.net</a>> wrote:<br></div><div class="gmail_quote"><div><br></div><div><snip> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p></p><blockquote type="cite"><div dir="ltr"><div class="gmail_quote">
        </div>
      </div>
    </blockquote>
    <p>It become stranger and stranger: on one of the register peer we
      receive in asterisk:</p>
    <p>*CLI> [2020-01-19 15:23:18] WARNING[17469]:
      res_pjsip_outbound_registration.c:1021
      handle_registration_response: Fatal response '401' received from
      'sip:<myprovider>' on registration attempt to
      'sip:<myuser>@<myprovider>', stopping outbound
      registration</p></div></blockquote><div>What is the actual full configuration for this? <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <p>On the other one:</p>
    <p>[2020-01-19 15:23:46] WARNING[17469]:
      res_pjsip_outbound_registration.c:801 schedule_retry: No response
      received from 'sip:<other provider>' on registration attempt
      to 'sip:<other user@other provider>', retrying in '60'</p>
    <p>*BUT*</p>
    <p>IP <other provider IP>.5060 10.1.58.14.64777: UDP, length
      497<br>
      E...e...6....2N$<br>
      .:....  ..RQSIP/2.0 401 Unauthorized<br>
      Via: SIP/2.0/UDP <our public
IP>:5060;rport=64777;branch=z9hG4bKPjdfb1d5d6-efbd-4e43-a932-252cfa0e7a9b                                                       
      <br>
      From: <sip:<otheruser@other
provider>;tag=743c09d7-bdf9-4579-b7be-b087b0f19a46                                                                          
      <br>
      To: <sip:<other user@<other
provider>;tag=a4993fce1db28f0d818901aca45fc7e1-39af                                                                           
      <br>
      Call-ID: fadecc03-31e1-50ef-b686-d1a6b7ea0eda<br>
      CSeq: 49518 REGISTER<br>
      WWW-Authenticate: Digest realm="<other provider>",
      nonce="XiRnoo5Qbfr8xRP1yNPD+Piy/eKORSub",
      qop="auth"                                                <br>
      Content-Length: 0</p>
    <p>So the answer is coming back to the server but not to asterisk.
      With the debian package of asterisk-16 the 401 response was
      received by asterisk.</p></div></blockquote><div>Every time I've seen this occur it's been the result of a firewall rule gone awry.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
    <p>We now have 2 problems:</p>
    <p>- why asterisk doesn't get the answer of one of the provider</p>
    <p>- why when receiving the 401 from the other provider it doesn't
      then the Authorization back</p>
    <p>If it matter, server is a VM using ipv4 and ipv6, we have mtu
      setted to 1492 and use nft for FW rules.<br>
    </p>
    </blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:tahoma,sans-serif"><font color="#073763">Joshua C. Colp</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Asterisk Technical Lead</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Sangoma Technologies</font></div><div style="font-family:tahoma,sans-serif"><font color="#073763">Check us out at <a href="http://www.sangoma.com" target="_blank">www.sangoma.com</a> and <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a></font><br></div></div></div></div></div></div></div></div></div></div></div>