Trunk replacement for Nortel PBX 1

[srmega41]

I am looking at options to migrate to VoIP for inter-office communications only! We are not interested in IP to the desktop at this time, and I really don't want to replace the 80 Option 11's and the 81C already installed. All of these systems are running on Succession 3.0 or 4.0. Here is my question:

Does anyone know if Q.sig works to provide path replacement on COT trunks? I know TAT and TRO-CM work on station calls and DID's, but it DOES NOT work on COT's!!

One option presented to me is convert all of my COT's (approximatly 500 across all 80 locations) to DID's, then use the H.323 trunks in Succession 3.0/4.0 with the gateway/gatekeeper to get the calls out on the WAN. This is similar to the ITG solution we tried three years ago, but much more elegant.

Another option is to use a Mitel 3340 for Trunk replacement and connect the Nortel using a Q.sig T1 into the Mitel box, then out to the WAN. The issue here could still be that answer supervision on the original COT trunks would not allow Call Modification or Call Redirection to tear down unnecessary call paths.

Turning answer supervision off does NOT change the handling of the call in the Nortel PBX. Nortel has told me directly TAT and TRO-CM will not work on COT's.

Any info on the Q.sig piece or other feedback would be helpful.

Scott M.

 

[Pudge99]

I'm trying to figure out your distinction between public and private trunking here? Are simple tie trunks an option? They would support TAT and TRO.

 

[srmega41]

You are correct in the TIE trunks scenario. The issue here is where the call originated.

If a customer calls a location using the main number (COT's into PBX A) and is then transferred to an employee at PBX B, the system(s) keeps track of where and how the call entered into the network. Now let's assume the employee at PBX B is at lunch, and the call redirects back to PBX A, where voicemail resides.

Because the call into PBX A was on a COT, the multiple call paths between PBX A and PBX B stay in place (I have tested this several ways and had it verified by Nortel it is working the way it is supposed to).

If this call scenario entered PBX A using DID trunks instead of COT's, TAT, TRO-BA and TRO-CM remove the redundant call paths.

I have a large number of locations that have call scenarios just like this with the COT's into the PBX's.

I hope this helps explain the scenario a little better. I was hoping not to overload the forum with to much detail, but I guess the devil is in the details.

Thanks for asking the question.

Scott M.

 

[johnpoole]

the basic 3 and 4 package both support all the flavors of qsig.. if your just looking at voip to the network, itg trunk cards work. care should be taken as far as

john poole
bellsouth business
columbia,sc

 

[srmega41]

I know that the ITG cards will work, as long as the call scenarios we have in place do not include COT's.

I guess my understanding at this point is that Q.sig will NOT overcome the call modification limits placed on COT's?? Or no one can speak to that specifically??

I did a trial using ITG 2.0 three years ago and found the call modification issues then. Since that time, NORTEL has admitted to me it was an issue on the 25.40 software release. Succession 3.0 included the TRO-CM feature to fix the call modification problem in call transfers and conference calls, but only in station-to-station and DID originated calls.

Now they tell me TRO-CM does not and will not work on COT's. I just need to know if the Q.sig features of call redirection and call modification will actually work on COT's.

Still searching,

Scott M.