ABC IP Issue

[amizone]

Dear All ,

I have onsite 2 nodes interconnected via ABC-IP, I m facing strange Issue, each Thursday afternoon the link stopped (when we call from node the the second node , we got Busy or link out of service ) then i need to restart both nodes or rstscpl for the both (GD node2 or INTIP nod 1) to have the link working again knowing that broadcasting is disabled on the both nodes, could you assist

[vad]

Do you have some incident on CPU when problem starts?
What is your release on PBX?
If you restart only one site - link not started?
You have problem with all feature (signalling and voice) - can you ping adjacent CPU?
suproutage - show some problem or not?

[amizone]

Thank you VAD , for your reply ,

we never had any problem with the CPUs , we had this problem the first week when the ABC link was configured , I think the problem is related to the configuration

Release is 11, If i restart only node 1, I can call node 1 from node 2 but I cannot not call node 2 from node 1, so I need also to restart the node 2 to have the link working on the both side , when the link is out of service I can PING the node 2 from node 1 Vice-versa , no problem on the suproutage

[vad]

About ping - you can ping from CPU (not from PC) to IP address declared in internode link?
About incidents - it's not about problem with CPU. If you have link (signalling/ and Ok in suproutage) - during problem you can have some incidents about link/resources. You need check this with incvisu command.

[amizone]

below the export incvisu export
23/01/22 11:06:38 000001M|000/11/0/000|=3:4104=outgoing VPN Overflow call aborted No 41 6300
23/01/22 11:06:38 000001M|019/00/0/000|=4:4108=VPN call failed: err 143N NL 1>2 e

I have created more VPN prefix , but still same problem , kindly assist

[vad]

Do you have something in "t3" trace? 0-11-0 - PRA board?

[amizone]

below the export from t3 cpl 11

(653885:000037) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 0 cpl: 11 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 80 33
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 83 -> [83] NO ROUTE TO DESTINATION
|______________________________________________________________________________

[vad]

On remote site - not managed what to do with received called number.
Remote site receive Setup with calling number and cannot route this call to destination.

[amizone]

I did not understand what did you mean , maybe because I am not an alcatel expert ,

could you explain what I have to do ? knowing that after restarting 2 PBXs the link works perfectly , and the two are located in the same network (site)

[haroun]

hi
as Vad told you , the remote side receive a setup with called number but it didn't fount a route for that destination (called number).
the called number is it local directory number for the remote site or transiting destination located in other nodes? in case of transit call cos are well managed ?!