atcomsystems.ca/forum Forums Wiring - Telecom Carriers - Trunks & Services T1's, CSU's and DSU's T1 Channel Bank Question

Well, if it is not cofigured to emulate loop start trunks, it "hunting" could simply be sending DNIS to the next available channel.


You could have make the entire system work with a Merlin Magix, a T1 card, and a Merlin Messaging. Use DNIS to indicate the number dialed, instead of sending it to a particular channel, and the Magix would route the call to the appropiate mailbox. You could have 12 calls at a time to the same number (only because 12 ports is the maximum for Merlin Messaging - other voice mails could have a larger number of ports). 0-out to an external number can be handled with a phantom extension remote call forwarded to the outside number.

Any number of "real" phone systems could handle what you've cobbled together, and still don't have working yet.

I tried 773-724-2063 and also 867-5309 . Niether one worked . :shrug:

Again, so sorry. These fools at XO issued me phone numbers that do not reflect my current area code. For emergency 911 reasons, they had to issue me new numbers and in so doing have set me back a bit. At any rate, I will reconfigure this thing and post the new number.

I appreciate your comments "Touch Tone Tommy", however like I said in an earlier post, it is a bit late in the game for me to rethink this entire project. Let's skip this IVR thing for a second because I think it may be causing some confusion. Let's instead pretend that I simply want 24 analog phones connected to the bank with each phone representing it's own individual phone number. How can I make each port on the punchdown block represent it's own number each and every time the number is dialed. So far the bank likes to throw the numbers around a bit, meaning it is not consistent.

So far, I have the T1 line itself terminated into the channel bank. From there I have an amphenol connector coming out and plugging in to this punchdown block (Pictured Here)https://www.twacomm.com/catalog/model_SPB-V.htm?sid=4E6FE8194F0CAE22C8699463387C6A79
From the block I have the lines running to a few modems and a couple of regular phones. I place calls and sometimes there is consitency and other times there is not. I would like to keep using the same equipment and if need be I can change the T1 service I have to accomodate my needs. However, before I do that I want to see if I can do some of this myself.

Ed mentioned this in an earlier post and I agree… That is coming from the CLEC switch. This is due to the manner in which the trunk groups’ “hunting” was built.

Thanks,
Bryan
Cars -n- Guitars Racin'

When T1s are ordered, some carriers make the trunk group portion more obvious than others. Having never order a voice T1 from XO, I don't know how obvious, or how much help their provisioning department provides.

When I ordered a T1 from Airespring for my company, I saw on the order form, spaces to specify trunk grouping. After discussing this with one of their techs, my boss, and my phone vendor, ESI, I figured out how it would be useful.

We have 5 groups of channels.
Lines 1 - 6 handle incoming calls for a group of 9 800 numbers. All incoming calls are hunted from the first line-up. In other words, the first call to any of these numbers goes to line 1. When the second call comes in, if line 1 is busy, it will hit line 2, and so on.
Lines 7 - 10 handle only 1 800 number, and we'll probably drop it soon.
Lines 11 - 16 have another group of 10 800 numbers, and behave similarly. These lines are dedicated for a secondary company we share the office with.
Lines 17 - 20 is for yet a third company, with 1 800 number.
21 - 24 are what we've dubbed an overflow group. When any other group's channels are completely busy, any calls to them hunt into this group. This group also has some 800 numbers we haven't assigned a purpose yet.

What it seems like has happened, is that none of this trunk grouping was defined on the initital order. While XO may not be the one responsible for performing the hunt, some carrier down the line IS. In my case, I contracted with Airespring, who is actually reselling Broadwing service, which is delivered on Verizon wires. It was with Broadwing who I had to detail my hunting scheme with, as the Airespring guy was getting too confused.

No single-T1 channel bank that I'm aware of will handle the hunting for you. Some carrier is responsible for it, and what you need to do is arrange the trunk groups. In your case it sounds like you want 24 trunk groups each with 1 line each. Each group is associated with only 1 phone number. However, in this arrangement, only one call can be handled by a particular phone number at one time - subsequent callers will get a busy tone.

On a side-note, I happen to work for a company that does call-center software, including the IVR part... and the application you're trying to build is precisely what we're good at. The others have all said that there's equipment designed specifically for this, and they're right. But I think it's easier to wrap my head around a software approach....

Sorry to get in on this thread so late, have been out of the office. I will PM you a PDF version of the manual for that Access I channel bank. 95% of everything you need to configure is printed on the flat face of the box. It does sound like you have it configured correctly, though I would have you check the dip switches at the back of the unit. There is a set of 10 DIP switches on the back right as you face the unit. They should be set as follows
1. Off
2. Off
3. Off
4. On
5. On
6. Off
7. Off
8. Off
9. Off
10.Off

The critical one to keep intermittant issues from creeping up is SW3, T1 clock source. If you have this turned on, then the Channel Bank is providing the clock, off and the clock, or T1 timing sync is coming from XO. You may not have any issues right now, but once you start placing or receiving 24 calls at a time, it tends to start giving you funky problems that are hard to track down, so just set it right up front.

Second, if XO has configured the T1 with DID's on top of the main trunking BTN, then the 4 digits you are hearing are from them, and they are routing translations for the DID's. In a PBX environment, it would tell the PBX which extension to send the Direct Inward Dial call to. Just call XO and tell them that you do not need the DID's and have them disabled, these tones will go away. The only time you would need the DID's is if you are publishing multiple numbers for your 'IVR like' system. For instance... 555-1111 is for customer service and gets one greeting or message.. 555-1112 is for Tech support and gets routed to a different, specific modem and gets a different message. If, and this is my assumption, you just publish one number, the main T1 BTN, and you don't care which channel they come in on, they all go into your software and get the same initial greeting or message, then have them disable the DID's. It will simplify your life.

You are right about rushing the job a bit. When a carrier installs a T1 circuit, there are three steps. The T1 is physically connected, usually by the LEC to a smart jack, which you have plugged into your T1 interface on the CAC. Then the 'turn up' the T1, meaning they turn on their equipment and you get a Sync with your equipment.. they can 'see' you and you can 'see' them. At this point, you can usually break dial tone and make outbound calls... even ANI the number because it is still within XO's network. The last step is to PORT the T1. This is when XO goes out to the mysterious database in the sky and tells the world that your phone numbers should find their way to your channel bank. This is the piece you were missing at first, but seems like you have crossed that hurdle.

Good luck! I will PM that manual over.