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!

3300 MXe III Interconnect Issue

Status
Not open for further replies.

rhyanmeade

IS-IT--Management
Aug 23, 2006
16
US
I have a 3300 MXe III that has 6 analog lines tied to it.
Trunks 1-3 are in trunk group 1.
Trunks 4-6 are in Trunk group 2.

There's 3 phones (out of 20) that are in a different department that I need to have use trunk group 2 (for both incoming and outgoing calls). All the other phone should use trunk group 1 for incoming and outgoing calls.

What's the easiest way to seperate the two departments, while allowing transfers betweem all phones (if that's possible)?
 
If you need inbound on all but outbound on specific then you will need to use COR restrictions.

Create a route for each trunk group
Create a route list that selects each (order doesn't matter.
Use COR restrictions to restrict Group A phones from dialling out on Trunk Group B and Visa-Versa.

If you have no idea what I'm talking about I suggest you hire someone, this can be quite complicated. Especially if you have sub-restrictions where some phones can dial LD and some can't.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Basically the two trunk groups need to be kept seperate on both inbound and outbound calls. But I have the feeling they will expect to be able to transfer the calls between departments if necessary. There should be no sub-restrictions. I've figured most of this out in two days so I guess COR will be next...
 
I agree with kwb, this can be rather complicated...

Also, you can use interconnect restriction and throw all trunks in the same Trunk Group. Then by using interconnect number and interconnect restriction table you can say whics stations are allowed to used which trunks.

This way your COR patern will be unique for all stations.

Regards,

Daniel
 
Interconnect restrictions would be simplest but also the least flexible. You would not be able to transfer. If complete sparation is acceptable then interconnect is the way to go.

**********************************************
What's most important is that you realise ... There is no spoon.
 
I appreciate the input. Lets say that complete seperation is acceptable. Do I just assign a unique Interconnect number to each trunk/trunk group and a unique number to each group the extensions fall under. For Example Trunks 1 through 3 have Interconnect #1, 4-5 set to #2, and extensions 2001-2016 set to Interconnect #3, and extensions 2017-2019 set to #4??

Seemed like I tried it that way but when I picked up Ext 2017, pressed 9 and tried to dial out my call was "Barred".
 
Group A Trunks = Interconnect 1
Group A Stations = Interconnect 3

Group B Trunks = Interconnect 2
Group B Stations = Interconnect 4

Then program your interconnect tables

1 and 3 connect
2 and 4 connect
3 and 4 connect

You may even be able to allow 1 to 4 and deny 4 to 1

I don't use this much, this is a guide only. The help tables should be sufficient to clarify anything i've missed.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Could you not also just do DTS keys on the appropriate phones? Otherwise as already suggested the best is COR restrction in a route list and ring groups for incoming.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
DTS keys have severe limitations.

They cannot be routed to VM for example.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Right agree 100%. However he did not specify that as a requirement. He has only specified this "key system" senario which I belive DTS would work for.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Thanks again. I will try it again today when I have time. Obviously all of the extensions have VM, with ext 2001 in the first group set as the main answer point, and 2016 in the second group as their main answer point.

I'm really guessing on how they expect the programming to be done. I've done a lot of Nortel/Avayas, and Mitel 3000's, but never a 3300. This was handed to me and I was given literally 2 days to configure it and get it installed, with no pre-field or data collection being done. This is a 3300 MXeIII with 19 5320 IP phones going in for a City..

Things should be pretty basic for now, as long as they have VM, and the two groups are split so one cant use the others phones. Otherwise I will wait til they tell me differently.

Thanks again for the help.

 
So I finally got back to this. With the interconnect restrictions set that way, the phones in the second group (interconnect #4) get a call barred error when I try to dial out. It's like they still no matter what try to dial out on Trunk #1, instead of starting on #4.

I can setup a second route using trunk group 2 if I define another leading digit (8 in this case) and it works. I just wonder if this will be confusing for the end users, press 9 for one set, press 8 for the others...
 
If you have an MXE III then you have 'new licensing' therefore you should have tenanting license. Could you not just split the phones into two tenants?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top