Fletch

OK, as I said, there is more than 1 way to solve a NARS/BARS issue. Bottom line is that it gets the job done and doesn't impact other services.

CDP and UDP can co-exist. The key parts of this problem are:

Pre-Translation Tables
Users have a 'simulated' CDP environment
The backend integration is via HLOC and UDP
This allows 'dial around' capabilities (not one of the requirements)
Translating to a HLOC also allows the 'simulated' CDP to use the CONV feature in an RLI to send the calls to PSTN if needed.

So the moral of this story is that I have made all of you come up with a solution to a problem that many thought could not be done! The same DN appearing in a CDP and local environment under certain situations.

Each of you have come up with your own little twist on how to get it there, each with different levels of functionality and support. The other lesson learned is that NARS/BARS can handle things in many ways. Which way is the most correct? None of them. You need to look at each environment and decide what is best for that situation.

GREAT JOB EVERYONE! I am truly impressed with your out of the box thinking. The best ideas come out of the "Idon't care what can and can't be done! Just DO IT!" environments we are all forced into every day.

Everyone who answered this challenge, send me your snail mail address and I will toss out a Nortel mouse pad....

__________________
Fletch
Nortel Emergency Services PLM

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

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts

slagburn

Interesting...

Can you break that out a bit... sort of like we were doing above.

Having never dealt with HLOC I'm having difficulty following the call flow.

damo1976

I havent had time to work this through completely, but just wanted to have a stab before this one gets exhausted. Fogive me if i am miles away!

I was thinking you could configure BARS/NARS to recognise that anything 2xxx should be routed via the PRI, rather than . Set all 1xxx phones to have ncos high enough to route calls over the PRI.

Next, (and this is where I didnt do the homework first!) I believe you can use Time of Day routing schedules to override route access settings on the phones (I believe schedule 7 is a special schedule which override existing route access). Within the table, specify an alternate NCOS without route access to the PRI.

Next problem is how to invoke DR. You could do this by pressing the RTC key on the attendant console, thus overriding the NCOS settings on the 1xxx phones.

I know i missed the conversation thread last week, but I am on UK time!!!

Cheers guys.

papa-bear

and here I thought I could compete with you brainy people out there. '

I got as far as using the RLI and ahving the first route calls to site B and to keep them on site A when the link failed. I could not think of how to use the CDP / DMI to manipulate the digits to keep the numbers on the switch.

I was even going as far stretched in my thinking as to say, why not just let the phones ring in both locations so when the line failed between A and B the lines in site A would keep ringing.

So much for that

Thanks for the thought provoking questions. I look forward to learing more from future questions.

Rick

damo1976

Here here! Its unbelievable how much I have learned from this site. Keep the challenges coming!

Chas2002

Fletch - What did you have in mind as the most efficient approach to your quiz?

I'd like to make it into a scenario for Contingency Planning and Management.

You can download my basic approach to CPM here:
http://nortel.pbxinfo.com/modules.ph...q=getit&lid=10

Let me know if you think this would be a good addition.

Thanks,
Chas2002