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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

E911 issue

Status
Not open for further replies.

roc221

IS-IT--Management
Jan 26, 2010
88
US
Afternoon all, Need some of your advice or help in clearing up this issue .

i have CS1K 1000E release 5.5 i am having some 911 issue, we are an all ip system 2000+ phone, our 911 is setup in one zone and analogs devices setup in ERL for each location . the problem i am having is once in a while when someone call 911 from there IP phone i dont get the LOC info . i have check my ESA and my DMI config all looks good but sometime i get loc unknown and other time i get the loc address.

expamples below .

correct info

--> Critical Alarm received at TM! - 2011 07 27 12 38 52 00 - Call_server - OSN000 - CS1K:port Of Seattle:CS - 2011 7 27 12 38 4 - 202 - CUST 0 911 CALL ALERT\15\15\15TIME: 12:38:52 JUL 27, 2011\15NAME: GT Inforcement\15ORIG DN: 4990\15SITE: STIA MER-VD\15LOC: 17801 INTL BLVD\15;;\15DES: GT\15SET: IP SET \15ERL: 100 \15TER RTMB: 190-41 ACOD: 89190\15CALLED#: 911\15CALLING#: 2067876300\15\15OSN000 RECORD END\15\15\15

incorrect info

--> Critical Alarm received at TM! - 2011 07 27 09 53 00 00 - Call_server - OSN000 - CS1K:port Of Seattle:CS - 2011 7 27 9 52 59 - 202 - CUST 0 911 CALL ALERT\15\15\15TIME: 09:52:58 JUL 27, 2011\15NAME: STIA Training Front Desk\15ORIG DN: 6862\15LOC: UNKNOWN\15;;\15DES: STIA\15SET: IP SET \15TER RTMB: 190-44 ACOD: 89190\15CALLED#: 911\15CALLING#: NONE\15\15OSN000 RECORD END\15\15\15

both of these example are from IP phone 1140.

these one is from analog phone .

--> Critical Alarm received at TM! - 2011 07 27 10 06 29 00 - Call_server - OSN000 - CS1K:port Of Seattle:CS - 2011 7 27 10 6 28 - 202 - CUST 0 911 CALL ALERT\15\15\15TIME: 10:06:27 JUL 27, 2011\15NAME: Oversize Baggage\15ORIG DN: 5675\15SITE: STIA MER-VD\15LOC: 17801 INTERNATIONAL\15;;\15DES: STIA\15SET: ANALOG SET \15ERL: 100 \15TER RTMB: 190-36 ACOD: 89190\15CALLED#: 911\15CALLING#: 2067876300\15\15OSN000 RECORD END\15\15\15

anyone have any ideas why loc is unknown ??

 
The first thing you should look at is what the actual OSN alert says on the terminal when you make a test 911 call, and that will help you narrow down where the problem might be.

rt12
 
i have check the TM server where the alarms come from, and they are reading the same as my posted . i am now going to get vendor to take a look . it odd it hit and miss not sure what going on .
 
What do you use to give the location to the IP phones? Static ERL, LIS or an external discovery manager?

If you do a "locrpt DN xxxx" in 117 for a set that doesn't work and one that does is there a difference.

Sometimes in LIS it can be that the port it is plugged into does not have the correct VLAN assigned an the set ends up on the data VLAN, obviously the Data VLANs are not set up in the Subnets (LD 117 "prt subnet") and the set is location unknown.
 
inking on it can be a mis config on the set if using say LIS where there is a value against the ERL prompt say "0". If you were using LIS then enter "x" against the ERL prompt of the set and then "Locrpt dn xxxx" the set again and see if it moves to the right ERL/Location.
 
thanks all, and yes the ERL on the IP phone was set to 0 . these phone were setup in TM 3.2 and come to find out that TM will always put 0 in the ERL setting and if you try to remove it VIA TM it goes back to 0 . have to remove via cmd line . by typing X .

THAT WHY I HATE TM AND TRY TO DO VERYTHING I CAN BY CMD LINE !!!

i am old school when all you had was cmd line that god TM goes away in 7.5 , but now you have session manager .
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top