sundance-communications.com/forum Forums Other TDM Phone Systems Sprint - Tadiran Telephones & Systems IPx 500 - UGW ipx - saying wait_db

I am having an issue with a 500 w/ version 14.66 software so of course tech support won't talk to me without a PO. (They will be upgrading in the next couple of months). Customer has been up and running fine for years. They have 2 sites networked together. They mainly use it to share voicemail. Last week something happened and now in CLIS the UGWipx (v. 2.28) says wait_db. They power cycled the system but it did not help. Red LED won't go out. MG-15 card installed.
I am going to the site tomorrow to trouble shoot. I am planning on bringing another UGW ipx and MG15 with me to swap. IT guys says the private IP addresses assigned to signalling and media are good addresses. Any ideas of what to do would be appreciated. Has anyone seen this issue before?

The media gateway and signalling and not talking to each other. Sounds like a IP conflict bad switch port or MG card has gone bad. 2.28 seems awful old as well but if it's been working. In my personal experience its almost ALWAYS been a rogue device plugged into the network conflicting with the IP on that card OR bad switcht port.

You were definitely on the right track. When I got onsite I plugged into the customers switch that the UGW was plugged into with my laptop and I could not ping signaling or media. They had 2 switches onsite and someone had plugged the patch cord into the wrong switch. We still have an issue though. The switch that we are in now I can ping both IP addresses. The other location can now 4 digit dial to this site BUT this site can not 4 digit dial to them. When they try the display of the phone says "Que" and we get beeping like when the PRI is down. We can call out with no problem and incoming is fine as well. The IT guy says the firewall is set up correctly and it should be working. Programming all looks good. Any ideas?

Reset both cards and see if it comes back up. It's been down so long I have seen it mark trunks (even IP) as out of service.

It turned out to be that the trunk group members disappeared when the UGW was removed during troubleshooting. While researching I found that prior to 14.67 (and this one was 14.66) that you would lose programming on the UGW. The TG was still there but had no members. Once I put them back in all was well. Thanks so much for your help!