BCM50b in UK - help for a new admin used to Avaya IP office

[IanRoss61]

Hello I was wondering if any experienced BCM administrators would help someone who has inherrited a BCM 50 that has moved from one office to another and has 4 channels of ISDN running a main number and 20 DDI's (DID). The system uses the call pilot voicemail and the main number is answered by an AA which distributes the calls as programmed. The problem is with the DDI's. The old office had a range that ended 825x and the new 343x. All calls to a DDI end up on the prime set (227 in this case). In target lines I have tried altering the old Pub received to the new and I get a message 343x is not a valid Pub #. How do you change this? It seems straight forward but something else obviously needs altering. Thanks in advance for any help.
Ian

 

[snowman50]

you need to look at the target line that has 343 as its receive digit.
Scroll down the Target lines
Remove it.(delete)
Then the system will allow you to now enter 343x to your new lines

 

[Bonker1974]

The reason why you are getting is not a valid Pub that means that that number is being use some where in the BCM.

you have a couple of option
1. Renumber the BCM and start over.
2. Change your Public DN to receive 3 digits rather than 4 digits and tell the co to send you 3 digits and make the change in the target lines.
3. look in the BCM to see where 343 is being use and renumber it to something else.

 

[IanRoss61]

Thanks to both for your pointers. Have now re-looked at the DN list and have discovered that target lines run 125 to 332 so my leading 3 digits aren't covered there. 343 is in fact one of the 12 application DN's allocated to the VM. Can I move Application DN's or is this is looking like a re-number and start over job as per option 1. Also why does the system need 200+ target numbers or is that just poor initial programming?

Thanks again

 

[Firebird Scrambler]

You can easily use up the target lines if you have loads of DID numbers or is part of a large network. It sounds like the programming from day one was overlooking the future DN allocation and it could have made allowances for the 3xx range?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[yankblan]

If the BCM50 (starting with 2.0 or 3.0; can't remember) has initial DN at 221, the VM defaults at 343. When starting a BCM, I always renumber VM to 500, a round - easy to remember DN for end-user/administrator of the bcm for FWDNA or FWDB to voicemail.

As for target lines, you have one created for each potential DN in use for obvious reasons, the main one being multi-site networking.

You never dealt with that; but I had a customer with a MICS that was installed as MEGA and later upgraded to 7.1 (11 station modules + 32 stations from main cabinet = 208 extensions/208 target lines); the administrator would do tons of relocating and change DNs, which would screw everything up, and had to browse each target lines one by one to find one free or where the screw-up happened. Telset back then, no visual help like Element Manager...

 

[IanRoss61]

Thanks to all who posted. I moved Callpilot DN's to 500 as suggested and removed the 383 entry for public which was against line 273 (!!). Placing the 6 digit ddi number in public for the target lines allocated to the various handset dn's then worked.

Thanks

Ian