Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ERR 5132

Status
Not open for further replies.

Ski123

Technical User
Mar 21, 2008
239
US
I have a Nortel system that is connected via tie lines to a Cisco Call Manager. As people migrate from the Nortel to the CM I delete their phones and create a CDP of their DID number and point it to the tie line between the two systems. I am geting ERR 5132 codes taht say somthing about the possibility of looping. Is this because the DID numbers that nave been converted to CDP's come in on the DID/DOD trunk group then get routed over to the Nortel/Cisco trunk group? Is there a way to stop the errors? Doesn't ssem to be service affecting at this point but I'm afraid as the numbers of CDP's will be increasing it may cause a problem.
 
I dont know if your situation matches what mine was, but I had to change the route going CDP over to another building to the following:
NCNA YES
NCRD YES
TRO YES

If I change TRO back to NO, then I start getting those 5132's again.
 
As the last Tektips member has stated above, it's the TRO prompt that was causing the problem.

ERR5132
For a tandem CDP DSC call, the incoming route and outgoing route belong to the same Route List Index (RLI). To avoid potential looping problems, the CDP DSC database may need to be modified.
The output data is: customer number, incoming route, outgoing route, outgoing route list index, outpulsed digits.
Severity: Minor

All the best

Firebird Scrambler
Meridian Programmer in the UK

If it's working, then leave it alone!.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top