cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
54770
Views
36
Helpful
15
Replies

PRI error message (RAI detected)

Manoj Wadhwa
Level 1
Level 1

Dear Friends,

I am getting the below log messages from one of my routers

Nov 12 17:53:19.841 INT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to up

Nov 12 17:53:20.133 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:21.209 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:22.221 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:23.625 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:24.633 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:25.649 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:26.657 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:28.637 INT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to down

Nov 12 17:53:33.953 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:34.961 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:36.017 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:36.941 INT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to up

Nov 12 17:53:37.025 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:38.841 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:39.849 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:41.829 INT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to down

Nov 12 17:53:42.113 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:43.121 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:47.429 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:48.437 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

Nov 12 17:53:50.969 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up

Nov 12 17:53:51.977 INT: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to down (RAI detected)

I am not sure what is this about ? I have checked this with my provider and they say there does not seems to be any issue from their end? Can anyone help me understand what this error suggests ?

Thanks in advance,

Regards,

Manoj

1 Accepted Solution

Accepted Solutions

This may happen due to wrong CRC4 settings as well 

Try disable/enable framing CRC4 on the controller interface (Framing NO-CRC4, Framing-CRC4)

View solution in original post

15 Replies 15

paolo bevilacqua
Hall of Fame
Hall of Fame

RAI means Remote Alarm Indication and it happens when the circuit is fine but the device on the other end was disconnected or out of service, or like in your case, flapping between RAI and normal. This indicates a serious problem indeed.

Hope this helps, please rate post if it does!

Thanks. But can you plz let me know what is the solution for this problem. How can i isolate this error?

Regards,

Manoj

Hi,

you have no problem on you side. RAI indicates a problem on the other end of the circuit, possibly with the switch.

You need to have this fixed by telco. If they said that all is good, then ask them to bring a small ISDN PRI device or tester of their own, and show you that they can make calls with it.

I am getting the same error on the router, I got the TELCO guys to connect the instrument. They were able to make outgoing calls from the PRI link without any disturbances.

Is there anything else that needs to be checked from the TELCO end?

You are responding to a 6 years old thread.

Open new threads for new problems, post ":show controllers E1".

I have faced such error before and found that cause foir such due to isdn switch tybe missmatching between the Voice gateway and PSTN switch.

I have faced such error before and found that cause foir such due to isdn switch tybe missmatching between the Voice gateway and PSTN switch.

Can you please let me know if the problem got resolved by changing the isdn switch-type on the router?

Hi Joseph,

Problem got fixed after disabling CRC setting from Telco side ...

Now observed new error " Channel unacceptable" in ISDN Q931 debug for both incoming & outgoing call..

Did anyone observed this type of issue earlier?

Vinod Kembhavi wrote:

Hi Joseph,

Problem got fixed after disabling CRC setting from Telco side ...

Now observed new error " Channel unacceptable" in ISDN Q931 debug for both incoming & outgoing call..

Did anyone observed this type of issue earlier?

As indicated above already: please open new threads for new problems, posting the relevant configuration and debug taken.

Thank you for the update.

Hi,

"Channel unacceptable" issue got resolved after changing channel selection on Call Manager under PRI setting from bottom down to Top Down.

http://telos-systems.com/support/csb/TCSB-022101.pdf

Cause No. 6 – Channel unacceptable

This cause indicates a called user cannot negotiate for a B-channel other than

that specified in the SETUP message.

Thanks,

Vinod

This may happen due to wrong CRC4 settings as well 

Try disable/enable framing CRC4 on the controller interface (Framing NO-CRC4, Framing-CRC4)

Thanks mate, you saved my day!!!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: