Hi Guys,
I am sorry if my issue is not related to this but I think it is.
I have a PRI with Bell Canada and when I dial in and have the call
transfered to a context to dial out and then have those two channels
bridged, the call disconnects with cause 16 just exactly as Jay R. Ashworth
shows in
Problem resolved with setting transfer=no in zapata.conf.
On Mon, Apr 12, 2010 at 9:14 PM, bruce bruce bruceb...@gmail.com wrote:
Hi Guys,
I am sorry if my issue is not related to this but I think it is.
I have a PRI with Bell Canada and when I dial in and have the call
transfered to a
Jay R. Ashworth wrote:
On Mon, Sep 08, 2008 at 11:28:13AM -0500, Matthew Fredrickson wrote:
For DMS100's version of TBCT, called RLT, one leg *must* be inbound and
the other *must* be outbound. No other combination is going to work.
This is explicitly mentioned in the protocol in RLT.
Ok.
On Fri, Sep 12, 2008 at 10:56:40AM -0500, Matthew Fredrickson wrote:
Will I actually need to do PRI debug on that span to tell?
Or will seeing hangup messages while I'm still talking be the solution?
Seeing hangup messages on the console while the audio path remains
indicates success
Jay R. Ashworth wrote:
On Fri, Sep 12, 2008 at 10:56:40AM -0500, Matthew Fredrickson wrote:
Will I actually need to do PRI debug on that span to tell?
Or will seeing hangup messages while I'm still talking be the solution?
Seeing hangup messages on the console while the audio path remains
On Fri, Sep 12, 2008 at 12:12:56PM -0500, Matthew Fredrickson wrote:
Can *you* confirm, off hand, that 1.2 would do TBCT at *all*? Someone on
IRC thinks it wouldn't.
It will only attempt it for DMS100 switchtype. You must have 1.4 libpri
for any other switchtype.
Will libpri 1.4 work
On Mon, Sep 08, 2008 at 11:28:13AM -0500, Matthew Fredrickson wrote:
For DMS100's version of TBCT, called RLT, one leg *must* be inbound and
the other *must* be outbound. No other combination is going to work.
This is explicitly mentioned in the protocol in RLT.
Ok.
Just found
On Thu, Sep 11, 2008 at 12:41:12PM -0400, Jay R. Ashworth wrote:
Will I actually need to do PRI debug on that span to tell?
I did a pri debug to a file, I can see the call go, I see no indication
that it actually tried to generate a TBCT/RLT request.
Cheers,
-- jra
--
Jay R. Ashworth
On Fri, Aug 15, 2008 at 03:03:23PM -0500, Matthew Fredrickson wrote:
Let me clarify some of this.
Under no circumstances can Asterisk receive a TBCT request. We just
ignore them. We can initiate them however.
There are different TBCT implementations, dependent on which switch type
is
Jay R. Ashworth wrote:
On Fri, Aug 15, 2008 at 03:03:23PM -0500, Matthew Fredrickson wrote:
Let me clarify some of this.
Under no circumstances can Asterisk receive a TBCT request. We just
ignore them. We can initiate them however.
There are different TBCT implementations, dependent on
Jay R. Ashworth wrote:
I'll assume you've watched it on a PRI, so I'll defer, but I wouldn't
expect that myself; I would expect that when you tell the switch to
transfer it, you go immediately from one B channel to 0.
You should expect that; in fact, that's what the 'TB' in 'TBCT' stands
On Tue, Aug 19, 2008 at 07:35:03AM -0500, Kevin P. Fleming wrote:
Jay R. Ashworth wrote:
I'll assume you've watched it on a PRI, so I'll defer, but I wouldn't
expect that myself; I would expect that when you tell the switch to
transfer it, you go immediately from one B channel to 0.
You
You should expect that; in fact, that's what the 'TB' in 'TBCT' stands
for... for a time, there are two B-channels involved. TBCT is a method
of taking two existing already connected B-channels and linking them
together into the network, it is not a 'transfer' facility where you
provide a
On Sat, Aug 16, 2008 at 09:35:10PM -0400, Ron Joffe wrote:
On Saturday 16 August 2008 14:37, Jay R. Ashworth wrote:
TBCT is a feature of LEC/IXC edge switches; there isn't much use for it
in any other context. I don't care if you're using Asterisk to be an
edge switch, but it's a *carrier*
On Fri, Aug 15, 2008 at 11:56:30PM -0500, Tilghman Lesher wrote:
There's no hairpin involved: the point of TBCT is that you tie up *0*
timeslots instead of 2, to forward a call.
There is a hairpin involved. The call (for several milliseconds at least) is
using two channels on the PRI
On Saturday 16 August 2008 14:37, Jay R. Ashworth wrote:
TBCT is a feature of LEC/IXC edge switches; there isn't much use for it
in any other context. I don't care if you're using Asterisk to be an
edge switch, but it's a *carrier* feature, by and large.
Certainly in the specific instance
I may have to do some work with TBCT, and probably cross-carrier TBCT,
here shortly, and I haven't ever worked with it. If anyone on the list
ever has, I'd be interested to know:
1) Only the carrier first involved with the call has to
actually be provisioned for it, correct?
: [asterisk-users] PRI TBCT - Practical Experience, Anybody?
I may have to do some work with TBCT, and probably cross-carrier TBCT,
here shortly, and I haven't ever worked with it. If anyone on the list
ever has, I'd be interested to know:
1) Only the carrier first involved with the call has
On 8/15/08, Don Kelly [EMAIL PROTECTED] wrote:
1. The carrier you are connected to must be licensed for it and have the
necessary software, if the carrier requires, your circuit(s) must be
provisioned for it. The originating/destination carriers shouldn't matter.
Most carrier sales people
On Fri, Aug 15, 2008 at 02:37:46PM -0400, Matt Florell wrote:
Most carrier sales people don't know what TBCT is unfortunately, and
even if a carrier is capable of doing it, it is a possiblity that not
all of their equipment is capable of doing it. One client of mine
tried to get TBCT working
On Friday 15 August 2008 13:45:11 Jay R. Ashworth wrote:
On Fri, Aug 15, 2008 at 02:37:46PM -0400, Matt Florell wrote:
Most carrier sales people don't know what TBCT is unfortunately, and
even if a carrier is capable of doing it, it is a possiblity that not
all of their equipment is capable
Tilghman Lesher wrote:
On Friday 15 August 2008 13:45:11 Jay R. Ashworth wrote:
On Fri, Aug 15, 2008 at 02:37:46PM -0400, Matt Florell wrote:
Most carrier sales people don't know what TBCT is unfortunately, and
even if a carrier is capable of doing it, it is a possiblity that not
all of their
On Fri, Aug 15, 2008 at 02:49:17PM -0500, Tilghman Lesher wrote:
To be more clear, what I'm after is to have *someone else besides me*
place calls out their PRI, and then TBCT those placed calls to my DN.
By the time the calls get to me, they should just be standard phone
calls.
So I
On Fri, Aug 15, 2008 at 03:03:23PM -0500, Matthew Fredrickson wrote:
Under no circumstances can Asterisk receive a TBCT request. We just
ignore them. We can initiate them however.
There are different TBCT implementations, dependent on which switch type
is used, with different
On Friday 15 August 2008 22:16:34 Jay R. Ashworth wrote:
On Fri, Aug 15, 2008 at 02:49:17PM -0500, Tilghman Lesher wrote:
To be more clear, what I'm after is to have *someone else besides me*
place calls out their PRI, and then TBCT those placed calls to my DN.
By the time the calls
25 matches
Mail list logo
