Mitelpassion
IS-IT--Management
Hi,
Have a weird problem and it's never happened to me before. XNET IP trunking was setup between two system 8.0 UR 2. All was working 100%.
I was busy syncing OPS man and making some other td name changes when the PBX reported a crtical alarm. The alarm was a Comms error (IP trunk down). The other controller was running, I could ping it, log into it and make programming changes on it. Also did a Tracert rtc from both controller to each other and succeeded.
I then ran a st xnet all on the first controller. displayed pbx nr 2 out of service, did the same on pBX number 2 and it said ICP/PBX not programmed for XNET - State Aborted. What the hell! Off course it is. Cleared the programming and re did the programming with no luck. Rebooted controller no luck.
any ideas, anyone seen this before?
thanks
Have a weird problem and it's never happened to me before. XNET IP trunking was setup between two system 8.0 UR 2. All was working 100%.
I was busy syncing OPS man and making some other td name changes when the PBX reported a crtical alarm. The alarm was a Comms error (IP trunk down). The other controller was running, I could ping it, log into it and make programming changes on it. Also did a Tracert rtc from both controller to each other and succeeded.
I then ran a st xnet all on the first controller. displayed pbx nr 2 out of service, did the same on pBX number 2 and it said ICP/PBX not programmed for XNET - State Aborted. What the hell! Off course it is. Cleared the programming and re did the programming with no luck. Rebooted controller no luck.
any ideas, anyone seen this before?
thanks