VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
jos at detele.dk
Guest
|
 Posted: Wed Feb 27, 2008 4:38 am Post subject: [asterisk-users] Zap Call deflection on PRI |
 |
|
Hello List.
I have created a patch some time ago, to use the ISDN feature "call deflection" or partial rerouting, as it Is also known, to make proper call transfers on PRI, without using an extra channel for the outgoing call.
Back then I ported the function zapCD from bristuff, to a normal zaptel, and it worked as it should.
I am looking at this again, and was wondering if anybody has made a similar function for zaptel, since this is a very usefull feature, or if I should make a new patch myself.
Kind Regards
Jon Leren Sch?pzinsky |
|
| Back to top |
|
 |
stotaro at totarotechn...
Guest
|
| Posted: Wed Feb 27, 2008 8:50 am Post subject: [asterisk-users] Zap Call deflection on PRI |
|
|
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.
Thanks,
Steve Totaro
On Wed, Feb 27, 2008 at 4:38 AM, Jon Sch?pzinsky <jos at detele.dk> wrote:
| Quote: | Hello List.
I have created a patch some time ago, to use the ISDN feature "call deflection" or partial rerouting, as it Is also known, to make proper call transfers on PRI, without using an extra channel for the outgoing call.
Back then I ported the function zapCD from bristuff, to a normal zaptel, and it worked as it should.
I am looking at this again, and was wondering if anybody has made a similar function for zaptel, since this is a very usefull feature, or if I should make a new patch myself.
Kind Regards
Jon Leren Sch?pzinsky
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
|
|
|
| Back to top |
|
|
jsmith at digium.com
Guest
|
| Posted: Wed Feb 27, 2008 9:42 am Post subject: [asterisk-users] Zap Call deflection on PRI |
|
|
On Wed, 2008-02-27 at 08:50 -0500, Steve Totaro wrote:
| Quote: | 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. |
|
| Back to top |
|
|
jos at detele.dk
Guest
|
| Posted: Wed Feb 27, 2008 10:03 am Post subject: [asterisk-users] Zap Call deflection on PRI |
|
|
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:
| Quote: | 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.
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
stotaro at totarotechn...
Guest
|
| Posted: Wed Feb 27, 2008 10:19 am Post subject: [asterisk-users] Zap Call deflection on PRI |
|
|
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:
| Quote: | 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:
| Quote: | 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.
|
|
|
| Back to top |
|
|
jos at detele.dk
Guest
|
| Posted: Wed Feb 27, 2008 10:49 am Post subject: [asterisk-users] Zap Call deflection on PRI |
|
|
Do you mean individual B-channels?
That could be done in dialplan, with the ZapCD command... When its done that is 
Jon
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve Totaro
Sent: 27. februar 2008 16:19
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Zap Call deflection on PRI
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:
| Quote: | 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:
| Quote: | 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.
|
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
