problems setup my first networked systems

[pgartner]

A client I installed a Mitel 5000 HX about year ago now wants to install 2 more in their remote offices.
The main site is 16 phone, each remote office has 3 phones.

I want to network them over the internet so they can make interoffice calls and transfer calls from the local trunk to the agents in the remote office. We do NOT want to share the trunks or do any LD routing

I built up a lab in my office to pre-configure the units and build up my knowledge of how to network these unit.
-   dumped their main office config to my demo unit, (ext1000s, ext2000s)
-   made a very simple config on the 2 remote 5000hx (ext1200s and ext1300s)
-   verified that they are all on the same software version (6.0.10.78)
-   networked each site with a WatchGuard firewall (with a VPN connection between each site)
-   used the networking wizard in DBP to config the connectors

When I try to import the phones from the remote site I get “node X- err.. not reachable”
if I try to dial the node route number (x97001) I get “destination is unreachable” on the phone

Do I need to program a NAT IP Address in the p6000 or do I leave it to the default 255.255.255.255? The traffic is not being NATed over the VPN

I’m stuck, I don’t know what I’m missing…


Paul

[NTEDave]

Check your P6000 and P6001 IP Connection numbers are correct and not clashing.

Use P6100, P6101 for node 1
Use P6200, P6201 for node 2
etc.

It's not instantaneous either, you could program them all up correctly, try a import or export and it would show the error you are seeing, leave it a couple of minutes and try again and they work!

[NeoMatrix1217]

P6000 NAT IP should be your public IP address

[pgartner]

I updated the IP Connections

node 1
local p6000, p6001
to node 2 p6002
to node 3 p6003

node 2
local p6200, p6201
to node 1 p6202
to node 3 p6203

node 3
local p6300, p6301
to node 1 p6302
to node 2 p6303


i'm not sure why my p6000 NAT need to be entered, they don't talk to the public internet, but I set it anyway

in either case, it still does not work.

I noticed in the manual they talk about network groups p7000s. I only have a pp029 default network group.

any ideas?

Thanks

Paul

[DND ON]

Your IP connection numbers need to be consistent. The Processor Module always has the same connection number for a specific node.

I do mine differently, where the last 2 digits of the IP connection is the node number: Node 1 is P6001 and P6101; Node 2 is P6002 and P6102; Node 25 is P6025 and P6125. I’ve got over 50 nodes, so it’s easier to keep track that way.

So, if the Processor Module at Node 1 is P6001, that’s what you need to call it when programming Node 1 at all other remote sites.

For example, you said that you named Node 2 as P6002, P6200 and P6303. If the local connection for Node 2 is P6200, it must always be referred to as P6200.

[NTEDave]

Hello

It should be:

node 1
local p6000, p6001
to node 2 p6200
to node 3 p6300

node 2
local p6200, p6201
to node 1 p6000
to node 3 p6300

node 3
local p6300, p6301
to node 1 p6000
to node 2 p6200

[pgartner]

node 1
local p6000, p6001
to node 2 p6200
to node 3 p6300

node 2
local p6200, p6201
to node 1 p6000
to node 3 p6300

node 3
local p6300, p6301
to node 1 p6000
to node 2 p6200

Your IP connection numbers need to be consistent. The Processor Module always has the same connection number for a specific node.

For example, you said that you named Node 2 as P6002, P6200 and P6303. If the local connection for Node 2 is P6200, it must always be referred to as P6200.

DND ON, NTE Dave,  when I saw your posts last night I wished I had remote access to my lab. you were bang on. fixed that up and it is working like a charm Thanks


now I am going to break it all, restore my pre-networking backup and build the network up again, documenting the steps so I can program their production equipment.


Paul

[NTEDave]

Glad you got it sorted and thanks for letting us know!

[Tech Electronics]

Pgartner,

I would like to throw my two cents in here for your future projects. I know NTEDave and others have stated to keep the base card on the first node defaulted at P6000, but experience has taught me to always change that to P6001 with a PEC of P6101; similar to the way DND ON does it.

Thanks,

TE

[pgartner]

Tearing down and rebuilding the network is easy now that I know the trick. Thanks guys

I have a few more questions.

From each site I can pick up the handset and dial the remote sites STAR (2600, 2640, and 2680).I would like to program a button on their 5330e’s to do this. I tried a system speed dial, but it wants to use the trunk. How can I program a key to point to a CRA , Huntgroup or STAR on the remote system?

In my demo lab, I have my demo 5000 with a backup of the existing production systems config, and the 2 new 5000 systems. When I am ready to deploy, can I just program the networking components on the client’s production system and just re-import/export the phone, cra, star hungroups? Or do I have to revert back each of the new 5000s to NON-networked and build the networking new with their production system?


Thanks

Paul

[NTEDave]

Pgartner,

I would like to throw my two cents in here for your future projects. I know NTEDave and others have stated to keep the base card on the first node defaulted at P6000, but experience has taught me to always change that to P6001 with a PEC of P6101; similar to the way DND ON does it.

Thanks,

TE

Hi TE

If you read post #2, I do it the same as you

[NTEDave]

Tearing down and rebuilding the network is easy now that I know the trick. Thanks guys

I have a few more questions.

From each site I can pick up the handset and dial the remote sites STAR (2600, 2640, and 2680).I would like to program a button on their 5330e’s to do this. I tried a system speed dial, but it wants to use the trunk. How can I program a key to point to a CRA , Huntgroup or STAR on the remote system?

In my demo lab, I have my demo 5000 with a backup of the existing production systems config, and the 2 new 5000 systems. When I am ready to deploy, can I just program the networking components on the client’s production system and just re-import/export the phone, cra, star hungroups? Or do I have to revert back each of the new 5000s to NON-networked and build the networking new with their production system?


Thanks

Paul

Program the button as a PKM/DSS button, you can then configure it as a STAR, Hunt Group etc.

Just program the Networking elements up then import/export and you should be good to go!