Off Premise extensions and "911" 1

[FoneDude66]

Customer has a Legend 7.0 w/ OPT modules in the switch. She would like to add about 6 extensions at a remote location about 4 miles away. My two concerns are:

1) Is this distance too great for this to work properly?
(my tech support is absolutely NO help at all, and the
Avaya website/documentation is even LESS help)

2) What are my options regarding "911" calls?
(I was told that RedSky works only with Definity...
CAMA trunks/Proctor box?...is this an option?)

I'm really stuck as far as where I should go to research this. Any pertinent info would be GREATLY appreciated. Thank you in advance.

 

[SYQUEST]

As far as functionality you should not have any problem with OPS on the Legend if the circuits are designed and installed PROPERLY! You want good levels, no more than 3dB loss end-to-end for good transmission. So when you order the circuits from your service provider you need to specify this and insist that nothing less will do. 911 could be a problem because the address where the Legend is, is what will be displayed if 911 is called on the local lines. Anyone calling 911 could give them the correct address for the situation.
I don't think any up-to-date telco even uses CAMA anymore since just about everything trunk wise is SS7 except for 911 PSAPs and the selective routers.

Hope this helps!

....JIM....

 

[franke]

I believe ToneCommander carries a 'E911' interface that works with the Merlin.

franke

 

[jgideon]

Are you using PRI trunks at the main location? If you are, you might not need a 3rd party box, just the software that your LEC uses to update PS/ALI.

 

[SYQUEST]

HI JGIDEON,

Please tell us more about this ISDN software to update the PSAPs' PS/ALI via PRI. I have not heard about this.

....JIM....

 

[jgideon]

The method to get the call to 911 with valid 'station' data, and the product used to tell the LEC/PSAP the location of the 'station' are two different products.

In the 'traditional' world, we used to have to install CAMA trunks (often with adjunct hardware) to get valid DID data from the PBX to the network to be handed to the PSAP. Nowadays in _most_ serving locations, if you have PRI, and are configured to transmit valid DID, that DID information will make it through the network to the PSAP. (I've heard of a couple of places where the LEC still can't get the call to the psap correctly due to CO switch software releases.)

The last time I did this was in Illinois with SBC nee Ameritech nee Illinois Bell. We had CAMA trunks with a box from Proctor (sp?) or Telident, and then we had a separate software product that we used to update location information for each DID. The software transmitted the information to a company in Colorado (i think) that managed the data for the PSAP's. We had to pay one fee for the CAMA trunks, and then another fee for the software, and a per-DID cost as well. Once we upgraded the switch, we went to PRI and dumped the CAMA. Lower costs (no separate trunks), and we no longer had the limit on the number of calls to 911, since any PRI trunk could be used.

I think they've migrated the PS/ALI software to be web-based.

 

[SYQUEST]

Hi jgideon,

Thanks for the info. Do you now what software versions on the Legend support this on PRI? Using PRI sure would be cost effective compared to the Proctor/ToneCommander, etc equipment, which is not cheap!

Thanks in advance.

....JIM....

 

[jgideon]

Unfortunately, I've only worked with v7 and later, although I think I've ready here about someone having PRI back on R3? Does anyone know which Avaya document provides release/feature availability comparisons?

 

[merlinman]

Almost any POCKET REFERENCE does some of that.

The FIRST MAGIX Pocket Ref didn't do a good job of it, but the later ones did.

You would probably have to consult a LEGEND R7 and a MAGIX R3 to get the full picture.

At one time I had a Spread Sheet that showed those things in the LEGEND Releases.

If I find it, I will submit it.