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!

Turning up a T1 with Frontier as the carrier.

Status
Not open for further replies.
May 2, 2010
86
US
I have a IPO 8.1.69. My settings are NI2 Pri, ESF,B8ZS, all 23 channels are in service and are idle. The carrier has the inbound calls working but can't make any outbound. They want me to change from National to Unknown. I can't find any setting to change that. The carrier is using a DMS10. if that makes any difference.
 
add this to no user source

NI2_CALLED_PARTY_TYPE=UNKNOWN

this will solve the problem with the pesky Nortel DMS10 outbound
 
Thanks for the reply. I tried that and it didn't make any difference. When the call is returned it displays number busy.
The carrier found a bad card at the central office and replaced it, made a test call and watched the call on channel 23 and it sits there for 15 seconds and then I get the waiting in line, they made a change and now it's back to number busy. I am getting a cause code 28 on the system trace.
 
Cause No. 28 - invalid number format (address incomplete).
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.

Maybe you should or shouldn't be sending the digit 1 as the lead digit when setting up calls over the D-Channel?
 
try this, as you stated the co switch is a dms10 on the t1 setting at switch type, change from NI2 to DMS100 and give that a try.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
I would bet that this is a carrier issue,have them come on site with a t1 tester and prove to you that it can make outbound calls.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
also how is your ars built for this? please post

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Right out the box:
Code Telephone Feature Ln Group ID
11 911 Dial Emergency 0
911 911 Dial Emergency 0
0N; 0N Dial 3k1 0
1N; 1N Dial 3k1 0
XN; N Dial 3k1 0
xxxxxxxxxxx N Dial 3k1 0

The Line Group of the T1 are both 0 on both in and out bound.
 
carrier issue!

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
just changed the IPO to DMS 100 and had the code programmed on the no user source and was able to make a couple of calls out. Thanks for the help.
 
I suggested that earlier and you stated that did not work so it must of been the code piece

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
your right, I tryed the DMS100 setting before they changed out the card at the co. I put the code in last night but didtn't change to DMS100 with the code till this morning.
 
so we change back to NI2 Pri and again can't make a call out. On monitor trace the type=National. When i am able to place a call it uses the type=unknown. Is there a way to override the NI2 protocol to make it type=unknown?
 
if this was cm I would say yes. but go back to the carrier and have them reprovision the pri.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Why have you changed it back if it was working?



"No problem monkey socks
 
Because after I hang up on a call the T1 drops. If we let it sit long enough with no traffic on it the T1 Drops. The Providor is provisioned for NI2 pri on a DMS10 curcit.
 
you really need to complain to the pri provider, insist on a site visit to prove that the pri is able to call out bypassing the ip office

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
had a similar issue with Century Stink They had to come out and replace the smart jack three times as well as card swaps on their side all of it was on a DMS10

let us know what happens with this
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top