atcomsystems.ca/forum Forums Wiring - Telecom Carriers - Trunks & Services Telecom Service & Providers CO switch transfer - urgent

Hi, our popular CLEC told us that a service they offer called 2-B channel transfer would let us receive a call on PRI into our PBX, flash their CO switch, dtmf an external number, flash, disconnect. The CO transfers the call to the external number after the call is released from our PBX.

Therefore we could front-end calls for another destination without using up two trunks on PRI's.

Now that we have a proposal into a client to do just this the CLEC tells us that this is false, 2-B channel only works between trunks in the same trunk group, not to external phone #'s.

Is there any product generally offered by a CLEC over PRI that does a transfer in the CO switch such that customer doesn't use up multiple trunks?

What service would one purchase to take calls, transfer elsewhere, and not use two trunks?

I learned recently that you can't do this with a PRI.
Centrex with POTS lines or T-1 Centrex will work depending on the CO Switch. I had a similar application. The common question I got was " what's the problem using 2 channels from the PRI"? There is no loop loss.
Mark

I am in agreement with MarkK here. Our resident CO gurus may want to kick in, but so far, the Lucent 5ESS does not offer this capability. If your CLEC is using a Nortel DMS switch, they might have another way to make this happen.

Do you have an area code and exchange for this customer availble (NXX-NXX)? We can at least take a stab at finding out what CO switch is being used so that you are headed in a better direction.

This sounds like a job for AnthonyH or Dexman. If they don't chime in soon, send them a PM.

Thanks Ed, Anthonyh, I couldn't remember who you got to help me out on this one, he's the man.
I'm out of brain cells. My dad would say "it's no disgrace to get old, just damn inconvenient".
Mark

Ed just about covered it

2 B-Channel transfer is a 5ESS supported feature on ISDN PRI. The feature allows the customer pbx to request the CO to replace the talk path of a given call so that the call doesn't tie up 2 channels on the PRI (in fact it releases both channels).

refer to Telecordia document GR-2865 for details

Pete, this i done on a PRI with dids, not with BRI's? It may just not be something we offer, I ahve never come across it...thanks for the document info I will try to pull it

Correct, GR-2865 refers to ISDN PRI, Basic Rate circuits have a similar feature covered under GR-858.

23.5.6 Feature Operation
Initially there are at least two calls over the PRI between end-users and the controller. Each call uses a B-channel on the PRI. To be eligible for TBCT transfer, at least one of the calls must be in an answered state; it may have been initiated by the end-user or by the controller. The other call may be in an answered state, or, if initiated by the controller, it may be in a ringing state.
If the controller determines that two of the calls are to be transferred to each other, the controller sends a request for two B-channel transfer to the 5ESS® switch.
When the 5ESS® switch receives the request from the controller, it checks the validity of the message containing the request, the states of the calls to be transferred, the compatibility of the bearer capabilities of the calls, whether the PRI groups associated with the B-channels in the request are provisioned for the feature, whether the PRI groups are members of the same PRI serving group (see below for explanation of PRI serving group), whether interactions with other services or features should prohibit execution of the transfer, and other criteria. If any of the checks fail, an error message is sent to the controller, and the calls remain connected to the controller. If the checks pass, the 5ESS® switch performs the TBCT transfer operations. The two users' calls are then connected together at the switch, and the two B-channels, which were previously occupied on the PRI by the users' calls to the controller, are released. After the transfer, the two B-channels are available for new calls to the controller.
The multiple interface capability allows transfers between B-channels that are on different PRI groups, that is, B-channels that are associated with different D-channels. A PRI serving group is introduced with this feature. A PRI serving group consists of members, each of which is a PRI group. All members of a PRI serving group must be on the same SM.
This feature also provides two counters that are available to control requests and usage of the feature on a per PRI group basis. If the two B-channels are from different PRI groups, one counter is incremented -- that of the PRI group with the B-channel that requests the transfer. One counter records the number of TBCT requests per 10-second interval. If the number of TBCT requests reaches a provisionable limit within the time interval, all additional requests are denied in the current time interval. The second counter records the number of active transfers, that is, the number of transferred calls that are currently active. If the number of active transfers reaches a provisionable limit, all subsequent TBCT requests are denied. (It is also possible for the number of active transfers to exceed the limit, for example if the limit is lowered while there are active transfers on the interface.) When a sufficient number of transferred calls are cleared, such that the number of active transfers no longer equals or exceeds the limit, new TBCT requests will be allowed. An audit is provided to ensure the integrity of the active transfers counter.
Traffic measurements are provided to record feature usage on a requesting PRI group basis. The number of valid TBCT requests, the number of successful TBCT transfers, the number of overflows of the active transfers counter, and the number of overflows of the transfer requests per current interval counter are measured.
As an enhancement to Feature 99-5E-3261 (Two B-Channel Transfer [TBCT] on PRI), the TBCT Notification to Controller feature, 99-5E-7268, sends notification to the controller when the transferred call is cleared. A non-call associated NOTIFY message is used. When the Notification to Controller feature is active, the switch assigns a Call Tag to the TBCT call at the time of the transfer. This Call Tag is unique at the PRI interface serving the controller. If the multiple PRI option is subscribed, the Call Tag is unique across the PRI serving group. The switch retains an association between the Call Tag, the transferred call, and the controller's interface throughout the duration of the transferred call.
The base TBCT feature, 99-5E-3621, passed the number of active and available transfers to the controller in the DISCONNECT message at the time of the transfer. When the TBCT NTC feature, 99-5E-7268, is active on the PRI group, the DISCONNECT message will also include the Call Tag assigned to the transferred call. The switch sends a NOTIFY message to the controller, when the TBCT transferred call clears. The NOTIFY message contains two notifications. One notification contains the Call Tag value to alert the controller that the TBCT call associated with the Call Tag has cleared and a second notification provides the updated number of active and available transfers on that PRI group.
The Notification to Controller feature is provided on a per PRI GROUP basis.
NOTE: Notification to Controller can be subscribed only if TBCT is active.

sorry for the messy post above, it didn't copy and paste well from the 5ESS manual (I have an older 'DynaText' copy of the manual) but it does a pretty thorough job of explaining the feature from a Lucent 5E perspective