Trunk Anti-Tromboning

[Pudge99]

Trying to set up Trunk Anti-Tromboning between an Option81C Rls.3.0 and an Option11C Rls.3.0. Replaced the DCHI card at the Option11C end with a proper MSDL card and verified MSDL at the Option 81C end.
Set TRO and TRMB to yes in the RDB; TAT in the RCAP of the appropriate D-Channels of both switches.
But when I trace a call on the TIE route; still using 2 TIE trunks? Thoughts?

 

[johnpoole]

do you have the same pni on both ends.. not only in the route but also both cdb's.. of course both ends have to be internal as opposed to extrernal routes

john poole
bellsouth business
columbia,sc

 

[Pudge99]

Double checked both the RDB's PNI-00001 and the CDB's PNI-1 on both switches.
Is there a TRAC prompt or something similar, that would say if the anti-tromboning is activated?

 

[telecomnorth]

How is the call routing back to the source PBX? Xfer? FNA? Call forward all calls? And how is that DN programmed in the redirecting PBX?

If not present add MSDL in the RCAP of each D-channel. Check NTP as correct responce might be MSL, MSL...??? Stands for the far end D-Channel is supported by a MSDL card. Remember to download new profile (LD 96) when changing programming on a MSDL card.

 

[Pudge99]

telecomnorth,

Yes, MSDL is present on both ends of the RCAP prompt.

The call originates on a DID trunk (11C), ACD NCFW's to a networked call pilot menu (81C) via TIE trunk, then back to an ACD Que (original 11C), using the same TIE route.

Thanks,

 

[johnpoole]

did you confirm the pni in both cdb's?

john poole
bellsouth business
columbia,sc

 

[Pudge99]

YUP! PNI-1 in the CDB on both switches.

 

[telecomnorth]

Seems like all the configuration items are covered. A few thoughts:

- In your call routing example is CallPilot transfering to a number within the 81C that is routed back to the 11C via NARS/BARS such as a CDP steering code? From my experiance TAT and TRO require that the call be routed via a CDP,LOC, or other NARS/BARS item and not route via a trunk route access code.

- Test other types of calls between the two PBXs. Phone to phone using call transfer to route call back to the source PBX, then call forward all calls...,.... Just a way of gathering clues.

 

[johnpoole]

that's a good point.. you need full intergration in both directions.. in your case you have to dial the actual dn from the station at both sites..

john poole
bellsouth business
columbia,sc

 

[Pudge99]

The calls are routed via CDP and work fine, but when I TRAC a call at the Call Pilot end (81C), I have 2 TIE trunks from the same route being used, with the source and destination DN's being correct. Works fine but the route is being congested (all trunks busy) and getting busy complaints.
Will try your suggestion using phone to phone instead of the mail and see how this affects the anti-tromboning.
Thanks Guys!

 

[informidicate]

Could you post The RDB's of both routes.

 

[Pudge99]

Received a tip to turn on D-Channel messaging to verify the TAT and TRO and sure enough it is working properly!
Here is the caveat: When the menu selection is made from Call Pilot (81C), the call routes via TIE back to the an ACD Que (11C). If an agent is available and the call is answered, both TIE trunks drop (TAT and TRO). However, if the call waits in Que and receives RAN treatment, the TIE trunks between the two switches stay nailed up.
I guess this is the way it supposed to work.
Thanks again everyone for your feedback!