You risk hanging up on your other 911 callers... but everything is
always a tradeoff.
In my experience, the 911 dispatcher can (does) pin the call, so that
even though the remote side hangs up, the line is not available for use
again until the dispatcher releases it. I'd expect this to mean
That would be the case if calls are dropped at random to clear the way
for 911 calls. With some form of access control (NCOS, Calling Search
Space/Partitions, priority levels) you would be able to drop the least
important calls.
BTW, how are trunk restrictions managed right now? How can I
make a context for l/d dialing and include it for the phones / times of
day, when it is actually supposed to be used, not otherwise.
At 09:52 AM 6/24/2003 -0600, you wrote:
That would be the case if calls are dropped at random to clear the way for
911 calls. With some form of access control
I'm not sure I can parse your examples correctly. I'm not being
snide, but do you use Asterisk on a regular basis? Do you understand
how applications work, and how call handoff is done between Asterisk
servers? Your example doesn't seem to make sense, no matter how I
think about it.
Of
Now that I reed it back, I can barely make sense of it myself! Anyway, I
was just thinking out loud, the example wasn't meant to be parsed.
Asterisk would need some lower level changes to parse the extra field
holding the location information, and to apply the routing rules to
substitute the
Dylan VanHerpen wrote:
Now that I reed it back, I can barely make sense of it myself! Anyway,
I was just thinking out loud, the example wasn't meant to be parsed.
Asterisk would need some lower level changes to parse the extra field
holding the location information, and to apply the routing
And now that I *read* it back again, you can tell that English is not my
native language either
Dylan VanHerpen wrote:
Now that I reed it back, I can barely make sense of it myself!
Anyway, I was just thinking out loud, the example wasn't meant to be
parsed. Asterisk would need some lower
Problem: 911 calls placed through Asterisk are associated with the
physical location of where the CO trunks terminate. This is not really a
problem when all extensions are located in the same building, but when
Asterisk is used in a campus-like or otherwise networked environment, it
can get
Also, it isn't very easy to 'test' either, as the staff at the 911 call
centre won't appreciate your testing, and at least in Australia, it is some
sort of criminal?/illegal offence to call emergency for non-emergency
situations.
I had much the same thoughts. Currently my 911 code is just
Jon Pounder wrote:
I had much the same thoughts. Currently my 911 code is just commented
out for that very reason - I don't want to get in trouble for
accidentally making 911 calls to test it. Should I rely on that code
untested for when it is really needed most ? What are other people doing ?
Also, it isn't very easy to 'test' either, as the staff at the 911 call
centre won't appreciate your testing, and at least in Australia, it is some
sort of criminal?/illegal offence to call emergency for non-emergency
situations.
Well, for testing purposes 911 could be replaced with any other
Also, it isn't very easy to 'test' either, as the staff at the 911 call
centre won't appreciate your testing, and at least in Australia, it is
some
sort of criminal?/illegal offence to call emergency for non-emergency
situations.
I had much the same thoughts. Currently my 911 code is just
Bumping calls to clear a path for 911 is possible within Asterisk
already - see the SoftHangup application.
That sounds good, but what can trigger the SoftHangup app to drop other
calls automatically when 911 is dialed?
A short AGI script, perhaps?
It probably would not even require a short
13 matches
Mail list logo
