<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <tt>Hi, Pete!<br>
      <br>
      I did not test this, but I think you can catch the 477 by checking
      the returned code of the t_relay() exit code. If it fails, simply
      call the use_next_gw() function.<br>
      <br>
      Best regards,<br>
    </tt>
    <pre class="moz-signature" cols="72">Răzvan Crainea
OpenSIPS Solutions
<a class="moz-txt-link-abbreviated" href="http://www.opensips-solutions.com">www.opensips-solutions.com</a></pre>
    <div class="moz-cite-prefix">On 01/04/2016 12:43 PM, Pete Kelly
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAEWH9M95qe_3i5EV=RXtUFR514CSy1J2OOLeY5Dj8BaJMXR4Sg@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Razvan
        <div><br>
        </div>
        <div>Happy New Year!</div>
        <div><br>
        </div>
        <div>Yes your answer is clear, thank you. I will do some
          experimentation but I think I may run into some issues. I am
          talking to some Cisco equipment which does not like the
          ;transport= suffix in the request URI so the socket
          specification is really a preferred option.</div>
        <div><br>
        </div>
        <div>In my case too I also want to be able to detect an internal
          477 (for example if t_relay with TCP should fail and the TCP
          can be changed to UDP). I guess I could still catch the
          t_relay failure and just call use_next_gw() in dispatcher.</div>
        <div><br>
        </div>
        <div>Pete</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 23 December 2015 at 13:43, Răzvan
          Crainea <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF"> <tt>Hi, Pete!<br>
                <br>
                The best way to do it is choice number 1, where you
                specify the transport=tls parameter in the URI. The
                socket field is used to specify which listener OpenSIPS
                should use to send the request to that destination. It
                has a similar meaning with force_send_socket() (iirc,
                internally it is implemented in the same way).<br>
                Therefore with choice number 2, it is not guaranteed to
                work. In most cases it will, but if you force a
                different transport for your destination (for example
                you have a TCP destination) and use a TLS socket, it
                might not work (haven't tested that).<br>
                <br>
                I hope my answer is clear.<br>
                <br>
                Best regards,<br>
              </tt>
              <pre cols="72">Răzvan Crainea
OpenSIPS Solutions
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">www.opensips-solutions.com</a></pre>
              <div>
                <div class="h5">
                  <div>On 12/22/2015 04:52 PM, Pete Kelly wrote:<br>
                  </div>
                </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div class="h5">
                    <div dir="ltr">Hi all!
                      <div><br>
                        <div>Is there an "approved" way to send to a TLS
                          destination using the dispatcher module?</div>
                        <div><br>
                          I notice there could be 2 ways to specify TLS
                          within the tables/configuration:</div>
                        <div><br>
                        </div>
                        <div>1) By using the destination field (by
                          suffixing with ;transport=tls)</div>
                        <div>2) By using the socket field (by specifying
                          the local tls: socket).</div>
                        <div><br>
                        </div>
                        <div>Is only one (or both) of these normally
                          required?</div>
                      </div>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                  </div>
                </div>
                <pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
              </blockquote>
              <br>
            </div>
            <br>
            _______________________________________________<br>
            Users mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
              rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>