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!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What PRI protocols do I specify to new 800 provider? 1

Status
Not open for further replies.
OrangeMonkey

OrangeMonkey

IS-IT--Management
Jan 4, 2007
67
US
I have a Nortel Meridian I option 11C switch. We recently switched providers and we are having trouble with incoming 800 calls. The new provider asked what our PRI protocols were so I asked Level(3). I was informed that we were NI1 or NI2 and 4 digits. 5e standard. Obviously we can't be NI1 and NI2... right? When we cut over our switch did not immediately accept the incoming calls. Then we discussed the possible options. The provider changed the setting from NI2 to NI1 and things improved. We thought all was OK. That was on Sept 25, 2008. On the 10th of October we realized that some 800 calls were failing with CAUSE#31 NORMAL UNSPECIFIED. We have since omitted the caller ID on all calls and it seems to have made things better but some 800 calls are still failing.

My question is what other specifications would be involved in getting the new provider hooked up? Remember it's only the forwarded 800 calls that are failing. The provider D&E Communications receives the 800 calls from a third party. They claim they can change settings before they send us the call. Which settings are they manipulating for only the forwarded 800 calls and where do I look in my switch to see what settings we have? Do they have the ability to control only the 800 calls. With Level(3) we received caller ID on our normal calls but didn't see the calling number for 800 calls. Can my provider be specific in controlling this and can this setting cause the calls to fail?

I have been weighing rebooting the switch which wasn't done after cut-over. I hesitate fearing a worse situation if everything doesn't come back up.

Thanks for your comments.
 
Sort by date Sort by votes
You have indentified the problem to be with Verizon. You can't fix thier problem from your PBX!

Have you contacted Verizon?


 
Upvote 0 Downvote
marcuspb, I believe my PBX is working too. But it's not just Verizon cell phones. Some calls to our 800 number do complete and some don't. I have been trying to understand what I need to tell my provider as far as NI1 or NI2 number of digits and so on. So that they know how to package the calls. All calls work except SOME of the calls to our 800 line. The technician at D&E says he makes changes but won't explain what he changes. He does test calls and they work (naturally) and he says lets see how this goes. We wait a while and continue to have calls that fail. I call him back - he says OK I made another change - lets see what that does. This has been going on since the 10th of this month. I was hoping to be able to tell him all the parameters required for my PBX and when the calls failed I could say it's his or the third party 800 company's fault.

From what I hear from you guys, it's not my problem but how do I convince the provider it's their problem?
 
Upvote 0 Downvote
You might be stuck using the "If you don't fix it, we're switching carriers...we didn't have this problem before" method.

Or - if you are a sizable company, have a Corporate Lawyer send a letter or a call to a very senior position at the carrier, challenging the contract and threatening that they start paying you for lost business.

It will suddenly become urgent...to the point they will have someone on your site with a T-Berd the day you tell them "our Legal Department is all interested in this problem now"


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
 
Upvote 0 Downvote
I appreciate the fact that it's probably something my provider could solve. The question is if they need to change their setup but don't know which things to change how can I help them? I have the programming notebook the installer used to setup our switch. I am reading the OVERLAY 16 Trunk Route Data Block Info. It says the IFC for the T-1 is NI2. D&E had their switch set to NI2 at cutover on Sept 25 and my switch would not accept any incoming data. D&E changed their setting to NI1 and we started receiving data and we thought all was good to go until Oct 10.

If I could get their engineer on the phone which pieces of information would I need to give him to be sure they have their switchgear compatible with ours?

D&E now has the 800 company engineer in the loop. What could I share with them to help get this working?
 
Upvote 0 Downvote
I would share this" you are wasting my time and yours, get it fixed and dont send a bill until it is" Personally, I would change back to your original carrier, despite any savings! You are NI2, they are filling you full of SH*T... All Telcos are terrible, some just worse than others.... I always thought AT&T was the worst.......
 
Upvote 0 Downvote
I have tried to follow as much as I could from all the messages. One thing to keep in mind with PRI, the protocol must be the same at both ends. If the carrier is NI2 then you must be NI2, if the are not then you must match what they are using for a custom setup. If the protocols are not the same you will probably not get this to work correctly. You stated that when the carrier was NI2 you had some trouble getting calls to work. One reason could be the CO_type prompt in your d channel data block must be correct. If the central office you are connecting to is anything other than an ESS5/4 then it is set corretly. However if the central office is an ESS5/4 you must change that prompt to ATT. This could be one of the reasons why the forwarded calls are not working. They will be including and extra information element in the setup message for a redirected call and the pbx may not be processing them correctly. Also if you make any changes to the d channel data you must do a foreced download to the msdl card or the changes do not actually get sent to the card.
 
Upvote 0 Downvote
When you stat PRI in LD 60 do you have 3VCE next to all the channels?
If not this could be your problem.
 
Upvote 0 Downvote
If all the calls work fine but the only problem you are having is with the 800 #’s company they may be set up using 3.1 kHz signaling and if your route is set as VOD or VCE this will explain your problems.
You would have to rebuild your and as 3VCE.
 
Upvote 0 Downvote
you can chg the route without rebuilding it, his route is VCE, not 3VCE... good catch
 
Upvote 0 Downvote
OK, I just did a stat in ld 60
CH 01, 02, 03, 04, 06, 07 = IDLE DID VCE *
CH 05, AND 08 THRU 23 = FE MBSY DID VCE *
CH 23 = DCH 0

CO_TYPE = STD
The only other option is ATT

If I have to change the CO_TYPE how do I force the download into the card?

Thanks
 
Upvote 0 Downvote
StoneColdphoneman,

My PRI is VCE = voice-only route. 3VCE = Voice route and 3.1 kHz. If I change the DSEL to 3VCE will it take effect right away or do I need to reset anything?

My manual says I'm only prompted for the DSEL if DGTP = DTI, DTI2 or JDMI. My current setting for DGTP is PRI = ISDN 23B+D

So it doesn't look like I will be asked to change the DSEL unless I change the DGTP.

Any Suggestions (Beside call in the BIG GUNS) By the way I called Verizon and they won't help on my end even though it is their copper. They say our number is serviced by GTE !!!! Does anybody have a number for GTE in York, PA?
 
Upvote 0 Downvote
GTE is Verizon, Verizon bought them 10 years ago. Your DSEL showed up in your PRT so you should be able to change it and there is nothing to reset after you do.
 
Upvote 0 Downvote
OK, I just changed the DSEL for ROUTE 0 to 3VCE and did an LD 60 STAT all channels are as I discribed above except now they say 3VCE where they said VCE before.
I have the LD 96 MSGI 0 and MSGO 0 running to the printer.
 
Upvote 0 Downvote
Because if the 800 number use the 3.1 kHz signaling his route will disconnect the call or have very long delay since he was using VCE That’s why G.
 
Upvote 0 Downvote
I went back after dinner and checked the printout. Some of the 800 calls are still failing. As I stated before the diags says CAUSE#31 NORMAL UNSPECIFIED. Does anyone know what CAUSE#31 would be? As far as me making test calls, my cell phone with ATT always works.

Let me ask again. If you were going to put in a new PRI for me what bare bones information would you ask me about my switch so that you came close to getting it right the first time.

My provider asked me two questions. Was I NI1 or NI2 and how many digits should they send.

I said NI2 and 4 digits. It didn't work with NI2 so they changed it to NI1 and it seemed to work.

Thanks and have a happy turkey day!

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

phoneswitchnewbie
  • Locked
  • Question
Map extension to outgoing 800 number 1
Replies
6
Views
156
phoneswitchnewbie
phoneswitchnewbie
lexer
  • Locked
  • Question
Meridian 11c and asterisk interconnection using PRI
Replies
7
Views
271
RS528
RS528
22NC
  • Locked
  • Question
Customer upgrading network switches. How to do a graceful switch
Replies
3
Views
170
Firebird Scrambler
Firebird Scrambler
CentralJIM
  • Locked
  • Question
no caller ID on PRI external call
Replies
5
Views
247
CentralJIM
CentralJIM
telepath
  • Locked
  • Question
Lost E1 PRI link
Replies
1
Views
119
Firebird Scrambler
Firebird Scrambler

Part and Inventory Search

Sponsor

Back
Top