papa-bear

Two questions.

First, does each site have their own mail and networked or does site A host the site B mailboxes? I know you said mail did not need to be addressed but if we do, I think this information would help us.

Second, I am new to "Fletch's Challenge" Are replies to be posted directly to this thread or should we message you while others are thinking of their answers and you post them all at the end?

Rick

Fletch

Assume that Site A hosts mail for both locations.

As for positng the answer, feel free to post it here. Obviously the first to respond with the BEST solution takes the 'win'. So, don't post too early before your solution is complete to prevent folks from stealing your idea, but don't wait too long either :wink:

I am the sole judge, and my decision is final. If I feel there are 2 or more responses worth a 'tie', then I will post both as a 'Poll' and the user community can vote.

Good luck!

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

Chas2002

Wow - this is a tough challenge.

The MCDN PRI isn't so bad, but how do you the same DN's on a CDP Network?

Hmmm...You've got me puzzled and intrigued. And I guarantee you the result (correct answer) will make an excellent article to coincide with my Contingency Plan on PbxInsight..

Chas2002

Steamer

Fletch,
Thanks for taking the time to throw these little brainteasers out.
It definitely keeps the forum lively and interesting.

Okay, I'll take a stab.
Normal CDP will take care of the 4-digit dialling between Site A (1xxx) and Site B (2xxx).

The D/R phones at Site A will be programmed with DN's in the 3xxx range to correspond with the 2xxx range at Site B.

The CDP steering code 2 will use an RLI with two entries.
RLI xx
ENTR 0
LTER NO
ROUT 10 <-- The PRI route
DMI 0

ENTR 1
LTER YES
DMI 3 <-- or any available DMI number
DMI 3
DEL 1 <-- removes the dialled digit 2
INST 3 <-- replaces the digit 2 with digit 3

When the PRI between A and B (ENTR 0) is down then calls to 2xxx will automatically be routed locally (ENTR 1) to 3xxx and ring at the D/R phones. This requires that the PRI has enough channels so that there is never an “all trunks busy” situation.

To handle incoming calls from the CLEC you will need Incoming Digit Conversion on the DID route to convert 2xxx to 3xxx.

The voice mailboxes for 2xxx phones should be programmed to include the 3xxx numbers as Extension DN’s. If the voice mail is Meridian Mail rls 13 then you can also program the mailboxes with Multiple MWI DNs so that the message light will come on at both locations.

Assumptions I am making:
A "disaster" at Site B means that the PRI is down. In the case of an evacuation where the PRI may still be up then some manual intervention would be necessary.
This could be done in different ways. I would suggest setting the TOD fields for the RLI ENTRY 0 to OFF.

Fletch

Not too bad Steamer. But there is a way to do this and have 2xxx on the local phones too!

You're on the right track, just missing a small piece to make the 2xxx phones local as well.

Your solution will work, let's see if anyone can skin this cat a different way..... :wink:

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

slagburn

How about a pretranslation table on the 1xxx phones at site A that will translate the leading digit of 2 into something else... lets say 3?

STOR 0
STOR 1
STOR 2 3
STOR 3

Anytime a user at Site A with a 1xxx station dials 2xxx it should translate into 3xxx and be handled by the CDP below rather than handled as a station to station call.

CDP 3 to SITE B but use a DMI table to yoink the 3 and insert a 2.

RLI xx
ENTR 0
LTER NO
ROUT xx <-- The PRI route to site B
DMI x <-- DEL 1 INST 2 (strips the 3 and inserts a 2)

ENTR 1
LTER YES
DMI x <-- same as above, DEL 1 INST 2 (strips the 3 and inserts a 2)

In D/R mode (assuming the PRI goes down) calls should local terminate and have the 3xxx replaced with 2xxx and be presented to the correct station at site A.

I'm not a voicemail guru (actually I don't know anything about it all) so I can't really help much on that end of things, maybe house the VM at site A and steer calls from site B to the VM at A?... I know that will work but getting the message waiting lights to light on the correct phone at Site B will be an issue since we have those DNs replicated at Site A.

At site B 'normal' CDP should handle the 1xxx calls from B to A.

Fletch

Not bad Slag, you're on the right track. But DMI's are a bad thing for Ring Again, and non-call associated signalling.

You are VERY CLOSE, but you are doing more work than is required.

Here's a hint. I said USER's must 4 digit dial. That is NOT saying what is REALLY happening in the background. What can you do with what you have and NOT invoke a DMI table on outbound calls from Site A?

Glad to see folks scratching their heads and comming up with a way to do something that 'can't be done'. I always said there is a little 'black magic' in NARS/BARS. If you understand it, you can make it do almost anything.

Nice going so far everyone! I'm impressed!

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

slagburn

Put an IDC table on the PRI route of the Site B switch...

I'm going to assume that isn't the answer you're looking for... more beer pls...

Fletch

Nope. It's something you can do on the Site A side. You had all the pieces, just had them put together a bit differently than I was thinking.

What you need is xxxxxxx What the user dials is xxxx

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911