11-04-2015 11:19 AM - edited 03-19-2019 10:19 AM
We have a set of call handlers that direct calls based on caller input, i.e.:
-Instead it plays the transfer greeting, "Please wait while I transfer your call", MOH plays, and then dead silence.
It does not ring, then you are forced to hang it up. It's like the call gets sent (to the SIP router I am guessing), but never gets there or gets terminated on that end.
All other options within the handlers work (transferring to an internal extension, and transfer to an additional call handler)
Any help would be greatly appreciated, or any ideas on where else to troubleshoot.
11-05-2015 08:46 AM
Yea I have a catch all outgoing dial-peer.
On the router if I do the "show dialplan number *****" , it matches a dial peer
Also if a user directly dials the number from their desk phone, it gets out no problem
11-06-2015 10:28 AM
Hi Joseph,
Just thought I might add one note to the great tips from Nadeem, Vivek, Lorenz & Anna (+5 each folks!)
I would check the Transfer Restriction Tables in Unity Connection admin to see if the desired number is allowed in the table. By default, this type of transfer to external would be blocked to prevent Toll Fraud. See attached link;
Cheers!
Rob
11-06-2015 10:44 AM
Yea I ran into this suggestion a couple of days ago. Is it incorrect to simply uncheck them all?
The weird thing is, this was all working before we implemented a new "AutoAttendant" setup, with more call handlers etc., and I never messed with that setting before?
I have the Default System Transfer and Default Transfer all unchecked, as far as testing purposes go. If I got it working, I would just go back and check one by one.
or is there a conflict by unchecking all the blocked options
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide