4-digit dialing dilema

[Davids38]

I have a facility that is running a bcm400. They are currently configured to run with 3 digits. HQ is wanting us all configured to run on 4-digits and they have randomly assigned this facility to have the first digit be an 8 then the last 3 would be the 3 they are currently using.
I just configured my facility to work with 4 digits (you might have seen my posts from before), but I was lucky as the #4 was our 1st digit assigned to us and that corresponded with the actual digit in all of our numbers! This other facility is not so lucky!

FINALLY, MY QUESTION - is it possible (and if so how) to configure this BCM 400 to run 4 digits and have the 1st digit be an 8 even though the actual phone numbers don't have that 8 in them?

Thanks!

David

 

[pccal]

Not positive what you are actually asking? Are you talking about the actual dn of the set starting with 8 or are you wanting the received number of the target lines to start with 8? The answer to both is yes you can.
Just change to 4 digit Dn's & then do DN changes.
Example: Ext range 2221 to 2252 change to 8221 to 8252

 

[fireeater]

a little trick to do to make the first number an 8 automatically is to set up the digits 1 to 7 as digits in use
make sure that 8 is not that way when you change to 4 digitd it will automatically change all the dn's to start with 8

one way to use up the digits is to make use of the routing codes


All Things Are Possible With Time And Lots And Lots of Money

mike

http://www.ics-on.ca

 

[rlsabin]

I think your question is "Does my extension number have to match my the last four digits of my DID number?" the answer
is No. You should be able to change your existing xxx DN's
to 8xxx DN's and not have any issue's with your currently
assigned DID's.

Rick

 

[DBrewsky]

Fireeater, very nice trick..

Also, when you change the DN Length, the Call Pilot (voicemail) will have to be reinstalled and you will lose all Call Pilot data.


--DB

 

[Boomarang]

I recently tried to change DN length and then change DN to Yxxx, keeping the last three the same as before. It worked great on the one system. Unfortunately this was one of five systems connected via VoIP, all with different numbering schemes. I ended up having lots of numbering conflicts between systems and all the destination codes in routing.

After fighting this on all systems for two weeks, I relented and did a cold-reboot and renumbered extensions beginning with Yxxx. Most on the routes and names stayed, I just had to double check line appearances and specific FNA's plus rebuilding the CP.

I went into the CP beforehand and downloaded the sound files to save time and rebuilt the VM without having to re-record anyone's voice.

My advice is to rebuild if networked with multiple systems.