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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MICS T1 disconnects

Status
Not open for further replies.

alebe

Vendor
Mar 21, 2002
36
US
Have a Norstar MICS with T1 and local copper lines. When user calls a specifice 800 number on the T1, the call is disconnected at a specific spot in the far end AA recording. However, if user calls uses their local lines, that call is not disconnected. Could the far end AA recording be sending some type of disconnect signal? Is there something I could check on the Norstar to troubleshoot this disconnect?
 
i would go with its a issue at far end

ONLY 17 WEEKS TILL SKI SEASON STARTS
 
If you are using T1 no Pri then you have no caller Id, and many companies are now using telemarketing block devices to block calls from callers with no caller id.
This may be the reason.
 
the PRI CallerID is for incoming calls ...but you do get a ANI with T1 or any line (which is usually the billing #) sent out when calling an 800#. This goes out from your local CO even when you suppress for other type of calls.

if your CO doesnt send out the information the tollfree call will not even go thru

problem with far end setup ...is my bet too ...
 
Additional information: Caller using T1-PRI to make call to AA can dial options, however, if caller ends dialing for approximately 10-15 seconds (is listening to flight information) then the call is disconnected. I had originally thought the disconnect was occurring at a specific spot in the AA recording. But again, the disconnect occurs if the caller, using their T1-PRI only, pauses dialing for 10-15 seconds. Calls using their local lines to this same AA do not disconnect.
 
There were many known issues on MICS 4.0.
For example dialing a specific phone number would result in immediate disconnect with no ringback or busy.
Turn on detailed release reasons on your Norstar and you will see an ISDN cause code for the released call.

Nortel issued subsequent software releases to deal with lack of full PRI protocol stack support on MICS 4.0
 
Upgrade to at least 5.0. Earlier with PRI, you are rolling the dice..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top