CUCM IP trunk to two HiPath 4000 2

[veilside]

Hello,.

I have two Hipath 4000 and CUCM linked all to each other like CUCM > PBX1 > PBX2

CUCM can reach extensions on PBX 1 but cannot reach PBX 2 when PBX1 can call PBX2 with no problem. I have checked LDAT on both PBX and I cannot find the problem why the PBX1 cannot forward the incoming calls to PBX2

 

[Iamnothere]

No one can provide a 100% accurate answer until you provide more details regarding the dialing pattern(s). From the CUCM, what is being dialed to reach PBX1? Is that same pattern used to dial from PBX1 to PBX2?
For example: is the user dialing 8+four-digit station number @ all sites?

 

[veilside]

Hi Iamnothere,

The extensions on all is like below;

CUCM: 7XXX

PBX1: 1XX , 2XX , 3XX , 4XX

PBX2: 5XX , 6XX


LDPLN and LROUTE configured like below;


on CUCM: 1XX , 2XX , 3XX , 4XX , 5XX , 6XX >> SIP Trunk to PBX1 ( Working OUT & IN )

on PBX1: 7XXX >> to CUCM 5XX, 6XX IP trunking to PBX2 ( Working OUT & IN)

on PBX2: 1XX , 2XX , 3XX , 4XX IP Trunking to PBX 1 ( Working IN & OUT ) and I configured LDPLN 7XXX to be routed to PBX1 and this one is not working

 

[Iamnothere]

So the problem occurs only when dialing from PBX2 to Cisco via PBX1, correct?
Question back to you: if this is IP Trunking via STMI (on 4K), why are the calls from PBX2 to Cisco tandeming thru PBX1 instead of being routed directly to the IP Address of the Cisco Gateway?

In PBX2 you have LDPLN dial pattern entries 1XX, 2XX, 3XX, 4XX routed to PBX1. In this route's LDAT config, the Out-Dial Rule should be "ECHO 1","END", since the LDPLN pattern contains only 1 field.
Also in PBX2, you have LDPLN pattern 7XXX. Based on your previous post, did you break up this pattern into "7-XXX", or combine it as "7XXX"? If the dial pattern is configured in LDPLN as "7-XXX", and the Cisco system needs to see all 4 digits, then your Out-Dial Rule for this pattern would be "ECHO 1","ECHO 2","END". But if the LDPLN pattern is "7XXX", the Out-Dial Rule should be "ECHO 1","END";

But the Out-Dial Rule may not be the problem. I suspect that since you added the Cisco dialing scheme yourself, you may have missed one critical trunking parameter that is usually relevant only in TANDEM scenarios: LCOSV. When a call from PBX2 sends the digits to PBX1 which are intended to be routed to the Cisco system, PBX1 must re-process the call, as if dialed by a "user" in PBX1. In a trunk tandem scenario, this "user" is the trunk itself. Therefore the "LCOSV" assigned to the PBX1 trunk circuit must be capable of placing the call to the Cisco system. Since you said that users/subscribers in PBX1 can dial the Cisco switch, DISPLAY one PBX1 station that CAN successfully place a call to the Cisco system, and note its LCOSV1 and LCOSV2 values (1 = DAY time, 2 = NIGHT time). Now DIS-TDCSU for the IP Trunk in PBX1, and verify that the trunk circuit uses the same LCOSV value as the station's LCOSV1 value. If not, then perform CHA-TDCSU and change parameter "LCOSV". Then re-test your call.

It could also be an LCR Authorization problem, but I am betting on LCOSV. Both the LCR Authorization and LCOSV are configured in AMO COSSU.

Good Luck. I AM NOT supposed to be HERE.

 

[veilside]

Many Thanks for your reply, It's worked now I can reach Call manager from PBX2 via PBX 1 but there is another strange problem as I cannot reach PBX2 from call manager via PBX1.

 

[Iamnothere]

If your PBX1 <-> PBX2 "point-to-point" IP trunking circuit is working properly, in a perfect world the addition of the Cisco system would result in changing this entire scenario to a "point-to-multiPoint" - since each individual system ("point") should be able to use the same IP Trunking circuit to dial the TWO other systems ("multiPoint"). But this change would involve a major config change involving the Large Enterprise GateKeeper. It appears that dialing via this IP trunk circuit is now based on a linear topology, where some calls from system A must route through system B to reach the ultimate destination: system C. My first guess regarding this new problem is again either LCOSV or a LCR Authorization problem, but I must assume that you have already verified that the PBX1 and PBX2 trunk circuits' "LCOSV" parameters are set high enough to support dialing (as explained in my previous post).
Is everything working except for this one particular type of call? When the call fails, what tone do you hear? AND, what does your phone's display indicate? (NOT POSSIBLE, PLEASE TRY LATER, etc)
Have you tried using RDS (Realtime Diagnosis System/Server)? Perhaps someone else can post, as I am not available to elaborate. Good Luck!

 

[sbcsu]

Each HiPath needs to know the Node Number of each system including the Cisco.
Each node number must be reachable by a route even if it is not directly connected to that node.