TomasSouth

Did I understand it right that a call to Cisco goes back to the same Nortel?

Was that the scenario? If yes, I could say it is not limitation of Nortel alone, Cisco could be part of it also.

If the link goes on both Nortel systems, I could offer the anti-tromboning.

But since Cisco steps in, I remember my trainor is always hypnotizing us Nortel...Nortel...Nortel...everytime we mention Cisco...

reachdk

The Cisco phone forwards to a different Nortel PBX phone station i.e


Nortel PBX1 Cisco CallManager Nortel PBX2
| | |
| | |
X2000 X6000 X5000

Both the Nortels are connected to a MGCP router via T1 QSIG.

x2000 calls x6000 which is set to forward to x5000

This is basically a test scenario where we are trying to ascertain whether Path Replacement works in the above test case. i.e whether Nortel proposes a Path Replacement and CallManager honors it. What we see is that Nortel does not even send a Path Replacement proposol.

Regards

reachdk

oops - the figure did not come out right - the spaces were truncated
basically x2000 is on 1st Nortel PBX, x6000 on CallManager and x5000 on the 2nd Nortel PBX. The CallManager forwards to a different Nortel PBX

TomasSouth

Oh oh, MGCP? I should get outta here...

mai_roo_jak

Have you configured Nortel by urself ? Checking D-Channel block in LD 22 and see the RCAP. This problem could be the configuration problem on either Nortel or CISCO.

Fletch

Is the Cisco sending the call back to the originating Nortel PBX via the same DCH and Q.Sig link?

If it is not, then path replacement may not happen. Also the DCH on the Nortel must be configured for Diversion and the appropriate Path Replacement Triggers need to be set.