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!

Routing DID's to AA on a MICS with a Call Pilot

Status
Not open for further replies.

chirkware

IS-IT--Management
Jan 17, 2006
80
US
The System before this project started:
MICS 7.1 with no analog lines. System is networked with another MICS via T1 (setup as PRI-A), and had no lines of its own (dialing 9 sent calls across the p2p T1 to the other MICS and out its analog line pool). Three digit extensions from 101-132 (admittedly, a mistake, but that's another story). System was getting VM from Call Pilot 150 attached to the other MICS.

This system is getting ready to get busy as ~10 collectors will be on the phone ALL DAY LONG. So, the plan was to put a PRI on this system, put in a CP150 on this system, and eliminate use of the other MICS' analog lines and call pilot (eventually the p2p T1 will go away completely). The CP150 has been put in (dn 130) and the PRI went in yesterday. The PRI is working (right now they have to use 66 to get out, as I didn't want to break 9 until I knew the PRI was working correctly, and 8 and 7 were already used for other purposes).

Now, we have 40 DID's, 555-5100 through 555-5139 (prefix changed to protect the innocent). Target lines had already been built for 101-132 so the callers from the other MICS could get in, so I did not have to build target lines (that made me happy). DID's 555-5101 through 5129 (129 is last extension in use) are doing exactly what they should.


We plan on using 555-5100 as the main number , where callers will get the auto attendant. Here's my first question: Is the following what I do to make this happen?

1) build a target line for 100.
2) Build a CCR tree and activate it on a greeting table
3) Set the target line in #1 to be answered by the AA after 0 rings.

Does that allow several calls into the AA simultaneously, or does the target line stay "busy" the entire time the first call is active?


Another Question: Once the AA is setup, we will have some toll free numbers forwarding to the new 555-5100 main number. Will I need to build target lines for them, or will the incoming calls look like 555-5100 to the system, and thus behave as if 555-5100 is dialed?
 
Yes to your first question. Yes to your second (up to 8 calls, if the vm has no one in it). No you don't need to build target lines for the 800 numbers because they are pointed to your main number (555-5100). Hope this helps.
 
keep in mind that you have to have the Callpilot ring at least two times for CLID to pass through your system...
 
Thanks guys! I can't tell you how excited I was when I found that my previous work in networking the two MICS' actually eliminated work for this task (the target lines being in place).

Norstarboy125: Are you saying I should set the Call Pilot to answer the target line after 2 rings rather than 0? Getting caller ID to work properly is DEFINITELY important to this project.


Another question I intended to ask before, but forgot: Outbound calls through this PRI show up as 555-5100 (main number) regardless of the extension. Any way to make the extensions all show their own DID (ie, call from x103 shows as 555-5103)?

Thanks!
 
-PRI does not require 2 rings...it's immediate.
-Check out OLI# under "line access" for 2nd question.
 
I think we're getting there, but the outbound caller ID is not right yet. I've set the OLI# under line access per bryontel to 8655555yyy on all sets (where yyy is the extension #), but I'm still showing 8655555100 for all outbound calls.

I spoke to the AT&T rep that built my PRI, and she says that all stations are being screened, and that caller ID is not being suppressed, so, according to her, this should work.

That leaves me thinking that I'm "the weakest link" and am probably missing something.

I did find under Hardware-->Module2-->Trunk Module-->Card1 that "Send Name Display" is set to Y. I've also set a business name under System Programming...not sure whether that was needed.

Thanks for the continued help!
 
I think Business name will override OLI so leave Business name blank, but both should override the Telco (at least they should allow it) and if one or the other does not override then issue is with the Telco.
Sometime explaining this to a the Telco repair is hard and you need to hope you get somebody who understands.

The rep cannot tell you it is not programmed, they can tell you that they requested it to be programmed.
They put is on paper but its those at the C.O. who build it to the reps liking and in this case not built right it seems.

Norstar- not guilty



 
The outbound caller ID issue is resolved, and it was on AT&T's end. I just got off the phone with testers from AT&T's provisioning department, and when I mentioned other techs had told me that they had double and triple checked that the DIDs were setup for screening, one of the techs online actually looked at the screening table, and it was....(drum roll please)...BLANK! Within five minutes, all 40 DIDs were in there and I was calling my cell and had the right number showing up on its screen.

Thanks so much for everyones help! Tek-tips.com is a GREAT resource for those of us who are trying to be experts at everything (two weeks ago, I was replacing an LCD screen on an ATM machine, next week, I'll probably be building a Windows server...lol). Jack of all trades...master of none. :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top