Is there any way to allow an attendant console across an ip trunk to receive emergency call notification for sets on the other side of the ip trunk. We can set up DSS/BLF with a feature directory number once we cluster the elements together, but can you set up emergency notification if the 911 route does not pass through the "listening" 3300?
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!
911 Emergency Notification across IP Trunks
- Thread starter rdpayne
- Start date
The call has to access a route on the local 3300 for Console notification.
I am unsure if you might be able to use an emergency hunt group accross multiple controllers but I suspect not.
If you are careful, you could program your ARS to loop the call thru the system with the Console. Complicated programming required modifying digits at both ends but it would work.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
I am unsure if you might be able to use an emergency hunt group accross multiple controllers but I suspect not.
If you are careful, you could program your ARS to loop the call thru the system with the Console. Complicated programming required modifying digits at both ends but it would work.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Thread starter
- #3
That makes sense on looping through and back across that link then out again to make the true 911 call. Make that loop route type emergency, the only thing I'd have to test is what would show up on the monitoring consoles 911 notification log.... Thanks for the tip. I'll give that a try.
- Thread starter
- #4
I am trying this in a lab between 2 controllers connected via IP trunking. I am simulating a 911 route going to a non emergency number (my cell phone). 911 across a tdm link on Controller A works fine.
I now want to create a list. List 1 has Route 20 and 21. 20 goes to Controller B to be looped back and fire of the emergency notification. Route 21 is in case the IP link is down and still allows the emergency call to go out.
Route 20 - IP trunk - DM on this route adds a *, so digits inbound to Controller B comes in as *911.
On Controller B, I have an entry for *911, Route 20 on Controller B. Route 20 has a DM that strips off only the *, pushing 911 across the IP trunk back to Controller A to be routed out the existing 911 route. I set it as an emergency route and when I generate a *911 call on Controller B, the attendant emergency notification fires off no problem.
I keep coming up with Access Denied. Because this is a lab, I've no one restricted under my COR Groups (all 64 groups are empty). I've added the Public Network to Public Network Allowed to the COS of Controller A & B's devices, IP Trunks, and TDM TRunks. I've tried adding PUblic Trunk to the COS of both Controller's IP Trunks. No luck. No interconnect restrictions on either controller. Any thought on what i am missing? Thanks.
I now want to create a list. List 1 has Route 20 and 21. 20 goes to Controller B to be looped back and fire of the emergency notification. Route 21 is in case the IP link is down and still allows the emergency call to go out.
Route 20 - IP trunk - DM on this route adds a *, so digits inbound to Controller B comes in as *911.
On Controller B, I have an entry for *911, Route 20 on Controller B. Route 20 has a DM that strips off only the *, pushing 911 across the IP trunk back to Controller A to be routed out the existing 911 route. I set it as an emergency route and when I generate a *911 call on Controller B, the attendant emergency notification fires off no problem.
I keep coming up with Access Denied. Because this is a lab, I've no one restricted under my COR Groups (all 64 groups are empty). I've added the Public Network to Public Network Allowed to the COS of Controller A & B's devices, IP Trunks, and TDM TRunks. I've tried adding PUblic Trunk to the COS of both Controller's IP Trunks. No luck. No interconnect restrictions on either controller. Any thought on what i am missing? Thanks.
- Thread starter
- #5
Make sure you have a route list that will allow 911 out of the local controller without the IP loop thru the second controller just in case the IP trunking fails.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Thread starter
- #7
I have a list with the first route doing the loop, then the second route out the tdm trk group in the event it fails. Now I am walking through my programming, because when I call from Controller B dialing *911, it works. When I attempt to loop from Controller A, it fails. On controller A, i have the other end of the loop, an ARS Digits Dialed entry for *911, out the TDM route, stripping off the * before going out. When I dial *911 from Controller A, it works. It is the loop out to B then coming in and trying to go out Controller A i keep getting INvalid, which means I've got a bad entry somewhere. I made sure to put the PUblic Trunk Access Via DPNSS on the devices and back on the inbound IP trunks, but it keeps failing. I am ripping it out and trying now with 81911 to just to see a different string come across SMDR which I am tracking - which by the way shows the string to Controller B , X9999 for the IP trunk loop back, then the call drops as Invalid and I don't see any outbound string on the Controller A side...
- Status
Similar threads
- Locked
- Question