CFW to DSC over IP Trunks fails

[yyrkroon]

I'm tring to CFW to a DSC over H.323 Trunks and its failing with the following errors.

DCH 5 IMSG DISC REF 00000197 CH 61 0 0 22 TOD 12:58:40
CAUSE :NO CHANNEL/CIRC AVAIL

The incomming number is a DID that's CFW 4 DSC.

If I dial the DSC, the call completes just fine.

The call flow is as follow: DID Trunk->setA->CFW 4 DSC.

Anyone experience this or ran into this before?

Thanks in advance.
p.s. - deplist installed as of 3/28 on CallServer, SigServer and VGMC.

 

[johnpoole]

might not have to do with the fact that it's ip at all. can you forward to another tdm route. check to see if that trunk has the same ncos and tgar as the ip..

john poole
bellsouth business
columbia,sc

 

[yyrkroon]

John,

Yes I can go DID->setA->CFW 16 91NPA...over COT.

The incomming DID trunks NCOS are 2, there's no TARG on any routes and my FRL on the RLI is 0 for the IP trunks.

 

[johnpoole]

might not have to do with the fact that it's ip at all. can you forward to another tdm route. check to see if that trunk has the same ncos and tgar as the ip..

john poole
bellsouth business
columbia,sc

 

[yyrkroon]

Both my DID and COT routes are TDM, there are no TIEs between site so I can't use DSC from TDM to TDM.

I can CFW external utilizing the DID and COT routes.

Thanks

 

[johnpoole]

are the ncos and trags the same on each of the two trunks your trying to go out on.. look at them on the tdm (did or cot) that you can cfxa .. tgar to targ can't match, nocs should for that call. other then that nothing else should block. try a did station forward to the remote station across the ip.. we need to find the point of failure, it's not an impossible call, and your not the 1st tech to do it. i can't set up test on this site, we don't use ip trunks. i perfer pri back to the cisco router, then they can ip to each other.. that forward is as a normal tdm to tdm, even though the station is voip wireless or soft

john poole
bellsouth business
columbia,sc

 

[yyrkroon]

an FYI for all that might encounter this problem.

The fix is to install MPLR18404 in all of the SigServer in the network.

Thanks John for your assistance

 

[johnpoole]

thanks for the patch, might need it in the future

john poole
bellsouth business
columbia,sc