<div dir="ltr">On Wed, May 15, 2013 at 12:10 PM, Ken D'Ambrosio <span dir="ltr"><<a href="mailto:ken@jots.org" target="_blank">ken@jots.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hey, all. I've got an office set up with Asterisk, and forwarding's got a bit of a glitch:<br>
When they forward, they listen for the remote phone to ring, then hang up. If the remote phone doesn't connect, it goes to the original phone's VM. Is this Polycom's "fault," or Asterisk's? I've been reading up on blind/supervised forwards, and, honestly, have myself more confused than when I started. If someone could give me a solid idea of how forwarding works, and a sample of how to send it to a remote extension, and have it *not* come back to the original extension, that'd be great.<br>
</blockquote><div><br></div><div style>You said "forwarding" but described a process that sounds like call transfer. I'm going to assume you mean the latter?</div><div style><br></div><div style>We just had a report of this from a customer on their own server. I haven't had time to investigate it. We have confirmed it with Grandstream and Cisco SPA phones, so it's not just Polycom.</div>
<div style><br></div><div style>As far as the atxferdropcall someone suggested, I did try that and then the call is just dropped off into limbo. The caller is left on hold, and the nothing happens on the called extension or transfer-to extension.</div>
</div><div><br></div>-- <br><div>Carlos Alvarez</div><div>TelEvolve</div><div>602-889-3003</div><div><br></div>
</div></div>