Halted Cards, VOIP one-way issue - 07/12/12 10:36 AM
Hi, here's a good one:
Someone who was working behind our rack mounted Axxess cabinets evidently bumped something because after he's done our second cabinet (connected by a wide flat ribbon cable) shows all cards with red halted light. Nothing obvious seems physically wrong. Reseat of cards / reboot of PBX did not help. Any thoughts on that?
The second cabinet was used only for our single PRI and 32 of our 50-ish IP phones. We have a 1024 system with a CPS.
The workaround is that I installed a spare T1 card into the first cabinet and connected the PRI to that. In DB Studio I moved the 32 affected IP sets to an previously installed but unused IPRC card in the first cabinet. I made sure both of these cards have the same settings as the original cards except that the IPRC card already had an IP address and gateway as we previously had been using it.
I corrected the trunk groups and ARS and confirmed that on the IPRC all 32 voice resources are set to IP Endpoints.
Finally we programmed the affected IP sets with the new IPRC gateway IP address.
In and outbound calling are generally fine. The first cabinet is now nearly full, now having a T-1 card, 2 IPRC, DKSC, SLC16, OPC and the CPC card.
It's a 1024 port system with a CPS server and over 140 IP endpoint licenses. Timeslots also don't seem to be an issue according to DB Studio information.
Our problem is that occasionally we now experience only 1 way audio on IP sets. Whether internal or external it is the call initator who cannot be heard. The call receiver can be heard. Again this is for both outbound and inbound and IP to IP calls. If you make the call, the receiver can't hear you. Occasionally. Not 100% of all calls to any IP set. You can repeat the call and it works fine or the receiver can call you back and now as the initiator, he can't be heard.
There is a firewall between the PBX and the IP sets but firewall permissions are managed by groups of IP addresses and both the IP of the original card and IP of the new card are listed in the same group therefore the firewall policies work the same for both of them. Previously this IPRC card with it's IP address was working fine with IP end points.
Thoughts?
Someone who was working behind our rack mounted Axxess cabinets evidently bumped something because after he's done our second cabinet (connected by a wide flat ribbon cable) shows all cards with red halted light. Nothing obvious seems physically wrong. Reseat of cards / reboot of PBX did not help. Any thoughts on that?
The second cabinet was used only for our single PRI and 32 of our 50-ish IP phones. We have a 1024 system with a CPS.
The workaround is that I installed a spare T1 card into the first cabinet and connected the PRI to that. In DB Studio I moved the 32 affected IP sets to an previously installed but unused IPRC card in the first cabinet. I made sure both of these cards have the same settings as the original cards except that the IPRC card already had an IP address and gateway as we previously had been using it.
I corrected the trunk groups and ARS and confirmed that on the IPRC all 32 voice resources are set to IP Endpoints.
Finally we programmed the affected IP sets with the new IPRC gateway IP address.
In and outbound calling are generally fine. The first cabinet is now nearly full, now having a T-1 card, 2 IPRC, DKSC, SLC16, OPC and the CPC card.
It's a 1024 port system with a CPS server and over 140 IP endpoint licenses. Timeslots also don't seem to be an issue according to DB Studio information.
Our problem is that occasionally we now experience only 1 way audio on IP sets. Whether internal or external it is the call initator who cannot be heard. The call receiver can be heard. Again this is for both outbound and inbound and IP to IP calls. If you make the call, the receiver can't hear you. Occasionally. Not 100% of all calls to any IP set. You can repeat the call and it works fine or the receiver can call you back and now as the initiator, he can't be heard.
There is a firewall between the PBX and the IP sets but firewall permissions are managed by groups of IP addresses and both the IP of the original card and IP of the new card are listed in the same group therefore the firewall policies work the same for both of them. Previously this IPRC card with it's IP address was working fine with IP end points.
Thoughts?