Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Ronan on January 31, 2019, 11:11:42 AM
-
Hello,
I don't know if I'm too dumb or too drunk but I'm missing something.
I'm looking at this doc : http://www.mitelforums.com/articles/3300/how-to-create-loopback-trunk.php
I'm failing right at the start, first sentence is This Network Element will be/is your local PBX. Note if this 3300 is already in a cluster then these fields are already filled in
My 3300 is already in a cluster, it has a PBX number, it has several IP trunks to other 3300s.
To create a new IP trunk should I use a fictive PBX number ? Then I put the IP adress of the 3300 I'm connected to ?
My goal is to route calls to a specific number through this loopback, and restrict it to 10 simultaneous calls.
Thanks for your help.
-
In the ip/xnet you create a profile and group that uses the local pbx number
-
No, the "remote" is the same PBX as the local.
Step 4) is probably where you need to start - the other steps are probably just worth going through so you can make a note of PBX IDs and so forth, not configure anything.
Edit: oh, except for Step 2) - you need to create that.
-
OK, so I can't reduce the number of VOIP calls in the ICP/PBX Networking as that would affect the calls I don't want to restrict.
I can put a low number of trunks when creating the IP/XNET Trunk Group but that doesn't seem to be working.
-
Hello can someone explain to me the purpose of this setup?
-
I think he is trying to limit the amount of calls to an ACD path due to bandwidth issues
-
Hello can someone explain to me the purpose of this setup?
I use Loopback trunks to route calls to numbers where I want to modify the number instead of sending it to the external trunk.
eg, people dial the full external number for an internal extension - I don't want to send that out to the carrier where it will just get hairpinned back in, so I use a loopback trunk to change the "dialled number" into an internally-recognisable number.
-
Hello can someone explain to me the purpose of this setup?
I use Loopback trunks to route calls to numbers where I want to modify the number instead of sending it to the external trunk.
eg, people dial the full external number for an internal extension - I don't want to send that out to the carrier where it will just get hairpinned back in, so I use a loopback trunk to change the "dialled number" into an internally-recognisable number.
Thanks Vince that make sense
-
Hello can someone explain to me the purpose of this setup?
I use Loopback trunks to route calls to numbers where I want to modify the number instead of sending it to the external trunk.
eg, people dial the full external number for an internal extension - I don't want to send that out to the carrier where it will just get hairpinned back in, so I use a loopback trunk to change the "dialled number" into an internally-recognisable number.
Yes , exactly Vince , this is why i use too , the loopback , i cant believe in 2019 some users still dial full number to join internal number , grrrrrrr.
-
Actually we do use something like that for that purpose, changing the numbers from external to internal (our ARS digits dialed has 21 pages), but here I don't want to just change the numbers, but restrict the number of calls. Someone from Mitel suggested me to do this.
-
In the IP/XNET profile you can restrict the number of trunks between 0 and 2000 (in/out)
Don't know if this works for a PBX marked as "local"
-
I think you mean in the IP/XNET Trunk Groups. I've put "Number of Trunks" at 1 and I can do 3 calls so it doesn't seem to be working.
-
Sorry, I ment "ICP/PBX Networking"
-
Hello can someone explain to me the purpose of this setup?
I use Loopback trunks to route calls to numbers where I want to modify the number instead of sending it to the external trunk.
eg, people dial the full external number for an internal extension - I don't want to send that out to the carrier where it will just get hairpinned back in, so I use a loopback trunk to change the "dialled number" into an internally-recognisable number.
Yes , exactly Vince , this is why i use too , the loopback , i cant believe in 2019 some users still dial full number to join internal number , grrrrrrr.
Well, it happens more now, with people using Click-to-Dial on the desktop.
-
Tom2018 : I definitely can't do that, although that was my initial idea, I created another network element to do it, however that caused problems, it was seen as a duplicate. The IPBX already has several IP trunks, and I don't want to restrict calls on those, so I can't do it that way.
Now I'm thinking of wasting SIP trunk devices to do it, I have some laying around (and it's a temporary setup).
-
I can already create a new Network Element with the same IP...
And there is no warning about a duplicate
-
But your 3300 doesn't seem to be part of a cluster. Mine are, and when trying to sync from one to another, I get an error telling me there is a duplicate IP address in Network Elements.
-
Yes, you're right.
In a cluster this seem don't working
-
I'm not sure what you're trying to do with creating dummy Cluster members.
To get a loopback working, you create a Trunk Group that refers to the same PBX you are on with a Local Profile Number that refers to a Trunk Service number that is *the same* as the Remote Profile number, which are in turn a Trunk Attribute number you've created for the purpose.
The forms are
ICP/XNET Trunk Group
ICP/XNET Trunk Profile
Trunk Attributes.
Just follow the Loopback instructions and it works.