<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi Brian,<br>
    <br>
    Which one? The one that doesn't work? If so, I'm not sure what you
    mean by "dial-string". Unless you're talking about the
    &lt;destno&gt; bit (which seems not to matter at all, it's just the
    originator part that is the problem).<br>
    <br>
    I've tested so far with &lt;destno&gt; as an extension on the local
    machine and as one on a remote server (Mitel and another FS box) and
    it's the same on both. The &lt;destno&gt;s are all referenced in the
    dialplan.<br>
    <br>
    eg<br>
    <br>
    originate user/1000 1234 XML default<br>
    <br>
    and <br>
    <br>
    originate user/1000 117399 XML default<br>
    <br>
    both exhibit the problem, where 1234 is a local extension on the
    same FS instance and 117399 is routed through a gateway. Those two
    destinations ring OK once the endpoint that has been ringing on
    "1000" has picked up, <br>
    <br>
    it's just that I have 2 endpoints registered as "1000@domain" and
    only one of them rings when the originate starts if I user the
    user/1000 syntax. Using loopback makes all registered extensions
    "1000@domain" ring for the A leg (if that's the right term to use
    for that).<br>
    <br>
    Cheers<br>
    <br>
    Alex<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 29/04/14 20:06, Brian West wrote:<br>
    </div>
    <blockquote
      cite="mid:7EFB3542-2A3F-4798-A13F-4506FCF08C65@freeswitch.org"
      type="cite">What does your dial-string and logs look like for that
      originate?<br>
      <div>--<br>
        Brian West<br>
        <a moz-do-not-send="true" href="mailto:brian@freeswitch.org">brian@freeswitch.org</a><br>
        <br>
        <span><img apple-inline="yes"
            id="FC4EF006-1EEB-4A3A-9AEC-DDC56541BA45" apple-width="yes"
            apple-height="yes"
            src="cid:part2.02010706.09030208@integrafin.co.uk"
            height="73" width="240"></span><br>
        <br>
        Twitter: @FreeSWITCH , @briankwest<br>
        <a class="moz-txt-link-freetext" href="http://www.freeswitchbook.com">http://www.freeswitchbook.com</a><br>
        <a class="moz-txt-link-freetext" href="http://www.freeswitchcookbook.com">http://www.freeswitchcookbook.com</a><br>
        <br>
        T: +1.918.420.9001&nbsp; | &nbsp;F: +1.918.420.9002 &nbsp;| &nbsp;M: +1.918.424.WEST<br>
        iNUM: +883 5100 1420 9001<br>
        ISN: 410*543<br>
        Skype:briankwest<br>
        PGP Key: <a class="moz-txt-link-freetext" href="http://www.bkw.org/key.txt">http://www.bkw.org/key.txt</a> (AB93356707C76CED)<br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
      </div>
      <br>
      On Apr 29, 2014, at 12:33 PM, Alex Crow &lt;<a
        moz-do-not-send="true" href="mailto:acrow@integrafin.co.uk">acrow@integrafin.co.uk</a>&gt;
      wrote:<br>
      <br>
      <blockquote type="cite">Hi,<br>
        <br>
        Is it part of the implementation of sofia that means, even with
        a shared&nbsp;<br>
        reg and presence db, that if I have the same extension
        registered on&nbsp;<br>
        both the default profile and a NAT profile, that<br>
        <br>
        originate user/1000 &lt;destno&gt;<br>
        <br>
        seems to only ring one of the registered endpoints (and it seems
        so far&nbsp;<br>
        random which one rings), while<br>
        <br>
        originate loopback/1000 &lt;destno&gt;<br>
        <br>
        and for an existing call<br>
        <br>
        bridge user/1000<br>
        <br>
        happily rings both endpoints?<br>
        <br>
        Cheers<br>
        <br>
        Alex<br>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
<a class="moz-txt-link-abbreviated" href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitchsolutions.com">http://www.freeswitchsolutions.com</a>

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
<a class="moz-txt-link-freetext" href="http://www.cudatel.com">http://www.cudatel.com</a>

Official FreeSWITCH Sites
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.freeswitch.org">http://wiki.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://www.cluecon.com">http://www.cluecon.com</a>

FreeSWITCH-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a></pre>
    </blockquote>
    <br>
  </body>
</html>