BCM 450 PRI issue

[4allcom]

I have noticed that they have deleted the protocal NI and replaced with NI2. Problem is my provider says the can only provide NI at this time. Is there a patch?

 

[gberger]

I have installed 3 Bcm450 lately and all 3 with DMS100(NI-1).What options do you have in Ressources-PRI?
Are you in North America?

 

[4allcom]

I have NI2, DMS100, DMS250 and 4ESS what got me was the release 3.6 that I am replacing has NI, DMS100, DMS250 and 4ESS.

 

[gberger]

DMS100 is NI-1 so just select this one and it will work.

 

[4allcom]

I will give that a try, Thank you.
It was just bugging me why release 3.6 has NI and DMS100 and the BCM 450 did not.

 

[4allcom]

Well changing to DMS100 did not work just changed to way it worked. Instaed of incoming and no outgoing I have outgoing but no incoming. I guess I will have to get with the provider and they will have to change or I will have to get a new provider

 

[telcodog]

If you are set to DMS-100, B8ZS and ESF, then you shoud be good to go. This stuff is pretty basic these days. If you can get outgoing calls, then you are probably set up correctly. I don't know what your level of expertise is so forgive me if I start with the basics.

Given this is your connection to the PSTN, are you set to receive the correct number of incoming digits? If so, do you have target lines set up to direct the call where you want it to go? Have you fired up the BCM Monitor to see what the provider is sending you? Don't forget your clocking either. You should be set to Primary-External.

If that's all set correctly, then definitely get the provider on the line and grill 'em. I once had a site where the carrier swore up and down they were all set correctly and kept insisting to the customer that the issue was with the phone switch. I even brought in a PRI tester to prove the problem was with the network but they still wouldn't believe it. Turned out to be Virtual Groups set up on the PRI from the carrier. These are set up to restrict the number of simultaneous inbound calls so there are always outbound paths available. In my case, they had one virtual group forwarding to another for some reason and the calls never did make it to the PRI. This resulted in the customer having the ability to make outbound calls but nothing inbound. Funny thing was, the guys at the test board always showed the calls routing to the correct circuit, so don't let them off the hook too easily.

Good Luck with it.

 

[4allcom]

This is an existing installation, they have a BCM 400 rls 3.6 there working already. I am trying to replace with a BCM450 because they have outgrown the BCM 400. I am 100 % positive the programming is correct. If I set up the PRI on the new BCM to NI2 because IT doesn't have NI I can call in but cannot call out. If I change it to DMS100 I can call out but I cannot call in. I get the same if I change to DMS250. If I change to 4ESS I can call both ways but the caller ID is screwed up.

 

[foneman1]

leave it at NI2. Remove business name, and or uncheck send name option (try one or both), then try to call out. Good luck.

 

[telcodog]

OK, I'll bet that your 3.6 is set to NI-2 if it works both ways with 4ESS. It wouldn't surprise me if it is also set up for Call by Call Services. If that's the case, and if you don't need to identify the type of service, I would ask the carrier to set it to NI-1, get rid of the call by call stuff and set the 450 to DMS-100. Unless your provider is using some really old equipment, this set up is the most common in North America.

This call by call stuff can get really confusing too, if that's what you have set up. You can download the manuual from the 3.6 (The Programming Operations Guide) and do a search on NI. You'll probably get about 50 hits so there's a lot of information in there describing what all this stuff is and how it all works.

Who is your provider by the way? at this point, you really need to find out what line protocol they are using.

 

[4allcom]

Thanks for all your help, I will try more things tomorrow. Also on the old BCM it is set for just NI there is not a NI2. our carrier is verizon. we are waiting for them to see how the circuit is set up.

 

[telcodog]

That's correct. In 3.6 the NI option covers both 1 and 2. Here's something from the 3.6 Manual.

Protocol
NI, DMS100, DMS250, AT&T4ESS, SL-1, Euro, ETSI Q-Sig

Choose the trunk protocol used by your service provider.

The supported protocols are:

PRI-T1: NI (NI-1 and NI-2), DMS100, DMS250, AT&T4ESS, SL-1

PRI-E1: ETSI QSIG, Euro, SL-1

Note: SL-1 and ETSI QSIG require an MCDN keycode to display.

BRI: Protocol can also be selected on BRI T-loops under the Services/Telephony/Loops
heading.

Note: Always check the line protocol with the central office.

Protocol type
User, Network PRI
When you select SL-1 protocol, an additional setting, Protocol type, appears.
SL-1 protocol is a private networking protocol. This allows you to designate a Business
Communications Manager node as a Network (Master). The default setting is User (Slave).
In public network configurations, the CO is generally considered the Network side or
Master.
Applies to SL-1 protocol only.

NSF
Extension

None, WATS, ALL

PRI
The Network Specific Facilities (NSF) information element is used to request a particular service from the network. Settings are based on the type of switch to which the line
connects.

Suggested settings:
DMS100/250: NONE
Siemens ESWD, Lucent 5ESS: WATS
GTD5, DMS10: ALL

When you select NONE, the NSF extension bit is not set for any service.
When you select WATS, the NSF extension bit is set for unbanded OUTWATS calls.
When you select ALL, the NSF extension is always set for all CbC services.
Appears only for NI protocol.

B-channel selection sequence

Ascending
Sequential

Descending
Sequential PRI

Defines how B-channel resources are selected for call processing. For more information,
see “PRI B-channel provisioning” on page 142.

 

[4allcom]

I am 100% on the programming, I know I have it right but it just doesn't work right. I can have the 400 and the 450 programmed the same and the 400 works and the 450 does not.
Is it possible that the protocol is set up NI1 on the circuit and the 450 will only do NI2?

 

[telcodog]

The 450 will do both. DMS-100 and 250 are both NI-1. I think foneman might have your answer though. Your provider might not be able to handle you sending the name and I believe that option is checked by default on the 450. You really should verify with Verizon what they have set for line protocol on your circuit.

It's been a while since I actually had to look at the PRI setings on a 3.6 and I can't recall what shows up for the protocol on the MBM configuration. Does it actually specify NI-1 or 2 or just NI? Something tells me that the setting is NI and the software handles whatever the provider sends but in the new stuff, you have to specify. That's just a guess though.

 

[4allcom]

I will try that out tomorrow, Sometimes these things make me think I am crazy!!

 

[4allcom]

Ok Here is what is happening now. I have removed company name and now it does have outgoing and incoming. The only problem now is with the OLI. No matter what I have in there it calls out with a diferent number and we don't even know what it is to. Help.

 

[4allcom]

I forgot to mention that the BCM 3.6 that is in place works perfectly. I don't see where it is a phone company thing unless it is back to a protocol thing.