BCM 3.6: Destination Code Issues - This is a tricky one! 1

[markelbcm]

Hi There, I'm going to try to be specific as I can becuase this questions is a HARD ONE!!! I'm an NNCDS and stuck up against a wall!!!

I have this BCM (400) RLS 3.6. It's been configured with DN's in the 4 digit range of 4xxx and not the standrd 2xxx becuase this is a branch office and we have VoIP, office to office dialing.

My problem:

In our toronto office (DNs: 21xx to 25xx) we grew and have now provisioned extensions that are 20xx range.

So, in the branch office (DNs: 4xxx) I have configured my IP Telephony H.323 Trunks, Remote Gateway, and added the [Desitnation Digits as follows [20 21 22 23 24 25]

I have also added to my Destination codes [20 22 23 24 25] and each respective dest. code uses route 004, absorbed length = 0 on NORMAL schedules.

Route 004: is Pool [o] (my VoiP pool] DN type: Private

Here is the KICKER!!!

I cannot add Destination Code 21 !! I get the error "21 is not a valid options for "Destination code"

I have checked EVERY target line, yup, i know, every one, to see if a stray 21 was added preventing me from using 21 as a dest code, nothing here.

To top is off, our PRI fro Allstream, has digit replacment on the DNIS so our recive digits are all 71xx for the LDNs & DID's..

I am soooo stumped! I cannot figure out why it will not let me add Dest Code 21 so people can dial the other staff with 21xx in the toronto office. The can reach anyone else with 20xx or 24xx, 25xx etc.

I just cannot get Dest. Code 21 added to this BCM.

P.s. I also reviewed access codes (line pool codes) and nothing there for 21!

Help!

 

[acewarlock]

I use 45, 78, 79, 86, 86 for my codes, why don't you just use 2 as your dest code?

 

[hawks]

What does your Hunt Group dn's start with?

 

[acewarlock]

some use 24 and some use 43

 

[photon33]

What wild cards are not available if you assign your dest code as 21A?

Or access the BCM via the telephony interface, and manuveur to System Programming>Change DNs.

Enter 21 then press 1 thru 8 to find your rogue 21XX extension. If you find one there replace it with a new number.

Like the others said, look at Hunt group dn's.

------------------------------------------
Wash, rinse, repeat.

 

[CBasicAsslember]

photon33 struck a nerve. This happened on a Norstar but I suspect they just ported the code over to the BCM's. If you put a DN in that sets a wildcard as not available, and then removed the DN, the wild card will still show as unavailable. Had to manually set the wildcard to available.

 

[markelbcm]

Wow, that you all for your replies!

Here's some aditional info:

[acewarlock]: The reason I don't use just 2 is in our toronot office, we outgrew the 1st BCM and slapped another one in beside it. The 1st system hosts DNs: 20xx to 25xx and the 2nd system host's DNs" 26xx to 29xx. The two are tied together with VoIP truning and use their own PRI's to dial out, but, the 1st system has the inbound calls and VM/Recpt transfers inbound callers to the 26xx->29xx range and it hopps on over to the 2nd unit via VoIP. Since we have 2 BCMs in one office, each Branch office needs to be programmed with the two respective gateways and their associated destination digits. I also did just try '2' and it would not take.

[hawks]: I have checked HG Dn's & all are in the 4xxx range. Keep in mind when the system as initalized the 4-Thousand DN range was selected with the inital system setup. DN Changes were not used to obtain the 4xxx range of DN's this sytem is config'ed for.

[photon33]: To date, I have not utilized any wild cards, but your comment struck and idea, i will test with a wildcard and see what happes.

I have also looked in EVERY target line for the appearance of any recv' digits 21xx and found none.

I have checked the Park Prefix and it's not 2, but default 1.

I have checked all the access codes for pools and nothing 21xx there.

I have looked at all the dest. codes and there are no 2's. (I have removed them all and tried to re-buld and it will take all dest. codes but not 21, ugh!)

I have looked at all DNs, active, application, companion, DETC, and all DN's are listed in the 4xxx range..

I am really stuck and really impressed with all your input and perspective!

 

[markelbcm]

Hi [photon33]:

So, I setup 21A and the wildcard 6 is not available..

What would this mean? Some where is a 216x programmed in a target line recv. digit (pub/Priv)?

In the minimum, i now know with first 3 of 4 mal-digits..

This, this is prograss... but where could this be hiding?

 

[markelbcm]

[COLOR=red yellow]!! Eureka !![/color]

I figured it out!!

Ok, with Photon33's comment about the WildCard feature, I added a 21A to the Dest. Code, it took it. Then went in to the Wildcard tab and looked at all the 0-9 states and say that 6 was not assignable. So, this told me that 216x was some where in my system. i went to the target lines, tried to add 2160 to 2169 to a blank target line in both PUB and Priv. When i got to 2169 it would not allow me to add, so, I went back and looked at ALL the target lines and sure enough, TL269 had the digits! (Doooh) I removed them, and were back in business!

Photon33: Thanks for the Wild card insight, very usefull!

 

[photon33]

Yea, finding those hidden numbers can be a real pain sometimes.

Glad to help.

------------------------------------------
Wash, rinse, repeat.