Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Trunk not connecting 1

Status
Not open for further replies.

Ceaserx

Technical User
Apr 14, 2008
119
ZA
Hi All

I have a client with 3 Mitel 3300 controllers, 1 MXE and 2 x CX. The MXE and one CX controller has been upgraded to MCD5 and one is still on Version 8.

The MXE was upgraded first and all IP trunks worked fine. When we upgraded the one CX the IP trunk to that branch went out of service on all other controllers. All the routing works fine as I can still ping and traceroute to all controllers. The IP trunk between the MXE and the CX with Version 8 works fine.

I can't telnet to ports 1066 & 1067 for the CX with MCD5 but the other two is fine.

When i do a RMESS VERIFY PBX 3 LAN command on the MXE I get the following:

RMESSAGE: Unsolicted STH Close
RMESSAGE: Failed to connect to PBX 3

When I do RMESS VERIFY PBX 1 LAN command on the CX with MCD5:

RMESSAGE: Invalid PBX ID
RMESSAGE: Failed to connect to PBX 1

I have checked all programming but it did work before the upgrade.

Any suggestions?

 
The invalid PBX ID indicates that the ICP/PBX Networking form on the CX is not programmed correctly.

Make sure there is a PBX 1 (That matches Cluster Element 1 and Network Element 1) and that the IP address is correct.

**********************************************
What's most important is that you realise ... There is no spoon.
 
I've had a similar issue on a couple of sites.
When I change the route type from "IP/Xnet" to "Direct IP" then suddenly everything works like PFM.
These trunks worked after the upgrade and then no longer do.
No clue why. Reboots do not help.

Try change the route to use "Direct IP".

Dry Aquaman



 
Thanks, will try the direct IP routes
 
Just to report back on what solved the problem.

I had to remove all the IP trunk programming and remove the Network Element PBX ID of the local PBX. This then forces you to select the controller as local under the ICP/PBX Networking form.

Even though it was programmed correctly before it did not work until doing this and selecting it as the local PBX and then entering the IP details.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top