Outbound Calls not processing on PRI 1

[norstarpro]

Hi everyone.
I have a client who has the Following setup:

NA MICS 5.0 WI 6.06
(1) PRI - 23B & 1D
NI-2 Protocol (matched by the carrier)
Framing: ESF
Line coding: B8ZS
Received digits: 4

Each morning when he arrives at the office, He finds that he cannot process outbound calls. Inbound calls process fine! He dials the outbound number. The system will act as if it is dialing, with no error code returned. However, the call simply fails and the Time & Date returns to the display.

I turned on "release reasons" to simple. I do not get any "reasons" to display on the Prime set.

This is the freaky part... He can log in to the system, clear the Event log, (which, by the way, has no events logged), and calls will process properly.
He can also reboot the system and calls will process properly.
Any help with this would be GREATLY appreciated.
Thanks,
D. McCall
norstarpro
866-985-7031 Dave McCall
Norstarpro

 

[mroberts]

Hate to say it but it sounds like software glitch of some kind. I know it's a royal pain in the butt but a re-initialization of the system might clear it. Feature * * startup and reprogram from scratch. Yikes.

MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[norstarpro]

Thanks for the tip. However, that has already been tried, with no resolution.
Any other ideas???
I'm in a pinch with nowhere to go!

Thanks in advance!
Dave McCall
Norstarpro

 

[mroberts]

How about replacing the software? That's the next step. MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[jerryreeve]

it sounds like your channel 23 may be locking up at the telco, if you have a smdr device log the calls and see if your first calls in the AM are all hanging up on the same trunk, then try two simultaneously. I know it sounds like I'm wistling in the wind but you gotta start somewhere. JerryReeve
Communications Systems Int'l
com-sys.com

 

[mroberts]

Following in the same vein as Jerry..... why not de-provision channel 23 that way you'll be testing channel 22 for viability? MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[thephoneman]

Channel 23 is the d channel...if its out of service the span
will stay down. no clocking,no d channel info. no calls.


qmoore@ameritech.net

 

[mroberts]

Oops, you're right. Losing my mind..... MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[executone]

Channel 24 is the d channel. channels 1 through 23 are the ISDN channels(B channels).
If you disconnect from Telco for more than 5 minuets it sends a alarm to the central office to rest crkt.

 

[mroberts]

Okay we'll I am right. Whew... you know I have to think on these things before I post.

Anyway, so while NOT disconnecting from the smart jack in anyway, just de-provision channel 23 so that when you try to get a 'line' out it will grab channel 22 so that if the problem is isolated to channel 23. MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[systemguru]

What is your setting for NSF Ext:none, WATS or ALL?

We have a simular issue here in So Cal. and Verizon thinks it might be a protocal issue.

Do you know what type of CO switch you are connected to?

 

[systemguru]

We are UP>>>>>>>

Verizon finally admitted that a second location in southern Cal was having the same problem starting on the same day and time.

The resolotion: Remove our business name from our Norstar system.

It seems that an update to their AT&T 5ess switch Must have occurred (althougth they are still denying it) and the business name caused extra characters to be sent with our dialing string. The business name has been on our system since June 2002 and the issue started at 12 noon on Thursday August 22, 2002.

Strange thing is that the four digits tests (traps) we had done lead them to believe was were not sending enough info.

(626) 810-2292

Hope this helps.

 

[systemguru]

We are UP>>>>>>>

Verizon finally admitted that a second location in southern Cal was having the same problem starting on the same day and time.

The resolotion: Remove our business name from our Norstar system.

It seems that an update to their AT&T 5ess switch Must have occurred (althougth they are still denying it) and the business name caused extra characters to be sent with our dialing string. The business name has been on our system since June 2002 and the issue started at 12 noon on Thursday August 22, 2002.

Strange thing is that the four digits tests (traps) we had done lead them to believe was were not sending enough info.

(626) 810-2292

Hope this helps.

 

[mroberts]

Yeah unfortunately most Telco(s) cannot accept the business name from the Norstar. They won't pass it on so outgoing calls fail.
But Norstarpro is saying that after a reboot it works fine for awhile. If it was a problem with the business name it wouldn't work at all on outgoing calls.

I am wondering though if Telco is running some kind of maintenance at night that's pulling the T down.

Norstarpro is there any update on this issue? MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[systemguru]

Mroberts:

I agree that it appears that the Telco not processing the name is unrelated, but the end fact is that since that name was on our system for 3 months prior to Aug 22, Telco must have done a service or patch update to the AT&T switch we route thru. Since Verizon was claiming it did not happen, until fixed the problem and agreed that someone had been lying to them, it is possible that the same thing is happening to Norstarpro's customer. Either way, I had told them I would let them know if we found our answer.

 

[mroberts]

Absolutely, some Telco switches haven't been updated to reject the name information so we here in tech support still get the occassional call reporting just what you did. When the Telco gets around to updating the specs on their swtiches, T-1's drop all over the place. MRoberts
mroberts@americaii.com
If you find a tip helpful, please mark it as such.

 

[DaimondCom]

Norstarpro, did you resolve this problem? I have a client that is experiencing the same problems. We are only experiencing the problem in the AM. Verizon w/5ESS, say they don't see the D-channel setup on the drop call. We have the same scenario as with the time and date on the display. We have swapped cards, reset and re-initialized.

Thanks for the input.
Lamar
lamarg@diamondcommunications.net

 

[Norstarguru]

If the carrier goes into maintenance every night at midnight and does a clear on the card for errors or schedules some sort of maintenance session you will have to reset your PRI if it loses signal, The thing that does not makes sense is that you have nothing in the network event log. Go into Link Status in the Morning with the customer and look at your B channels to see what is missing NEAR OR FAR.

John1@refurbphones.com

http://www.Refurbphones.com

I can dial into it and check it out if you have a RAD on it..

 

[teletubby5e]

well if you are served out of a 5e, then you can have them set turn a setting to yes called "cpn disc" this is calling party name discard and this will test your carrier caller id text theory. which may be valid, since i know that we send caller id ino to a customer with a toshiba, it will crash his system. but anyway i digress ....

we had a similar situation with a customer who had a norstar running 5.0 also. he replaced whatever the line card is called in the norstar, then even the processor card, we rebuilt on another dnus port out of our 5e, changed the dacs cross connects, etc. we had nortel and lucent tier 3 techs stumped. still the channels would go out of service farend (5e received disco req from the norstar) about once every 2 days.

one day, i don't know if it was coincidence or what but we changed the switch type to at&t and then back to ni2 on both sides, of course i think that he had to rebuild the routes in the norstar, but it came up and has been up every since.

and we had not done any recent bwm (code update) on the 5e any time close to this incident. one thing that the guy at nortel did allude to was something about the 5.0 code and its interoperability with the 5e switch.

sorry only one ive got

 

[BagsNYC]

Had the same problem with the BCM. Entering Business name locked up outbound call services...Whew!!