Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trunk to trunk conference-transfer

Status
Not open for further replies.

Lynx77

Technical User
Oct 9, 2007
163
LB
Hi All,

Below is a triky scanario concerning trunk to trunk connections and I want to check if the following request can be applied:

1 - Telephone set must be able to make conference calls between 2 CO lines and between a CO line and a TIE trunk.
2 - Telephone set msut be able to transfer calls between 2 CO lines and between a CO line and a TIE trunk.

Option 1 and 2 can be applied by FTOP = FTLY and CLS FFTU.

However, we want to disconnect the trunks if telephone set A hangs up while a conference is established (Unsupervised conference). This can be done by CLS FTTC. Unless FTTC will not allow trunk to trunk transfer.

As per the books, this is a normal operation. Unsupervised conference and transfer can be allowed or denied together by CLS FTTU or FTTC.

Anyone has been able to deny unsupervised conference and at the same time keep the trunk to trunk transfer operational?

Thanks.
 
Since TRN and AO3/6 work the same from a restriction standpoint, you are gonna be stuck if you want to have trunks "disconnect upon releasing a Conference" but allow "Transfer to maintain the trunk connections"

I don't know of any restriction that could apply.

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too
 
2 - Telephone set msut be able to transfer calls between 2 CO lines and between a CO line and a TIE trunk."

This worries me as in APAC if transfer 2 x COT together you get lockups. To overcome this, you need some sort of carrier supervision (reversal on idle ?) or to use the TFD timer in LD 16.
 
Hi Again,

GHTROUT
What you said is correct but I just wanted to be sure of my conclusions. This is what is mentioned in teh NTPs.
Thanks a lot - As always you have answers.

DFKSydney
This is correct. We use supervised COT trunk NTCK16 boards which supports disconnect supervision based on busy tine id BTID. But this not our problem. The issue is to disconnect the extrenal users when teh PABX user releases the conferecence and at the same time kepp the trunk to trunk transfer working. Accordin to the NTPs, this is not possible.I just wanted to check if anyone has been able to overcome it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top