BCM 50, New PRI, delayed ringing 1

[slimwhit]

Hi;

I might be a little over my head here, but here's the issue nonetheless:


Background: BCM-50, T-1 PRI with 6 blocks of DID's. Installed 10/2004. Been working mostly without any incidents. I have a telecom and IT background, but have never been a "phone guy". Becasue the company that sold me the BCM and a long-term maintenance agreement has gone paws up, I have very limited support. I've managed to keep things going until now.

Catalyst: Originally had a shared T-1 with 12 lines split/out or dedicated coming into the BCM as PRI. This was from "Carrier C". Because of growth, etc, we needed more internet capacity, so I went to "Carrier L", who assured me that this would be a smooth transition, nothing to worry about. Carrier L is providing a Bonded T-1 solution (2 T's) with a "dynamic" PRI option. I have up to 16 lines available (more if I need them later). The Internet portion of the service will dynamically adjust according to the number of in-use lines.

Conversion: Everything did go pretty smoothly. Outbound Calling OK, Inbound calling mostly ok (see below), CLID ok, Internet OK. A few issues with LPN/NPAC and smaller carriers not updating LRN information, so those calls can not come in. There is one issue that remains.

I made no changes to the BCM through this process. Just unplugged the Telco side of the PRI connection from Carrier C's equip and put it into Carrier L's equipment. Carrier L ported the numbers and the 60 DID's came up.

The problem is that previously, if I recieved (or the receptionist) recieved an inbound call on our DID, and another call came in behind it, we would see / hear it ring on our set. Now, the second caller in this situation hears 5 rings before it appears / rings on the set.

I do know for a fact that it was ringing immediately prior to this cutover. Carrier L is claiming that there is no way that it could have, unless I changed something on the BCM.

One contact I have suggested that I put another Target line on each set. I'm not sure that I know exactly what that means, but I set another line to appear and ring on a couple of sets as a test, and that did not solve the issue.

Carrier L says that they provide no "ring back" through thier switch, so the caller is hearing a ring provided by the BCM. I can believe this.

It is my belief that there are different settings possible on either the Head-End equipment, or in the PRI itself that is delivering the call in a slightly different way than it was on Carrier C -- and this is what is causing the nortel to ring 5 times before putting it through to the set.

Any thoughts? Any thing that I could try?

I thank all for any help that you offer.

Best,

Slim

 

[Deweyhumbolt]

Are you sure it's not happening on the first call also. If the recvd. digits are not matching up with telco, the DRT (Delayed Ring Transfer) feature would still deliver it to the set, but delayed.

Adversity is Opportunity

 

[slimwhit]

Hello, and thanks.

No, when I call in as the first call, it appears and rings straight-away.

Thanks again,

Slim

 

[pccal]

How many appearances of the Target line do you have on the receptionists set? Is this only a problem on the main set or is it on all sets with target lines?

 

[slimwhit]

Hi;

It's on all sets. The receptionist set, and all the other sets have one target line, and a prime line set to the intercom.

I think that I've found a solution --- I dropped DRT down to after one ring instead of 4. Might there be repercussions from making this change that I have not contemplated?

I do have a question regarding "how it worked before" and "why it doesn't work after the cut". If anyone has ideas re: PRI or Telco equip settings, I'd welcome hearing them. Things that I don't understand or can't solve really, REALLY bug me.

Thanks again!

Slim

 

[bluemr2]

You need to open BCM Monitor and take a look at the lines. See if the digits are hitting a line immediately or if takes 4 rings to see it. DRT being 1 ring WILL cause problems. All lines will ring the prime set after just 1 ring. Try setting the target lines to ring only. It might be a problem that you only have 1 appearance of the target line, and it doesn't hit the prime set until the DRT timer expires. Also if they want line appearances add a couple more and see what happens.

 

[DBrewsky]

When the first call comes into the recpetionist, what line are you on? If the CLID info is displayed, press INFO then MORE.. If you see a line number that is Line 235 and below, then your carrier isn't sending the correct number of digits.. BCM Monitor, as stated in a previous post, would be your best option in seeing whats happening. Just run the program, then click on the UIP tab, select BUS 7 (assuming BUS 7 is your T1), then click on PRI (I would unselect the timer function). Once this is done, make an inbound call and see what the information says.. You should see the exact digits sent by your provider...

One thing as well, you can increase your public received digit length without it erasing any, but if you set it to a lower number, it will automatically erase any public received digits that are greater than the number of digits you have selected the system to receive...

--DB

 

[nooop]

How about fwd buzy to voicemail DN? That is how I set it up because I always have two line appearances, set the prime set to itself and set if buzy to prime. You may like how easy this change is to make on a user basis, it is not as global as the other ideas I have read so far.

 

[slimwhit]

D Brewsky: Thanks for that post. I've been using BCM Monitor, but only the line monitor.

Here's the output from an inbound call to a DID:

I think from "number digits", it looks like it's sending 4 digits (which is what I have the BCM set to look for). Am I looking at this right?

I *so* wish that I had known about this before the cut and had the foresight to grab a capture on the old Carrier.

Thanks again!




[PRI - Bus 7]
[15:44:44 > CC < CRef Origin: CRef 223 SETUP 4025 6103756289]
[Bearer capability - Speech - G.711 u-law]
[Information Transfer Capability: speech]
[Coding Standard: CCITT standardized coding]
[Information Transfer Rate: 64 Kbits/s]
[Transfer Mode: circuit mode]
[User Information L1 Protocol ID: Recommendation G.711 u-law]
[Layer and Protocol Identification: User Information L1 Protocol]
[13 00 81 90 00 00 A2 ]
[Channel identification - B-Channel 1]
[Information Channel Selection: B1 channel]
[D-Channel Indicator: channel identified is not the D-channel]
[Preferred/Exclusive: exclusive - only the indicated channel is acceptable]
[Interface Type: primary rate interface]
[Interface Identifier Present: interface implicitly identified]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : Channel 1]
[0D 00 A9 00 83 00 01 00 01 ]
[Called party number - Unknown/Unknown - 4025]
[Numbering Plan Identification: Unknown]
[Type of Number: Unknown/Reserved Value]
[Number Digits: - 4025]
[03 00 80 00 04 00 04 0A 02 05 ]
[Calling party number - E.164/National - 6103756289]
[Numbering Plan Identification: ISDN/Telephony numbering plan (Rec. E.164)]
[Type of Number: National Number]
[Screening indicator: User provided, not screened]
[Presentation indicator: Presentation allowed]
[Number Digits: - 6103756289]
[07 00 21 80 0A 00 06 01 0A 03 07 05 06 02 08 09 ]
[15:44:45 < CC > CRef Origin: CRef 223 CALL_PROCEEDING_CC]
[Channel identification - B-]
[Information Channel Selection: B1 channel]
[D-Channel Indicator: channel identified is not the D-channel]
[Preferred/Exclusive: exclusive - only the indicated channel is acceptable]
[Interface Type: primary rate interface]
[Interface Identifier Present: interface implicitly identified]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : ]
[0D 00 29 00 83 00 01 00 81 00 ]
[15:44:45 < CC > CRef Origin: CRef 223 ALERTING_CC]
[15:44:51 > CC < CRef Origin: CRef 223 DISCONNECT Normal]
[Cause - Normal]
[Location: Public network serving the local user]
[Coding Standard: National standard]
[Cause Class: Normal Event]
[Cause: Normal clearing]
[05 00 82 00 90 ]
[15:44:51 < CC > CRef Origin: CRef 223 RELEASE_CC]
[15:44:51 > CC < CRef Origin: CRef 223 RELEASE_COMPLETE]
[15:45:00 < CC > CRef Origin: CRef 21F DISCONNECT_CC Normal]
[Cause - Normal]
[Location: User]
[Coding Standard: CCITT standardized coding as described below]
[Cause Class: Normal Event]
[Cause: Normal clearing]
[05 00 80 00 10 00 ]
[15:45:00 > CC < CRef Origin: CRef 21F RELEASE]
[15:45:21 > CC < CRef Origin: CRef 224 SETUP 4025 6103756289]
[Bearer capability - Speech - G.711 u-law]
[Information Transfer Capability: speech]
[Coding Standard: CCITT standardized coding]
[Information Transfer Rate: 64 Kbits/s]
[Transfer Mode: circuit mode]
[User Information L1 Protocol ID: Recommendation G.711 u-law]
[Layer and Protocol Identification: User Information L1 Protocol]
[13 00 81 90 00 00 A2 ]
[Channel identification - B-Channel 1]
[Information Channel Selection: B1 channel]
[D-Channel Indicator: channel identified is not the D-channel]
[Preferred/Exclusive: exclusive - only the indicated channel is acceptable]
[Interface Type: primary rate interface]
[Interface Identifier Present: interface implicitly identified]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : Channel 1]
[0D 00 A9 00 83 00 01 00 01 ]
[Called party number - Unknown/Unknown - 4025]
[Numbering Plan Identification: Unknown]
[Type of Number: Unknown/Reserved Value]
[Number Digits: - 4025]
[03 00 80 00 04 00 04 0A 02 05 ]
[Calling party number - E.164/National - 6103756289]
[Numbering Plan Identification: ISDN/Telephony numbering plan (Rec. E.164)]
[Type of Number: National Number]
[Screening indicator: User provided, not screened]
[Presentation indicator: Presentation allowed]
[Number Digits: - 6103756289]
[07 00 21 80 0A 00 06 01 0A 03 07 05 06 02 08 09 ]
[15:45:22 < CC > CRef Origin: CRef 224 CALL_PROCEEDING_CC]
[Channel identification - B-]
[Information Channel Selection: B1 channel]
[D-Channel Indicator: channel identified is not the D-channel]
[Preferred/Exclusive: exclusive - only the indicated channel is acceptable]
[Interface Type: primary rate interface]
[Interface Identifier Present: interface implicitly identified]
[Channel Type/Map Element Type: B-channel units]
[Number/Map: channel indicated by number]
[Coding Standard: CCITT standard as in Recommendation Q.931]
[Channel Number: : ]
[0D 00 29 00 83 00 01 00 81 00 ]
[15:45:22 < CC > CRef Origin: CRef 224 ALERTING_CC]

 

[pccal]

Slimwhit, Give your receptionist more than one appearance of the target line in question. Don't play around with yout DRT to Prime. Setting for target line should be private to the extention it is assigned to, if busy to prime & prime to the extention it is assigned to.Target line is than assigned to extention to appear & ring with as many appearances as you wish. Even if you only have one appearance the second call should come in on the intercom.
It is easier for a receptionist to have at least 6 appearances of the target line.

 

[DBrewsky]

What does the display say when a call comes in? Is the trunk line name displayed, or the target line?

 

[slimwhit]

OK;

I put several appearances on the receptionist phone and it worked. Thanks to all who suggested same.

With the other phones that I had tested on (and were problematic), the problem was remedied by removing appearances of the line on other sets. For example, one of my employee's phones also appears and rings in the computer room. Once we removed that appearance in the computer room, second calls were handled normally.

Thanks for all the suggestions. I still have no idea why switching PRI carriers caused the system to break, or at least not function the same, but I'm very appreciative of the suggestions here that lead to another way to skin the cat.

Best to all.

 

[DBrewsky]

Ok, so calls are going to the PRIME SET of the target line. What happens is the target line has a setting IF BUSY TO: (PRIME OR BUSY TONE). Since there was another set with that Target Line assigned, then the system didn't see that target line as busy after the first call (there was an appearance available on another set) and thus not forwarding to the PRIME SET.

Whew, hope that made sense..


--DB