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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2 B-Channel Transfer (TBCT) on Mitel 3300 Rel 9.0 - NI-2

Status
Not open for further replies.

kwbMitel

Technical User
Oct 11, 2005
11,505
CA
2 B-Channel Transfer (TBCT) on Mitel 3300 Rel 9.0 - NI-2

North America only

Has anyone implemented TBCT in North America?

The programming only says to enable the COS option

I have verified that the Central Office has the option enabled.

The transfer is not taking place.

Can anyone give me any insights?


**********************************************
What's most important is that you realise ... There is no spoon.
 
There is only 1 COS option associated with this function and I have enabled it for all devices and trunks.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Didn't think that was available on Release 9. That doesn't answer your question though. No never done it but have a customer interested so I am interested in the answer to your question. Since its release 9 is your trunking via NSU or embedded? From what I understand its as you say only a COS option if the CO has the feature enabled.

One final thought if the CO has it enabled does the customer have to pay for the extra feature and if so is your customer? Would be surprised if the carrier gave the feature for free.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
The feature has a one time activation fee in our area for the CO.

TBCT Was added to the 3300 in rel 7

I am using embedded PRI

**********************************************
What's most important is that you realise ... There is no spoon.
 
What type of CO?

TBCT is only supported for Bellcore and 5ESS variants of the NI-2 protocol for the embedded ISDN offerings of the 3300 ICP. It is not supported on the NSU

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Looks like you have it setup correctly. Only needs a COS option in the transferring device.



I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
The switch is a DMS. (Bellcore)

Unfortunately the customer is off SWA with Mitel so I can't go that route.

Looks like I'll have to find time to set up my lab system.

**********************************************
What's most important is that you realise ... There is no spoon.
 
So are you set to use the NI-2 protocol?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Yes, NI-2

**********************************************
What's most important is that you realise ... There is no spoon.
 
Don't think the SWA tied to product support is in place yet so that is still an option. Pretty sure release 9 still supported.


Would CCS trace shed any light?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Yes, SWA is important from where I call from (Canada)

CCS - Don't think so.

I've now tried with another system in another city - Same issue.

Looks like I'll have to set up my lab system.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Update:

Lab system was OK. Worked like a charm.

By this time the customer was updated with SWA and I opened a ticket with Mitel.

2 weeks of pointing fingers led us to a DPAR by Mitel where the issue was fixed in SW load 9.0.3.16.

My load was 9.0.3.15.

MN00300083 - TBCT fails to transfer the call with call reference of 0xd004
REPORTED IN SW LOAD - 9.0.2.18
SYMPTOMS
During 2 B call transfer ( TBCT), 3300 sends the same call reference ID of 0xd004, which is different from the call reference of the first call setup.

WORKAROUND = This is patched in 9.0.3.16 and is officially fixed in 10.0 UR1

**********************************************
What's most important is that you realise ... There is no spoon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top