Has anyone installed and maintained a solid E911 platform integrated to a CS1000? We have i2004 phones tied to our PBX over a WAN circuit and need a 911 soultion. Can anyone recommend from actual field usage. All the sales guys spew the usual sewage about theirs being the best etc etc.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
E 911 and Nortel 1
- Thread starter hebegb41
- Start date
I'd start here:
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
-
1
- #3
The you tube series is your best thing to use. I pretty much used that and have setup in network. We are using the dynamic elin's and subscribed to the locator id service thru telco. Etelemetry makes the locate 911 server to keep track of where your ip phones are in the network. The issue I have with them is I gave them my information to test drive their len's software and they will not respond back to me. Basically it's smnp traps that send out a screen pop when a 911 call is made. It can alert multiple people. Don't know much more than that since they won't respond to me.
Ed, I'm the product architect of the eTelemetry items mentioned above. Other than a lack of response (for which I apologize), can you describe the issue you're having in detail, please? If you have it, I'm sure others do as well, and could benefit from it being answered and addressed here.
That's an odd situation. The process is automated, so you should have received an email within minutes. Perhaps your spam filter grabbed it? In any event, I've attached a link to the download to this post.
There is still a registration component to the server piece. As soon as it's installed, you'll need to run the Activate LENS application, and indicate the IP address of the network adapter that the client will connect to. It should be pretty painless.
On the CS 1000 side, you need to configure it to send alarms to the LENS device. If you have more than one CS 1000 on your ELAN, simply do this once on each.
a. Connect to the CS1000 using the cslogin command from a signaling server (or connect directly if you prefer)
b. Log in as a user with administrative privileges
c. Enter the LD 117 command overlay
d. Use prt open_alarm to see what devices are set to receive alarms
e. Find an empty # and then issue the command: set open_alarm <#> <LENS IP>
f. Exit out of the overlay by typing ****
g. Enter the LD 43 command overlay
h. Save and Backup the configuration by issuing the EDD command
i. Exit out of the overlay by typing ****
j. Log out of the CS1000 by typing LOGO
k. Disconnect by typing ~. at the command prompt.
At this point, the LENS server should receive every alarm generated by the CS 1000. Install and run the Alert Agent on the same or another Windows machine, and point it at the IP address of the LENS server. Anytime an emergency call or misdial is detected on the CS 1000, the LENS Server will send a message to the Agent, which will scream like crazy until it is dismissed.
Please feel free to continue to post with questions.
There is still a registration component to the server piece. As soon as it's installed, you'll need to run the Activate LENS application, and indicate the IP address of the network adapter that the client will connect to. It should be pretty painless.
On the CS 1000 side, you need to configure it to send alarms to the LENS device. If you have more than one CS 1000 on your ELAN, simply do this once on each.
a. Connect to the CS1000 using the cslogin command from a signaling server (or connect directly if you prefer)
b. Log in as a user with administrative privileges
c. Enter the LD 117 command overlay
d. Use prt open_alarm to see what devices are set to receive alarms
e. Find an empty # and then issue the command: set open_alarm <#> <LENS IP>
f. Exit out of the overlay by typing ****
g. Enter the LD 43 command overlay
h. Save and Backup the configuration by issuing the EDD command
i. Exit out of the overlay by typing ****
j. Log out of the CS1000 by typing LOGO
k. Disconnect by typing ~. at the command prompt.
At this point, the LENS server should receive every alarm generated by the CS 1000. Install and run the Alert Agent on the same or another Windows machine, and point it at the IP address of the LENS server. Anytime an emergency call or misdial is detected on the CS 1000, the LENS Server will send a message to the Agent, which will scream like crazy until it is dismissed.
Please feel free to continue to post with questions.
You're most welcome. Just so you know, there was a version of the trial that did not ship with a default preferences file. An oversight, but one that will prevent the configuration tool from starting. It's been fixed, but I don't know if the installer on the web site has been updated yet. If you try to run it and get an unhandled exception, simply create a file called LENSPrefs.xml in the same folder that in which you installed the LENS Server. Edit the file and make sure it contains the following content...
<?xml version="1.0" encoding="us-ascii" ?>
<LENSPrefs xmlns:xsi=" xmlns:xsd=" <LastModifiedBy />
<LastModifiedDate>2008-12-18T14:17:46.4658438-05:00</LastModifiedDate>
<LocalServerIP></LocalServerIP>
<SMTPServer />
<SMTPUser />
<SMTPPassword />
<SMTPFrom />
<SMTPFromFriendly>eTelemetry LENS Server</SMTPFromFriendly>
<SMTPRecipients />
<SMTPRecipients />
<SMTPRecipients />
<SMTPSubject>Emergency Call Alert</SMTPSubject>
<SMTPEnabled>false</SMTPEnabled>
</LENSPrefs>
Save the file and restart the configuration app. After you changed the configuration, you may need to restart the LENS Service.
Regards,
Mike
<?xml version="1.0" encoding="us-ascii" ?>
<LENSPrefs xmlns:xsi=" xmlns:xsd=" <LastModifiedBy />
<LastModifiedDate>2008-12-18T14:17:46.4658438-05:00</LastModifiedDate>
<LocalServerIP></LocalServerIP>
<SMTPServer />
<SMTPUser />
<SMTPPassword />
<SMTPFrom />
<SMTPFromFriendly>eTelemetry LENS Server</SMTPFromFriendly>
<SMTPRecipients />
<SMTPRecipients />
<SMTPRecipients />
<SMTPSubject>Emergency Call Alert</SMTPSubject>
<SMTPEnabled>false</SMTPEnabled>
</LENSPrefs>
Save the file and restart the configuration app. After you changed the configuration, you may need to restart the LENS Service.
Regards,
Mike
- Status
Similar threads
- Locked
- Question
