Page 1 of 1

DID and incoming calls on PRI not working

Posted: 21 Mar 2011 05:28
by Xero
Hi all,

My customer is using R 7.0 with reduntant CPUs, there are 5 incoming PRI trunks and 2 outgoing PRIs,

Suddenly all my incoming PRIs stopped working, i have checked the card status but all PRA couplers were in service, I have tried to reboot them but my incoming calls didnt start on PRIs, i have checked the incidents and there I see alot of below incidents :

21/03/11 14:14:32 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:32 000001M|00/12/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 265) especially TEI or flag
21/03/11 14:14:33 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:33 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:33 000001M|00/12/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 279) especially TEI or flag
21/03/11 14:14:34 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:37 000001M|05/02/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 4183) especially TEI or flag
21/03/11 14:14:40 000001M|05/11/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 4596) especially TEI or flag
21/03/11 14:14:41 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:42 000001M|08/22/0/000|=3:0287x002=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:42 000001M|05/02/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 4189) especially TEI or flag
21/03/11 14:14:42 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag
21/03/11 14:14:43 000001M|00/16/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 360) especially TEI or flag
21/03/11 14:14:45 000001M|05/11/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 4599) especially TEI or flag
21/03/11 14:14:46 000001M|08/22/0/000|=3:0287=Header msg pb (T2, T0 or S0), (5 1 6250) especially TEI or flag

I dont know why i am getting these incidents, but I had to resolve the issue i did bascul my CPU and the issue resolved, but i want to know the causes of this issue and these incidents can anyone please help me so that i will do the right thing for saving my client in future.

Regards,
XERO

Re: DID and incoming calls on PRI not working

Posted: 21 Mar 2011 07:02
by Konstantinos.E
hi

syncro problem i suppose...

check with infocs

Re: DID and incoming calls on PRI not working

Posted: 04 May 2011 07:12
by Xero
this problem reoccurs after every few weeks i dont know how to solve it :S

Re: DID and incoming calls on PRI not working

Posted: 04 May 2011 11:34
by Konstantinos.E
the role is the same after the bascul...or this is happenng to the other cpu aslo? did you tryed with an other pra board ?


this is the meaning of the incident

Incident number : 287 Impacted element : Dhs3Terminal Incident severity : Minor
Network indicator : 3 Event type : 10 Probable cause : Unknown

Header msg pb (T2, T0 or S0), (P1 P2 P3) especially TEI or flag

P1 : Type of incident
- 1 -> flag received inferior to 128 on T2, T0 or S0
- 2 -> Non-existing link
- 3 -> TEI different from 0 on T0
- 4 -> Problem of trunk assignation on T0
- 5 -> Problem on internal facility or notification chain
P2 :
- 2 -> Problem on internal notification chain if the type of incident is 5
- 3 -> Problem on internal facility chain if the type of incident is 5
- Number of equipment for other type of incident
P3 :
- Value of the flag if the type of incident is 1
- Number of the lacking link if the type of incident is 2
- Value of the TEI if the type of incident is 3
- Number of fictitious equipment if the type of incident is 4.
- Number of equipment if the type of incident is 5
T2 T0 S0 fault
The digital communication concerned with this incident does not succeed, but
the system is not
disturbed.
no operator action required

Re: DID and incoming calls on PRI not working

Posted: 06 May 2011 01:39
by Xero
yes with the same role....i didnt check with other cpu...and i dont think the issue is with PRI board because there are 5 PRA boards and problem is seen in all trunks connected to all boards, so thats why i think that this is some configuration or system issue