[sirtwist]

Ok... subject line doesn't really do this one justice.

I'm using AAH 2.8, latest version of freePBX. I have two trunks from ViaTalk plus two "virtual" numbers. The two virtual numbers are set up within ViaTalk's system to forward to extension@ourasteriskserver so that they can in effect be DIDs for our extensions.

I'll use my extension as an example - 801. I have set it up at ViaTalk to forward to 801@ourserver. This brings the call in to our server just fine.

On our AAH server I've set up an Inbound Route for 801 and set it to go to the Follow me for extension 801. Follow me is set up to do memory hunt.

What happens is this:

Call is made from a POTS line to the DID number, it forwards to 801@ourserver. Our AAH rings the SIP phone at 801. If I let it ring until it times out, it goes onto the next step in the memory hunt which is keep ringing 801 but also ring my cell phone. At this point, on the POTS line where I initiated the call I get a "fast busy" signal and the call is essentially dead.

Follow me works fine if someone calls our main number, hits our IVR and dials 801. It'll ring my SIP phone, then my cell, with no problems. It's only when forwarding directly to the server via a SIP address that it has a problem making outbound calls.

I *think* it's related to the fact that forwarded call is unauthenticated, but I'm not sure.

Has anyone ever seen anything like this or have any ideas?