Alcatel Unleashed

We recently had a hard drive die in one of our switches (Node B). We replaced the hard drive and restored the database. However, since that time we have had issues dialing that switch.

We have 10 switches spread out over a wide area. Nine are on 5.0, One is on 6.1

Since the hard drive replacement, we see no problems at Node B. It can dial out to all of the other Nodes without a problem. However, all of the other nodes cannot dial into Node B on the IP trunks. Whenever you dial a 4 digit extension from the other nodes, you get a message stating, "You may request automatic callback by dialing 5" as if the extension(s) were busy.

We have tried resetting the hybrid links, re-enabling the x25 tunnell, and totally rebuilding the IP trunk groups on Node B & the Primary PCX. We have restarted the switch at Node B, and the Primary phone switch.

We are stumped. Additional information is all network connections seem fine, we can ping, telnet and traceroute the switch, and nothing looks wrong.

Any help will be greatly appreciated.

Cheers,
Joe

Hi.
check the VPN configuration, if all ok, you can trace on Hybrid link to verify signaling.

best regards

Also, when you network PBX, they should ALL be on the same release.
Did you try to roll back to 5.1 on this PBX ?
Was it in 6.1 already before ?

Hi,

In ip parameters, there is a parameter called Inter node link signallinhg mode (i am not sure if it is the correct name) that must be equal in all the nodes. The mode can be h323 or not. Probaly on the resent node, it is not set to h323, witch was the default value or the only value possible (i do not remember)

Check the NPD on nodeB as could be an incoming translation problem. Make also sure that the Local NPD prefix is pointing to the right NPD.

we had this problem before, and we found out that we can ping the CS from one node to the other, but from one node we cannot ping the remote GD's, it was the IP address configuration in the GD of the nodes(subnetmask). Check if you can ping th eremote CPU, GD/INTIP. Maybe after restoring the databse you didn't configure correctly the GD/INTIP IP Configuration.

I hope this will help you solve the problem. Many issues could be also the problem, like VPN Configuration.