<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">Le 20/01/2020 à 12:11, Joshua C. Colp a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAM0A2Z3k5oUNOk5ZYfN7fY79FBgYyvpB820wiqYka8Uf7ydAXQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">On Sun, Jan 19, 2020 at 10:45 AM Administrator
          <<a href="mailto:admin@tootai.net" moz-do-not-send="true">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>
              <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>
        </div>
      </div>
    </blockquote>
    Guess what: provider change registration port number from usual 5060
    :( <br>
    <blockquote type="cite"
cite="mid:CAM0A2Z3k5oUNOk5ZYfN7fY79FBgYyvpB820wiqYka8Uf7ydAXQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div>[...]<br>
              <br>
              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.</div>
          </blockquote>
          <div>Every time I've seen this occur it's been the result of a
            firewall rule gone awry.<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>You got it. Provider IP was blacklisted.</p>
    <p>[...]<br>
    </p>
    <p>Finally we got it up and working, thanks to you and C.Maj</p>
    <p>-- </p>
    <pre class="moz-signature" cols="72">Daniel</pre>
  </body>
</html>