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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Trunking not working on node

Status
Not open for further replies.

ExCentigram

IS-IT--Management
Jul 26, 2011
37
US
Hi all
This problem has me very frustrated. We have 7 sites, MCD new release 6, existing for long time. We had 8 sites, one closed for awhile, I changed the iP address of that controller, never removed it from the cluster and just stuck it in the rack at one of the sites. So now, the economy is good, I go to deploy it at a new location, and xnet is not working. All the original ARS, CEID, etc was already in there. I went through and double, well now triple checked and all the sites line up. PBX numbers are consistent. CEID and Feature DN are consistent. When dialing site 8 from any other location I get Out of service.

Location 1
STATE XNET ALL

Signalling | Link | Dest | XNET | State | Owner | ID |Status
Dvc Location |Handle|Switch| Trunk Id | | | |
-------------------------------------------------------------------------------
1 1 11 | | 3 | |Idle | | |
1 1 11 252 | 5 | 5 | |Established | | |
1 1 11 1 | 23 | 8 | |Established | | |
1 1 11 253 | 4 | 9 | |Established | | |
1 1 11 250 | 8 | 11 | |Established | | |
1 1 11 | | 14 | |Out of Service| | | <-- new site
1 1 11 254 | 3 | 16 | |Established | | |
-------------------------------------------------------------------------------

New site
STATE SNET ALL

Signalling | Link | Dest | XNET | State | Owner | ID |Status
Dvc Location |Handle|Switch| Trunk Id | | | |
-------------------------------------------------------------------------------
1 1 11 | | 3 | |Idle | | |
1 1 11 | | 5 | |Idle | | |
1 1 11 | | 8 | |Idle | | |
1 1 11 | | 9 | |Idle | | |
1 1 11 | | 11 | |Idle | | |
1 1 11 | | 14 | |Idle | | |
1 1 11 | | 16 | |Idle | | |
-------------------------------------------------------------------------------

RMESS VERIFY PBX 14 LAN
shows the following:
RMESSAGE: Open Timeout
RMESSAGE: Failed to connect to PBX 14

Ping works fine between all sites, no problems there. Phones are up at the new site 8 - they can dial out over the PRI
 
If you changed the IP adress of the controller, you need to change it in Network Element and in the ICP / PBX Networking of each controller.
 
There is an IP address in the ICP/PBX form of every site that would need to be modified. Have you done so?

**********************************************
What's most important is that you realise ... There is no spoon.
 
Yes that was done at the beginning. THe new ip address is in the Network element form on all controller and in ICP/PBX networking. When doing a routeshow from maintenance command window in a different node, the route to the new controller address 10.10.30.241 shows up. It seems like it's trying to establish a connection but not able to. Traceroute from maintenance shows successful path, as does ping.
 
btw, in that STATE XNET ALL command, if I run it before making any calls it shows

STATE XNET ALL

Signalling | Link | Dest | XNET | State | Owner | ID |Status
Dvc Location |Handle|Switch| Trunk Id | | | |
-------------------------------------------------------------------------------
1 1 11 | | 3 | |Idle | | |
1 1 11 252 | 5 | 5 | |Established | | |
1 1 11 1 | 23 | 8 | |Established | | |
1 1 11 253 | 4 | 9 | |Established | | |
1 1 11 250 | 8 | 11 | |Established | | |
1 1 11 | | 14 | |Idle| | | <-- new site
1 1 11 254 | 3 | 16 | |Established | | |

Then when I make a call that new site (PBX 14) goes out of service. It seems it cannot establish the link. And it shouldn't show Idle all the time, it should show Established.
 
Mostly all works now. I did not, even though I looked at it 3 different times, see that the ip address in the ICP/PBX form under trunking was still the old address. I've changed that and now almost all site to site is working. Just have a couple little hitches that I will work on, SO thanks to both of you for steering me to re-look at that.
 
What you may have left now is some SDS errors that need fixing.

Always look out for the next guy because it may be you!
 
Thanks for the update and glad to help.

We've all been there. (looking directly at the issue and not registering)

**********************************************
What's most important is that you realise ... There is no spoon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top