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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Merlin Legend T1 channel selection low to high or inverse?
- Thread starter adc110
- Start date
build a second pool ( 890 ) ,take out some of your ( 70 ) pool lines & put them into your 890 pool( like 16 to 23 ) in your ARS tables use your 890 first ,than your 70 pool
when dialing out all your phones will use the 890 pool first than call out on the 70 pool when 890 is busy
when dialing out all your phones will use the 890 pool first than call out on the 70 pool when 890 is busy
MrTelecom1
Vendor
Depending on your carrier too, you can have them ascend or decend.. Inbound is usually ascending, and outbound decending. Splitting them up in different trunk groups in the switch is a cool thing too if you cant get what you want from the carrier.
MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!
MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!
- Thread starter
- #4
So, essentially (since I have all 12 channels of the partial T1 assigned to Pool 70) we are going outbound as a low to high (1-12)? It's too bad the the Legend works in a round robin fashion with trunks on the T1. Instead of choosing the first trunk everytime it selects the next trunk in order in a circular pattern until it cycles around back to the first trunk. The IP Office with a PRI/T1 will always choose the first trunk if it is available which means that when you set the route selection (low to high or high to low) you have a much less chance of Glare. I suppose you can't configure the Legend to always use the first unused trunk instead of round robin?
MrTelecom1
Vendor
A PRI will make life a Lil more flexible.
That will be an explanation!
Renumber that trunk group and make it do what ya want!
I see it comin'!
MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!
That will be an explanation!
Renumber that trunk group and make it do what ya want!
I see it comin'!
MrTelecom1
Re-Living the AT&T/Lucent/Avaya issues since 1979!
- Thread starter
- #7
Well, if you are having "glare" issues, I would break the T1 up into at least 4 pools.
The Legend does hunt through the trunks, but it does it in a circular manner and it always remembers where it left off.
However, it only moves on to the next POOL Choice in ARS once the lowest one is busy.
So, if the Provider has the lines hunting from 1 to 24, and you make Lines 19 to 24 the FIRST ARS choice, 13 to 18 the SECOND ARS choice, 7 to 12 the THRID ARS choce and 1 to 6 the FIRST ARS choice, it would be rare that your 1st 6 lines would ever be used for out going. (Depending on the number of extensions you have and other factors.
Prior to all these PRI's being sold, I used to do that a lot.
The Legend does hunt through the trunks, but it does it in a circular manner and it always remembers where it left off.
However, it only moves on to the next POOL Choice in ARS once the lowest one is busy.
So, if the Provider has the lines hunting from 1 to 24, and you make Lines 19 to 24 the FIRST ARS choice, 13 to 18 the SECOND ARS choice, 7 to 12 the THRID ARS choce and 1 to 6 the FIRST ARS choice, it would be rare that your 1st 6 lines would ever be used for out going. (Depending on the number of extensions you have and other factors.
Prior to all these PRI's being sold, I used to do that a lot.
dagwoodsystems
Programmer
E&M Wink--the defacto signalling standard for "vanilla" T1 trunks--should keep glare at bay, making the hunt direction almost a non-issue.
As stated previously, PRI hunting is usually specified by the hardware vendor via interview or questionnaire form provided by the carrier. Two-way Forward Hunting (low to high) is known as 2WF in 5ESS language or ACEQ in Nortel DMS language. Two-way Backward Hunting (high to low) is known as 2WP or DSEQ. Again, the references are for 5ESS and DMS respectively.
A less popular form of hunting chooses the least busy trunk first (known as MIDL). Another is Uniform Call Distribution or UCD, which hunts in a circular fashion. The UCD technique is only available on the 5ESS and is known as FUCD or BUCD (moves through the circular hunt in a Forward or Backward manner).
I don't know if that answers your question or not, but at least you are now armed with some "Telco speak".
Tim Alberstein
As stated previously, PRI hunting is usually specified by the hardware vendor via interview or questionnaire form provided by the carrier. Two-way Forward Hunting (low to high) is known as 2WF in 5ESS language or ACEQ in Nortel DMS language. Two-way Backward Hunting (high to low) is known as 2WP or DSEQ. Again, the references are for 5ESS and DMS respectively.
A less popular form of hunting chooses the least busy trunk first (known as MIDL). Another is Uniform Call Distribution or UCD, which hunts in a circular fashion. The UCD technique is only available on the 5ESS and is known as FUCD or BUCD (moves through the circular hunt in a Forward or Backward manner).
I don't know if that answers your question or not, but at least you are now armed with some "Telco speak".
Tim Alberstein
When using PRI, GLARE would be next to impossible because the CO switch and the CPE "communicate" over the DCH before a channel is selected. So during call set up the two "agree" on what BCH is selected.
One purpose of GROUND-START lines/trunks was to reduce or eliminate the GLARE problem, which it did in elctromechanical systems, but sort of came back when electronic and microprocessor controled PBXs showed up on the scene. That was primarily because of timing issues in the software. So the low-to-high and the high-to-low options were added to compensate. Most of this applies to the "LINE" side of the CO switch.
On the "TRUNK" side, there are different "hunting" options available. As Tim has mentioned some of those are available for both types, but the LECs don't always make all those choices known or available to subscribers.
I like the round robin hunting format for outgoing calls because all the trunks get a chance of being used and is easier to spot a bad one.
....JIM....
One purpose of GROUND-START lines/trunks was to reduce or eliminate the GLARE problem, which it did in elctromechanical systems, but sort of came back when electronic and microprocessor controled PBXs showed up on the scene. That was primarily because of timing issues in the software. So the low-to-high and the high-to-low options were added to compensate. Most of this applies to the "LINE" side of the CO switch.
On the "TRUNK" side, there are different "hunting" options available. As Tim has mentioned some of those are available for both types, but the LECs don't always make all those choices known or available to subscribers.
I like the round robin hunting format for outgoing calls because all the trunks get a chance of being used and is easier to spot a bad one.
....JIM....
dagwoodsystems
Programmer
Technically, the Magix software does not bond the trunk number with a specific PRI B-channel. So even if you always seized 805 (for example) as the first outgoing trunk, the actual channel that the call goes over will be any one of the available 23 B-channels.
Although it appears to be programmed this way, there is absolutely no one-to-one correspondence between the Magix line/trunk number and the carrier's bearer channels.
Tim Alberstein
Although it appears to be programmed this way, there is absolutely no one-to-one correspondence between the Magix line/trunk number and the carrier's bearer channels.
Tim Alberstein
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question
