[asterisk-users] Zap Call deflection on PRI

Steve Totaro stotaro at totarotechnologies.com
Wed Feb 27 09:19:28 CST 2008


Now to come up with a way to "busy" out individual channels via this
or another method.  This is one feature that is in great demand.

Thanks,
Steve Totaro

On Wed, Feb 27, 2008 at 10:03 AM, Jon Schøpzinsky <jos at detele.dk> wrote:
> Actually this isnt the same as Two B-Channel transfer.
>  This is done by sending a FACILITY message to the ISDN, which in hand then disconnects the call and sends it to the number provided in the call deflection message.
>  All b-channels are closed when the FACILITY message is sent.
>  You can also send a deflection reason code, such as Busy and Unavailable.
>
>  Jon
>
>
>
>  -----Original Message-----
>  From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Jared Smith
>  Sent: 27. februar 2008 15:42
>  To: Asterisk Users Mailing List - Non-Commercial Discussion
>  Subject: Re: [asterisk-users] Zap Call deflection on PRI
>
>  On Wed, 2008-02-27 at 08:50 -0500, Steve Totaro wrote:
>  > I recall that this is now part of Asterisk (1.4 or 1.6 or both).  It
>  > really is a great feature rather than using two channels in "trunk to
>  > trunk" transfer.
>
>  This is often called a "Two B-Channel Transfer", or TBCT.  As long as
>  your PRI provider has this service enabled on your PRI, recent versions
>  of libpri, zaptel, and Asterisk will support this.  Obviously it won't
>  work if your PRI provider hasn't enabled TBCT on your PRI.
>
>  On the Asterisk side of things, you need to make sure you have
>  "facilityenable=yes" and "transfer=yes" in zapata.conf for the bearer
>  channels of your PRI.
>
>  --
>  Jared Smith
>  Community Relations Manager
>  Digium, Inc.
>
>



More information about the asterisk-users mailing list