Mitel 3300 - XNET Busy

[AH64Armament]

I have a site that has 8 3300's that are networked with IP trunks between each of them. This has all been working well for quite a while. All Sites are running release 8.0.8.8 software.
The systems are listed as PBX #1,2,3,4,5,6,7,8
Recently when users at site 1 call site 4, they get "xnet busy" on the display, with re-order tone. Similar has happened when an outside caller calls a user on site 4. The PRI's are on site 1 and 2.

Users on Site 4 can call users at other locations without problems.
I did not get any reports of users at any other site having the issue calling to site 4.

The log files are only showing a congestion report about the same time as the problem.

Another tech has troubleshot the issue at the time it happened, and has reset the site 4 controller. This reboot cleared the immediate problem.
The problem has happened twice now, and I expect to see it happen again soon.
Also, after the first time, we increased the number of IP trunks at each site from 23 to 48. This didn't resolve the issue, even in the immediate time.

If anyone would like to see how this is set up, I can set up a YA collaboration session and share the setup with you.
mark_compton@phonesav.com

Sincerely,
Mark Compton

 

[Lundah]

XNET is probably a trunk label in Trunk Service Assignment. What this is telling you is whatever trunk/trunk group the call is trying to access is either busy or out of service. Go into Maintenance Commands of the controller and type in "state xnet all" and you can see the status of all of the IP trunk links, I'm guessing one is out of service. If so, verify the path availability across the IP network, then check the programming in the ICP/PBX Assignment and XNET ICP/PBX Assignment forms and correct anything that may be wrong there.

 

[AH64Armament]

Thanks for the reply. Unfortunately the label isn't what it is. XNET is the IP trunks from one site to another. This issue happened both Thursday and Friday of this week and as of right now is happening again.
I have opened a ticket with Mitel support, and they have escalated it to the level 2 support and design. It was interesting to see that the CCS trace shows the call failure on both the originating and ending systems. It shows the call being rejected.
I believe they will recommend an upgrade or a patch.
They originally began to make the determination that the problem is on the network, not on the phone system. I manage this site’s data network as well as their telephone system. We were able to make ping commands, and trace routes from one system to the others, and fully determined that this problem is on the 3300’s.
I have found several ways to resolve the problem, albeit temporary.
First, reboot the receiving controller. This has been almost the best solution, as the problem doesn’t come back for a week.
Second, disabling the switch port or unplugging the Ethernet cable feeding the controller. Doing so on the originating controller is ineffective.
Third, busying the XNET going to the originating PBX at the end PBX, then returning it to service. For instance, “bu xnet pbx 1” “rts xnet pbx 1” From Site 4.
Fourth, (I just found this out minutes ago), busying the xnet from PBX 1 to PBX 4. “bu xnet pbx 4” and rts.

I hope to hear from Mitel support soon with a solution. We went through the configuration of this, and it is programmed properly. The funny thing about this is that it has been working for about 6 months without any problems. This organization has 8 controllers that are all running the same software load, 8.0.8.8. This problem is only happening from Site 1 to site 4. All other sites are working properly, even when the failure is happening.

Mark