1) Inbound calls terminate on a T1/E1 trunk of a UC520 (ie. Voice IOS router)
2) Rotuer matches the call on an inbound dial-peer, answers it
3) Somehow, the router now decides to redirect the caller. Instead of setting up a new call leg, it uses an ISDN-level signal to tell the incoming leg (from the Telco's switch) to instead dial a different number.
The goal of doing it this way is so that:
1) the calling-number of the original inbound leg is presented to the redirectee
2) hey, we save ourselves a call
If it's feasible-from-a-signalling-perspective, is a TclIVR script required? Or is there a way of configuring the dial-peers on the Voice router to do it? For example, the initial out-bound leg of the call is a SIP dial-peer, and the router receives a SIP REDIRECT from it ... how to tell the router to 'forward the redirect to the inbound leg', rather than looking for a new outbound peer?
Yes, that would do. The main point is not so much avoiding tying up the channels, but making sure that the eventual transferee has the original caller's number show up on caller-line-id. (Although avoiding call redirection charges and 2 channels is a bonus).
How does one typically invoke the TNT feature? Is a TclIVR script indicated here, or is there some fancy things one can do with dial-peers?
Hmm, won't the original caller hear the DTMF sounds on the line? Apart from that, I like this solution.
Alternatively, I have located a whole bunch of information on doing redirects with TCBT (Two B-Channel Transfer) . In that scenario, you can apparently tell the teclo switch to connect two call legs on the same ISDN trunk, even if the 2nd one is outbound (and even when the 2nd one is in the 'ringing' state, which is nice). But it's not clear which Caller-ID will be presented to the eventual recipient of the call. Do you have any experience with this?
I'm asking around in the TclIVR community for some specifics on how to practically access this functionality in a script.
Thanks Karthik. Hi, yes all of the above are true, I believe. The telco is Telstra, and the product is their ISDN10, which I believe uses an NI-2 type switch. Their literature suggests that it is possible to subscribe to an ISDN-delivered transfer service like this. (I will check all of this with them soon).
But I would really like to know if it is feasible to instruct the NI-2 compliant switch to present the caller-ID of the transferee to the tranfer-to party?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...