Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Silence when calling in on T1

Silence when calling in on T1

Silence when calling in on T1

Recently we started experiencing about a 10 second period of silence when calling in on our 800# (rides in on an AT&T T1).

After this silence, our ACD auto attendant answers the call fine, but that period of silence must go.

Does anyone have any ideas on this.

RE: Silence when calling in on T1

If this just started happening suddenly and nothing was changed on the system side then I would be calling AT&T to see what has changed there.

If you find a tip helpful, please mark it as such.

RE: Silence when calling in on T1

Been there done that, and their usual reply is nothing is wrong with our equipment.

Currently we are trying to set up an after hours time to test the T with a T-Berd and find out for sure whose problem it is, AT&T's or ours.

Do you know of anything on the Norstar MICS that can affect this?


RE: Silence when calling in on T1

Nothing really, unless there is an Auto attendant on the ACD that doesn't have a greeting recorded, then it would play the silence before the ACD greeting picked up the call.

That's the only thing I can think of at the moment.

If you find a tip helpful, please mark it as such.

RE: Silence when calling in on T1

What you can check is in the routing for the acd - you may have delay answer set up as step 1 if you change that to AA or announcement 001 depending on how your acd is set up.  this should take the delay off.

Hope this helps


RE: Silence when calling in on T1

Late last night, AT&T said that they are not receiving an alert message back to them to signify to generate a ring.  The T1 is a PRI circuit, and according to AT&T an ISDN type setup.  

Is there some setting on the MICS that tells it to send a alert back to the provider?

To my knowledge nothing other than enabling the PRI on the circuit was done during the cut to the new T.

Thanks for the help.

RE: Silence when calling in on T1

Check your software level on the MICS.
If it is MICS 5.0 W.I. 6.00 , ITAS has a notice out that this problem will occur . You will have to upgrade your software.

RE: Silence when calling in on T1

I just looked at the flash card, and it has:  COA-MICS-XC 4.1 S/W WI 6.04.

Is this level ok?  If so, is there anything on the MICS, that would enable the alert message back to AT&T?


RE: Silence when calling in on T1

Here are the settings for programming a PRI. Just your settings to make sure they match:The DTI card should go into Slot 4 first. If you have a second card it would go into Slot 3. One PRI code covers both cards.

To enter the software key code:
From Terminals & Sets – Next until get to software keys – Show
Sys ID – Next
Password Keys – Show
Key 1: (enter 1st key code)
Key 2: (enter 2nd key code)
Key 3: (enter 3rd key code)

You must disable the card first, program the card for PRI, then re-enable the card.

To Disable / Enable Card
From Terminals & Sets – Next until you get to Maintenance – Show
Next until get to Module Status – Show
Show module – Next
KSU (1):        Next or State if using (2) cards
KSU (2):        State
( ) Ports Busy – Press Disable or Enable
Disable at Once? – Yes

Protocols & Signaling
Hardware – Show
Show Module – Next
Cards on KSU – Show
Cd1 – KSU:        Change to PRI – Show
Card Type PRI – Next
Lines: 001-023 – Next
Protocol: SL1 – Next (check with your Telco Carrier for setting)
Type Slave – Next
Bchanseq: Ascend or Descend – Next (check with your Telco Carrier for setting)
CO Fail: TIA–547A – Next
IF Levels: ISDN – Next
Framing: ESF – Next (usually ESF, check with your Carrier
Internal CSU: ON – Next
{need to have either an external CSU or turn the internal one on. If customer needs to use some channels for data then they’ll need a CSU/DSU to split off channels before the 0X32. OR to split off data channels after 0X32 they’ll need a Nortel Data Interface (NDI) plus bandwidth allocation key codes}
DSX1 Bld: 000-100
Line Coding: B8ZS (usually B8ZS, check with the Carrier)
ClockSrc: Primary (second card would be secondary)
Users cannot access PRI lines directly through line appearances or line pools (except PRI line pools). All outgoing PRI calls are dialed via intercom using routing codes.
When a trunk card is changed to PRI, all existing line appearances for that card are automatically removed.

To Build a Route
Services – Show
Ringing Service – Next to
Routing Service – Show
Routes – Show
Show Route: 001 – Show
Dialout: No Numbr – Leave alone – Next
Use: (    ) – Change to PRI
DN Type: Public

To Build Destination Codes:
Routing Service – Show
Routes – Next
Dest Codes – Show
Show destcode: (enter code)     - Next
DstCode: (enter code) – Show
Normal: 000 – Change to route built – Show
AbsorbLength: ALL
Don’t usually have to worry about Night schedule etc.

Line Set Up
Assign each channel (001-023) as trunk type PRI, Line Type: PRI –A.
PRI Lines are always configured Auto Answer. Never Manual Answer.

Target Lines Programming:
From Lines – Show
Show LN: 145 – Show (target line range from 145-275 non-XC SW, 145-336 XC SW)
Target LN – Next
Private to: (extension number) – Next
Rec’d #: (enter digits Telco is sending) – Next
If Busy: to prime – Next
PrimeSet: 221 change to the extension # - Next
CLID Set: None – Next
Aux. Ringer: N – Next
End of list

If you find a tip helpful, please mark it as such.

RE: Silence when calling in on T1

I would look into the ACD for the way the call is presented to the ACD. Also if your PRI is working don't reinstall the keycodes (if they are not in, the PRI won't work at all). If your switch is version 4.1, try the restarting feature in the Maintenance heading. I've had problems after making many changes in the switch, "rebooting it" usually cures the symptoms. If you have a lot of incoming traffic into the switch, usually that slows the switch down, for example, if you grab an outside line, it takes forever to get dial tone, if you invoke a feature, it takes a long time for it to complete the command, it's like the phone gets "hanged" like PC's when you open windows and they stand there, and after a little while does their thing. If traffic is the problem, I'll would definetly go with something more powerful like an Option 11C or similar switch. Good luck!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close