Alcatel Unleashed

Hi.

Our incoming calls go through an Alcatel 4400 PBX and are passed through a PRI euroisdn link to Asterisk where a group of SIP extensions take the calls. The operators then have the possibility of transfering the calls to some extensions within the Alcatel system. Currently, two PRI channels are used when a transfer has been performed (as expected).

Is there a way to do something similar to Flash/Hook but on a PRI? This way, bridging would be avoided and no PRI channels would be used after the transfer.

Asterisk supports flash on analog circuits but is there something for PRI?

You can't use hook flash on digital links - this is an "feature" for analog lines.

I have implemented such an bridging in chan_capi (current trunk version).
It will do automatically the path replacement, if asterisk tells chan_capi, to do bridging.

You will need an QSIG-GF trunk (instead of Euro-ISDN) and an Eicon DIVA PRI card in your asterisk.

Which type of PRI card are you using at the moment?

Mario

mgoegel wrote: Which type of PRI card are you using at the moment?

I'm using a cheap Digium TE120P.

So (IMHO) this card has to use libpri.
In the latest cvs there should be support for path replacement, but this was developed for an avaya pbx, i don't know if it is compatible with alcatels QSIG implementation.

Mario

mgoegel wrote:So (IMHO) this card has to use libpri.
In the latest cvs there should be support for path replacement, but this was developed for an avaya pbx, i don't know if it is compatible with alcatels QSIG implementation.

Mario

hello,
has anyone tried this libpri patch with an Alcatel OXE ?
regards

yes.

but only on clones of Digium cards, clones named te400p, te110p (4 ports E1/T1, 1 port T1/E1), and without no luck.

btw. qsig pathreplacement is sth diffrent than 2bct

in the cvs version there is real PR implemented.
Maybe you have to switch the OXE from ETSI to ISO mode...

Mario

I actually had something like this working a couple of years ago with asterisk on a PRI, but can't remember how I did it! I am also pretty sure that the feature is commonly enabled on US PRIs. It required no reconfig on the telco side.

I'm pretty sure it was related to "dial command options" like [t] and [T].

Ultimately it was no big deal.

Wyatt
whendricks@avtechmed.com

The following is off of an Avaya site:

Explicit Network Call Transfer over ISDN PRI Trunks
This feature allows incoming and outgoing calls using the Primary Rate Interface over T1 to be connected together under directions from Interactive Response, but without requiring a call bridge through the software. The net result is that IR applications connecting incoming and outgoing calls can handle more call traffic, since it is attached to calling and called parties only briefly, rather than for the duration of the call. This feature will make PRI connections to Interactive Response more attractive, for now, ANI, DNIS and transfer will all be possible via the same connection. (Previously, applications requiring transfer had to use analog, line-side T1 or bridge the call through the IVR for the duration of the call.)

To use this Interactive Response feature, the customer must first subscribe to one of the following network call transfer operations:

* TBCT. A feature running on a National ISDN (NI) network provided by both Nortel and Lucent. The TBCT feature is provided to Avaya Interactive Response by a Nortel DMS 100 or a Lucent 5ESS switch.
* RLT. A proprietary version of TBCT on a Nortel proprietary PRI (NTNA). The RLT feature is provided to Avaya Interactive Response only by the Nortel DMS100 switch.

With the Avaya Interactive Response TBCT feature, a call coming into the Avaya Interactive Response on one B (bearer) channel can be connected, within the switch, to a call that has been made by the Avaya Interactive Response on another B channel, and both incoming and outgoing calls on the Avaya Interactive Response are released. Without this feature, the connection would need to be maintained within the Avaya Interactive Response for the duration of the call. Instead, just as the Avaya Interactive Response hands off calls locally to a PBX, it can hand off this call as soon as possible. The result is that fewer resources are tied up and the Avaya Interactive Response can handle more transactions.

What OXE Release?
What mode ISO/ETSI or ANSI?
what kind of trunks (PRA access on E1 in Europe or PRI with T1 in US/North America)?
what Telco switch (if you do know your telco switch) ?