Inbound Primes Fast Busy

[ParkView]

I have a BCM400 v3.5 and we ran a DR test last weekend to test the unit. The only time the primes go active on the unit is when we do a DR test. The problem we discovered was that when we called in on the main number for our primes we received a fast busy on the calling end. We know that the primes really did become active on the BCM because when we called out from the prime set the phone number that showed up was the main number for the primes. I did verify that pool PRI-A was attached to the prime set and this makes sense because dial out worked fine. Any thoughts on where to look in programing for outbound fine, inbound fast busy would be appreciated.

 

[acewarlock]

Did you program the target line to the phone's, if not you'll get a busy.

 

[biv343]

Check the prime set on the PRI lines - inbound calls should at least ring to the prime set. If the prime set configured on the lines doesn't exist, you'll get a busy.

Once that's done, check your target lines as ace mentioned.

 

[acewarlock]

I had this problem only once with XO COMM, I was set fot NI1 and so were they, but it didn't work until they changed to NI2

 

[56BelAir]

sounds like your signaling is off. Are you sure you have a 23 channel pri or 24 channel T-1. If its just a t-1 you need to change your bus settings accordingly ESF, B8s and possibly auto answer if its a T-1.

 

[biv343]

If he's dialing out through PRI-A, we know he has a PRI and not a DTI/E&M T1.

Ace - ran into that same thing once with the CO. The BCM only does NI-2. Argued with the telco for about an hour before I could convince them to change it.

 

[ParkView]

I looked at the ISDN PRI settings and they are correct. I see in the programing that the DID numbers are assigned to target lines in the BCM. However, I do not see the main number assigned to a target line anywhere. Is what I consider the main number truely different than DID numbers or should I just look at it as another DID? My thought is that I need to assign this number to a target line. We also proved that these DID numbers do ring through to voicemail so the incoming fast busy issue really does appear to be for the main number.

 

[acewarlock]

When you say Main Number do you mean the first DID number in the range?

I assign the first DID number to target 241 and put 8 app of 241 on the Recpt phone.

 

[biv343]

Sounds like your main number isn't a part of your DID block - typical if numbers get ported over to the PRI.

To answer your question, yes, you'll want to build a target line with the received digits that match your main number (such as 5551234). Assign that line to the phone and you're set.

But, if the prime set of the PRI trunks is set to an extension of your receptionist set, you would still get inbound calls without a target line - you'd see Line 61 to Prime or something similar to that in the display.

 

[ParkView]

Biv343, I agree with you. The receptionist phone has a single DN of 7000. This is the prime set of the PRI trunks. In BCM monitor we believe we see the beginning of a connection but it drops instantly. To me this explains the fast busy on the main number because it does not know how to get to the prime set. However, from my understanding and from what you are saying this should just happen. Again, it appears that all of the DID functionality is working fine and all outbound calls work fine. More thoughts. BFT was recently replaced for the cap issue. Vendor did no BCM configuration work after replacing. Is it possible it could actually be related to this somehow? Last four of main number is 7171 and DN range is 7000-7015. Is it possible there is a 7xxx conflict somehow? If I try and make a target line for the 7171 number I get an error stating "not a valid option for public number.

 

[biv343]

Replacing the BFT shouldn't affect any telephony programming.

Not being able to add 7171 as a target line typically points to a target line already built with those digits, or a access code/destination code built that starts with 71 (or includes 7171 already).

Might need to break out the shovel and start digging.