I'm trying to get "blind transfer" from an incoming DAHDI line to an external number to work on an * 1.6 install using a T1 from XO. The documentation is very "distributed" and incomplete, so while it's not working, it's definitely more likely my error somehow. Couple questions if anybody is out there who even knows what TBCT is. 1) Is this even supported? 2) Does it require some settings in dahdi_channels, or features, or whatever? 3) Would I "trigger" it via a Dial command or commands, or via Transfer? 4) Do either or both of the legs need to be answered? Thanks very much. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090414/bd02cd99/attachment.htm
I know what TBCT is, but haven't used it with Asterisk yet. Hopefully will be soon. 1) Supposed to be supported by Asterisk. Is supported by XO (I use it with a different platform). 2) Dunno 3) Dunno 4) The ISDN spec sez that one of the calls needs to be active to initiate the transfer. --Don Don Kelly PCF Corp People Come First 651 842-1000 888 Don Kell(y) 651 842-1001 fax _____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Max Metral Sent: Tuesday, April 14, 2009 4:52 PM To: asterisk-users at lists.digium.com Subject: [asterisk-users] 2B Channel Transfer on XO-based T1 I'm trying to get "blind transfer" from an incoming DAHDI line to an external number to work on an * 1.6 install using a T1 from XO. The documentation is very "distributed" and incomplete, so while it's not working, it's definitely more likely my error somehow. Couple questions if anybody is out there who even knows what TBCT is. 1) Is this even supported? 2) Does it require some settings in dahdi_channels, or features, or whatever? 3) Would I "trigger" it via a Dial command or commands, or via Transfer? 4) Do either or both of the legs need to be answered? Thanks very much. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090414/c5ad2f5e/attachment.htm
On 4/14/09, Max Metral <max at povo.com> wrote:> > I?m trying to get ?blind transfer? from an incoming DAHDI line to an > external number to work on an * 1.6 install using a T1 from XO. The > documentation is very ?distributed? and incomplete, so while it?s not > working, it?s definitely more likely my error somehow. Couple questions if > anybody is out there who even knows what TBCT is? > > > > 1) Is this even supported? > > 2) Does it require some settings in dahdi_channels, or features, or > whatever? > > 3) Would I ?trigger? it via a Dial command or commands, or via > Transfer? > > 4) Do either or both of the legs need to be answered?Are you positive that your carrier PRI circuit has this feature enabled? If so, how much are they charging you for this service?(if they are not charging you for it monthly it is most likely not enabled) What kind of PRI do you have? (5ESS, NI2, DMS100,...) How many PRIs and trunk groups set up across them do you have? I have set up 2BCT for two different call center clients before, and neither implementation went smoothly as far as the carrier's part of it was concerned. Asterisk and zaptel(Dahdi) can handle it and will always attempt to do 2BCT on ALL native bridging of channels on the same trunk group if you have Transfer=yes in zapata.conf(or the Dahdi equivelent file). I have never configured 2BCT on an Asterisk 1.6 system, only 1.2 and 1.4 (using zaptel 1.4 for both), although I can't see any reason why it wouldn't work. MATT---
On Tue, 2009-04-14 at 17:52 -0400, Max Metral wrote:> I?m trying to get ?blind transfer? from an incoming DAHDI line to an > external number to work on an * 1.6 install using a T1 from XO. The > documentation is very ?distributed? and incomplete, so while it?s not > working, it?s definitely more likely my error somehow. Couple > questions if anybody is out there who even knows what TBCT is?> 1) Is this even supported?s Yes, it's supported in Asterisk and DAHDI, but your success in getting it to work will depend on many factors. As I understand it, it only works with certain switch types (I've had the best luck on 5ESS), and only when the telco enables that feature on your trunk group. In my experience, the telcos usually don't enable this feature by default, and it can be a pain to talk them into enabling it.> 2) Does it require some settings in dahdi_channels, or features, > or whatever?It requires the following features be enabled in chan_dahdi.conf (or zapata.conf, for later version of Zaptel): facilityenable=yes transfer=yes> > 3) Would I ?trigger? it via a Dial command or commands, or via > Transfer?Neither... it happens automagically! Some time after the second leg of the call has answered, Asterisk will send a facility message to the CO switch saying "Hey, mind bridging these two calls on your end, so I can free up the channels on my end?" If the switch says "OK", you'll see the calls disappear from Asterisk (and the people on the calls won't know the difference). Otherwise, the calls will continue to be bridged by Asterisk. Obviously there are options to the Dial() application that would preclude Asterisk from allowing the transfer to happen, such as the t, T, w, and W options (and I'm sure there are probably more).> 4) Do either or both of the legs need to be answered?It's my understanding that both legs need to be answered and bridged before this will happen, but I'm not 100% sure. One other minor thing I'll point out... assuming that your 2-B-channel transfer is successful, the telco will send a message to Asterisk at the time the call is eventually hung up. Unfortunately, Asterisk has long since forgotten about the call by that point, so it simply writes a harmless warning message to the console and goes on its merry way. (If a developer happens to read this and needs a pet project -- it would be nice if this would update the CDR records for the original call!) I hope that's enough documentation to get you started! Please let us know how it works out for you! -- Jared Smith Training Manager Digium, Inc.
Hi, I'm using it on 1.4. Actually, the driver does all the work. I have clients calling in, give them DISA, they dial the number and the call is pushed to the switch. Jimmy> -----Original Message----- > From: max at povo.com > Sent: Tue, 14 Apr 2009 17:52:23 -0400 > To: asterisk-users at lists.digium.com > Subject: [asterisk-users] 2B Channel Transfer on XO-based T1 > > I'm trying to get "blind transfer" from an incoming DAHDI line to an > external number to work on an * 1.6 install using a T1 from XO. The > documentation is very "distributed" and incomplete, so while it's not > working, it's definitely more likely my error somehow. Couple questions > if > anybody is out there who even knows what TBCT is. > > > > 1) Is this even supported? > > 2) Does it require some settings in dahdi_channels, or features, or > whatever? > > 3) Would I "trigger" it via a Dial command or commands, or via > Transfer? > > 4) Do either or both of the legs need to be answered? > > > > Thanks very much.
May I ask : beside saving channels, what are the benefits of TBCT over bridging calls inside Asterisk ? What about caller ids ? I would say caller id should passed over to final callee after bridging but that should need some kind of signaling update. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090415/55906a5d/attachment.htm
> -----Original Message----- > From: d at tucny.com > Sent: Wed, 15 Apr 2009 19:44:23 +0800 > To: asterisk-users at lists.digium.com > Subject: Re: [asterisk-users] 2B Channel Transfer on XO-based T1 > > 2009/4/15 Olivier <oza-4h07 at myamail.com> > >> May I ask : beside saving channels, what are the benefits of TBCT over >> bridging calls inside Asterisk ? >> > > I'm not aware of anything apart from saving channels... >You're also saving resources. You can have a higher call ratio when using TBCT since the channels are freed after the transfer.> >> >> What about caller ids ? I would say caller id should passed over to >> final >> callee after bridging but that should need some kind of signaling >> update. >> > > Passing the original callerID during a forward/unattended transfer is > standard North American functionality... Call comes in, forwarded out > either > over the same, or alternate, trunk, callerid left intact... A feature > that > can make using certain commercial PBXs in other countries somewhat > problematic... > > Updating the caller information during a call, including feeding back > connected callee information, is I believe, a qsig/dpnss addition used > within a private network (though there may be instances that it can work > in > a public network that I've not seen)... > > dSince you're dialing the second number, you send the callerid. Therefore, you can read the callerid from the caller and send it out on the second leg of the call. You can also change that information. Jimmy ____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium