Guy's/Gal's we are getting ERR008 IPTN Failer (Call Droped) and have rebooted the CSK1 ,Callpilot, SigSer's and nothing has helped a lot of user's are unable to make out bound or receive inbound calls , as soon as the call is answerd the the call drops, any ideas what this might be . Help ! Please
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CSK1 Rls 6.5 (ERR008)
- Thread starter cole06
- Start date
- Thread starter
- #3
Firebird Scrambler
Systems Engineer
I found this out on a release 5.5 switch below. It might help?.
Typical DDI into MGC using 96 port DB out over the TLAN to a Cisco router then on to the IP set
The IP set rings - CSA - Call drops & err008 seen
Description of err008 from NTP's
ERR0008 tn1 tn2 Call drop due to IPTN failure.
TN1 - PTN
TN2 - VTN
Action:
Severity: Major. Critical to Monitor: No. SNMP trap: Yes
The TN's in the ERR008 were the I/C DDI Trk and the 96 port DSP port TN.
Tried another MGC card but that didn't fix.
Tried another 96 port DSP board but that didn't fix.
From a TLAN port on the IP Tele side of the Cisco switch it was possible to Ping the MGC DSP TLAN IP, but you couldn't Ping the actual MGC Board TLAN IP.
We then put the MGC and the IP set into a standalone HUB and you could Ping all TLAN IP's
This showed a problem with the Customers Cisco switch.
Customer then fixed.
The customer said that on the Cisco the MGC Board TLAN IP address was in a 'Voice' VLAN but it needed to be in both a 'Voice' VLAN and an 'Access' VLAN. (Access VLAN is a Cisco term)
Once the MGC TLAN IP address was added to the 'Access' VLAN then the call matured as it should and no ERR008 message was seen.
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
Typical DDI into MGC using 96 port DB out over the TLAN to a Cisco router then on to the IP set
The IP set rings - CSA - Call drops & err008 seen
Description of err008 from NTP's
ERR0008 tn1 tn2 Call drop due to IPTN failure.
TN1 - PTN
TN2 - VTN
Action:
Severity: Major. Critical to Monitor: No. SNMP trap: Yes
The TN's in the ERR008 were the I/C DDI Trk and the 96 port DSP port TN.
Tried another MGC card but that didn't fix.
Tried another 96 port DSP board but that didn't fix.
From a TLAN port on the IP Tele side of the Cisco switch it was possible to Ping the MGC DSP TLAN IP, but you couldn't Ping the actual MGC Board TLAN IP.
We then put the MGC and the IP set into a standalone HUB and you could Ping all TLAN IP's
This showed a problem with the Customers Cisco switch.
Customer then fixed.
The customer said that on the Cisco the MGC Board TLAN IP address was in a 'Voice' VLAN but it needed to be in both a 'Voice' VLAN and an 'Access' VLAN. (Access VLAN is a Cisco term)
Once the MGC TLAN IP address was added to the 'Access' VLAN then the call matured as it should and no ERR008 message was seen.
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
- Thread starter
- #5
Thanks man we ended up RST the MGC and the ERR008 stop once the card Registerd , this fixed today's problem but still not sure why it happend the first time on Tuesday , I asked the Engineer about Access Vlan and he said we already have both . Thanks for the reply I'll keep this in mind .
- Status
Similar threads
- Locked
- Question
- Question