BCM 50 -> BCM 400 Trunk Goes to Prime

[WDSRob]

We have two offices, one with a BCM 400 (site A), one with a BCM 50 (site B), trunked together. Each site is configured with seperate DN's, and it was all setup so that you could dial an extension at the opposite location and it would ring through to the proper DN/ext on the other side.

Recently this stopped working, but only from one end. I can dial extensions for site B(50) from site A(400), but not the other way around. Whenever I dial an extension for site A from site B, it goes straight to prime on site A (operator).

I've verified that the private network dialing plans on each side match (CDP, Network ID of 1, BCM400=location code 1, BCM50=location code 2) are correct, and the routing is correct.

I'm not sure what else could be causing this?



Thanks!

 

[Dasheen]

verify the private rec'd digits are still programmed

 

[WDSRob]

I'm assuming you are talking about from the 400 and not the 50 (since it doesn't seem to be properly routing calls on the 400 side). If I open up the target lines in the BCM 400 I don't see anything other than real incoming numbers listed, nothing for the VOIP trunk lines. If I open up the VOIP trunk lines, I don't have a pop out for received number under trunk/line data. Maybe I'm not understanding/looking in the right place?


Here are some pics of the config, on both devices:

BCM50:

BCM400:

Thanks for your help!

 

[Dasheen]

What version BCM 400 are u using? U would've had to assign target lines to the BCM 400 just like u did on the 50. U'd also have the private rec'd digits entered just like on the 50. Target lines on the 400 start at 241. Verify the programming of all your target lines and verify they're still assigned to the correct phones.

 

[WDSRob]

Ok, I'm with you

BCM400 is at 3.6, not sure what revision, no clue on the BCM 50, they were purchased at the same time (if you can tell me where to grab the version from the interface I'll be happy to provide it). I didn't do the original setup on either of these, we actually have both under maintenance with att/bellsouth, but their local techs (although extremely helpful) seem less than knowledgeable on the device than we are -- we have done the majority of the customizations to the system (ie: they didn't know how to enable call screening).

Target lines 241 through 267 are all public numbers, there doesn't appear to be any target lines pointing to pool A or pool B -- it's all PRI-A (public) numbers. It's possible that this was wiped out when a backup was restored several months back.

I'd like to leave some room for more additional incoming lines, and I'm not real sure how to set a private target line up in the 400, because there aren't any examples present to duplicate/work from.

Can I start my private target line assignment at say Target Line 300?

I tried setting up an example target at 300 in this way:
Name: Line 300
Control Set: DN 221
Trunk Type: Target Line
Line Type: Private to 222
If busy: To prime
Prime Set: DN 221
Distinct rings in use: Patterns 2,3,4
Distinct ring: None
Use aux ringer: N
Priv Rec'd #: 0222 (would only let me use 4 digits)
Pub Rec'd #: 0222 (would only let me use 4 digits)
Voice message center: Center 1

I then tried dialing from x326 at site B (BCM 50) to x222 at site A (BCM 400), and got the same results. I'm probably missing something simple.


Thanks again.

 

[WDSRob]

I also tried it setup like this (to duplicate what I was seeing on the BCM50):

Name: Line 300
Control Set: DN 221
Trunk Type: Target Line
Line Type: Public
If busy: To prime
Prime Set: DN 221
Distinct rings in use: Patterns 2,3,4
Distinct ring: None
Use aux ringer: N
Priv Rec'd #: 0222 (would only let me use 4 digits)
Pub Rec'd #: 0222 (would only let me use 4 digits)
Voice message center: Center 1

Then I tried it with extension 254 (222 rings to 254, 222 is a hardwired set, 254 is a softphone):

Name: Line 300
Control Set: DN 221
Trunk Type: Target Line
Line Type: Public
If busy: To prime
Prime Set: DN 221
Distinct rings in use: Patterns 2,3,4
Distinct ring: None
Use aux ringer: N
Priv Rec'd #: 0254 (would only let me use 4 digits)
Pub Rec'd #: 0254 (would only let me use 4 digits)
Voice message center: Center 1



Thanks.

 

[Dasheen]

U can use any free target line within the 241-492 range.

Did u remember to assign the target line to the set in question?

If your DNs are three digits, u can change the private rec'd number length under Dial Plan. U want your private rec'd number to match your DN.

 

[WDSRob]

On both sides the DN's are three digits, using three digit dialing (not location codes) for calling from site A to B (and vice versa). 2xx at site A (400), 3xx at site B (50)

I went to assign the target line to the DN, and figured out the scheme that they used when it was setup originally. Target lines for the DN's start at Line321.

Here is how each one is setup (321,322,323,etc..):
Name: Line323
Control Set: DN 221
Trunk Type: Target Line
Line Type: Public
If busy: To prime
Prime Set: DN 221
Distinct rings in use: Patterns 2,3,4
Distinct ring: None
Use aux ringer: N
Priv Rec'd #: (blank)
Pub Rec'd #: 223
Voice message center: Center 1

This is assigned to extension 223.

223 extension is setup as follows:
Last name: User
First name: Joe
Display in directory: Yes
Outdial type: none
Name: Joe
Model: T7316E
Device port: Port 0203
Control set: DN 221
Call log passwords: (blank)
Prime line: I/C
Intercom keys: 2
Private OLI number: (blank)
Public OLI number: our public phone #
Line assignment: Line 323
Appearance type: Ring only
Appearances: 2
Caller ID set: Y
Vmsg set: N
Line pool access: Pool A, Pool B, Pool PRI-A
Answer DNs: none

There are other values, but I don't think they will be relevant.


So it does appear that the target lines are in place and assigned on the BCM 400, unless something in the config above is off.


Thanks!

 

[gberger]

You should use CDR client to troubleshoot this. It will show you what the bcm50 is sending and what the bcm400 is receiving.
Do you have MCDN keycode on your bcm400? If so, use the private received field.
Since you have 3 digits extensions, program the private receive to 3 digits and put the proper extension for each target line.

 

[WDSRob]

Any tips for using the CDR client? I downloaded it, but it doesn't seem to connect to either BCM.

BCM400:
Unable to create connection point object: Access is denied

BCM50:
Unable to create connection point object: The RPC server is unavailable

I have the following keys applied:
IP Clients - 3
23 CallPilot Mailbox Increment
LAN CTE DEsktops - 1
CallPilot Professional Call Center
8 VoIP gateway port(s)
SL-1



As illustrated in the screenshots earlier in the thread, private is set to receive 3 digits on both ends, and target lines seem to be configured based on what I saw last night (my last reply).



Thanks for your help.

 

[Dasheen]

I see an error. Your private rec'd number is blank. It should have the ext ur assigning it to.

 

[snowman50]

I am a bit confused..Is your private receive digit lenght 4 or 3.
It should match the extension number .eg. 222 private 222.
You say in your screen shot it would only allow you to set it to 4 digits.

set it to 3 to match your extn lenght.
THE ONLY PROBLEM IS IF YOU REDUCE THE PRIVATE EXTN LENGHT IT WILL WIPE OUT ALL RECEIVE DIGTS FOR THE SYSTEM.
you will have to renter them manually one at a time

 

[WDSRob]

Private/pub rec'd on the public lines is 4 digits, I was confused initially

The target lines assigned to the DN's (that I located after digging around a bit) have a 3 digit public rec'd number (matching the corresponding extension that the target line is assigned to), but the private numbers are blank.

Dialing plan for private, DN length is set to 3 on both the 50 and the 400. Is this the setting that I'm looking for, or am I mixed up and rec'd length is set somewhere else also?

When I get back I'll see if it will let me enter the extension in private rec'd for the target lines (assigned to DN's) and post my results.


Thanks!

 

[WDSRob]

Ok confirmed. Private rec'd DN length is off.

I had to look in the help file to figure out where else DN length was, and both pub/priv are set to four digits.


I'm weary of changing it at the moment though, based on one of the replies here:

"THE ONLY PROBLEM IS IF YOU REDUCE THE PRIVATE EXTN LENGHT IT WILL WIPE OUT ALL RECEIVE DIGTS FOR THE SYSTEM.
you will have to renter them manually one at a time "


Now if we're talking about wiping out all of the private rec'd digits, that isn't really an issue -- as there are no private rec'd digits set on any line in the system currently. If we're talking about wiping literally all rec'd digits throughout the system (public and private), that would be a pretty big problem!

So for clarification, if I change the private rec'd length, will it just reset all private rec'd numbers, or are we talking about a total loss of all public and private rec'd numbers if the private is changed from a length of 4 to 3 ?

btw .. bcm version is 3.7, not 3.6.


Thanks for all the help!!

 

[Dasheen]

It will only affect the the private rec'd length as there is a different prompt for public rec'd. Once you enter the private rec'd numbers, your calls should go thru.

 

[WDSRob]

It worked!


Thanks for all the help everyone!!

 

[Dasheen]

glad I could help