IP Trunk Setup - Two 3300's

[Cabarrus]

Our health department shares a building w/ our counties social services and have 4 digit dialing working between our SX2000's but those are going away and we want to setup IP trunking via our 3300's. Routing works between them as we can ping each other's 3300.

It is currently not working and we have two items we think may be causing it..

1) Under IP Networking Programming we see this: CAUTION: The PBX Number for each element must match the element's CEID index.
Does this mean under the ICP/PBX Assignment form our PBX Number must mirror on each of our 3300's ? Or can someone elaborate what that means.

2) His Mitel 3300 ICP is running version 9 software and ours is version 8. I am not sure if this could cause it?

Any help is much appreciated, and if I can share anymore details to assist, let me know..

thanks!

 

[kwbMitel]

In your Cluster programming, each system is assigned an ID Number. (CEID = Cluster Element ID)

In your ICP/PBX Assignement each PBX is assigned a Number.

These Numbers must match.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Cabarrus]

thanks, ill give that a look and let ya know!

 

[LoopyLou]

Also you can network release 8 and 9 systems together without much problem so that is not what your issue is.

It is most likely your programming.

 

[Mitelpassion]

Also make sure you trunk service assignment is set to absorb the correct amount of digits - in your case I'm guessing 0

 

[slapin]

Also make sure that you enter 0 in number of digits to absorb if you don't absorb any. There is no default value for this field.

P.S. So far I counted 4 things which may be configured wrong if you don't know all this trics

 

[Cabarrus]

I was told under the ICP/PBX Assignment form, the order of PBX Numbers must be the same between our two 3300's .

i.e. PBX 2 is our local , PBX3 is an IP Trunk to another site and PBX Number 4 is the IP trunk to his 3300. But on his end his pbx 3 is the local one we need to connect to, so i would need to undo configuration of our ip trunk pbx 3 and set it to 4 and make his pbx 3 so they are mirrored properly.

does that sound right?

 

[kwbMitel]

I dont understand your terminology.

Why are you refering to PBX's as IP trunks?

How many PBX's (3300's) are you networking?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Cabarrus]

We have a PBX at our main site and one at another one of our sites connected via IP Trunking.

We want to add another PBX into the mix at our main site which is owned by another agency. That PBX is connected to 3 other PBX's.


In ICP/PBX assignment there is a PBX Number column. I was told by a phone company rep, that the PBX numbers between our main site PBX and the other agencies PBX have to be mirrored for it to work. i.e. if our local PBX # is 2, and his local PBX # is 3 . On my PBX in ICP/PBX assignment form i need to have his added as #3. Currently my #3 is occupied with configuration for our other site.

I hope this makes sense. this is a new area for me.

thanks

 

[slapin]

It is total BS.

Try to read embedded help files starting from the very beginning. When you get the idea behind IP trunking, check what needs to be done to make it work. If you don't have time or desire, call MITEL and ask them to find a reputable VAR in your area.

 

[kwbMitel]

OK,

That is much clearer.

In a well designed system the PBX numbers should be identical. PBX 1 should represent the same system regardless the of system it is programmed on. Whether or not this is mandatory is a completely different matter.

I would say if your intent is to cluster these systems (very difficult to say the least) then the PBX number must match.

If you intend to implement resiliency, then the PBX numbers must match.

If all you want is the ability to call between systems by dialing a PBX prefix and then extension number then it can be managed without the PBX numbers matching. I wouldn't necessarily recommend it but I see no reason that it would fail.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[slapin]

I made a rule for myself to have unique PBX numbers across the entire network. Every new controller gets new number. Plus I assign IP trunk numbers matching remote PBX number, route records match trunk numbers and so far so on. It is not a requirement, but when I look in ASR and see that a prefix is pointing to route #5, I can assume that it is pointing to PBX #5. Some fancy cases I have moved to much higher records numbers. IMHO

 

[kwbMitel]

I agree Slapin, best practices would be each PBX has a unique number.

All I'm saying is that networking these systems MIGHT be possible depending on the requirements.

If all that is required is simple networking for dialing set to set between systems then the numbers shouldn't matter. Big headache to support but doable.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

couldn't agree more.
keep it all unique but if you're not clustering or going resilient you might get away with non-unique pbx numbers.

Slapin makes a good point which I think most of us have entrenched in our cluster designs. I also have a system very similar to Slapin. This makes troubleshooting a walk in the park compared to programming all over the show.

first things first though. you need to understand the minimum programming required for an IP trunk to work. question is do you at this point?