| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: err5525, error |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 4 ![]() | Error ERR5525 I am continuously getting the following error On a 61C. Is there anyway correct this or to disable the error? ERR5525 TN: 00001508 N: 00000007 P: 00000000 L: 00000002 DTA: 82000000 ERR5525 Parsing of name information received. Severity: Info | ||||||||
| | |
| | #8 (permalink) | ||||||||
| Senior Member ![]() Ramjet is wore ass out from the holidays!
Rep Power: 8 ![]() | The problem is in the Meta Switch. I have an OP 11 behind a Santera 1 softswitch and after they did a software upgrade I started seeing the same error code. Santera wrote a patch for the CO in question and the error went away. __________________ Two snips, a snort, a turn, a fly, and a grunt, and it was so simple, like the jitterbug, it plum evaded me! | ||||||||
| | |
| | #9 (permalink) | ||||||||
| Junior Member ![]()
Location: Jonesboro AR Rep Power: 6 ![]() | I work with Ramjet and remember this particular issue. As I recall it had to do with our switch sending a Facility message containing the calling name data. We were specifying a digit length of X digits and the Nortel was expecting a length of Y digits. I don't remember the exact length of the fields. Normally, a CO will send the incoming setup message to the PBX and specify that an additional facility message is to follow containing the Calling Name Information Element or IE. The originating switch specifies the length of the Calling Name IE as 15 digits persay, which is the norm. In our scenario, the SanteraOne/Tekelec T-9000/Genband G9 was specifying a CNAM length of 13 digits and the Nortel Op11 was expecting the length to be 15. Therefore it generated an error on every incoming call that involved CNAM delivery. One option might be to see if your provider offers delivery of the CNAM IE in the call setup message versus the facility message. I know that most Nortels will handle either. Outside of that I would recommend contacting Nortel support to obtain a Layer 3 trace of the PRI signaling as this error is occuring. Once you hand that trace off to Metaswitch, they should have no problems correctly identifying the source of the error and consequently offering a solution. | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |