| Kris Seraphine 2007-03-31, 1:12 am |
| Changing the access code can be relatively simple but it depends on your
setup. If you use MGCP for your gateways you only have to change the route
patterns. If you use H.323 (or SRST) you will also have to change dial
peers on the gateways. Other places you may need to make changes are IP
services (fast dials allow you to specify the access code), Unity
restriction patterns, user speed dials, dial-from-outlook dialing rules, fax
machine speed dials.
On 3/30/07, Miller, Steve <MillerS@dicksteinshapiro.com> wrote:
>
> That's good thinking. Of the 100 calls in 3 months, there were 57
> different users who dialed 911 and the ones who did it more than once,
> usually did it one call after another and then corrected their mistake. Was
> it difficult to change the access code?
>
>
> Steve Miller
> Telecom Engineer
> Dickstein Shapiro LLP
> 1825 Eye Street NW | Washington, DC 20006
> Tel (202) 420-3370 Fax (202)-330-5607
> millers@dicksteinshapiro.com
>
>
> ------------------------------
> *From:* cisco-voip-bounces@puck.nether.net [mailto:
> cisco-voip-bounces@puck.nether.net] *On Behalf Of *Kris Seraphine
> *Sent:* Friday, March 30, 2007 10:09 AM
> *To:* Jerri Robbins
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] Quick Question About 911 Policy - Please
> Respond -Quick Response
>
> We ended up switch the access code to 8 to cut down on false dials but 20
> to 30 911 calls a month for only 100 users seems extreme. Do you have
> anyone using the dial from outlook plugin? I've had situations where a
> customer deploys it and an employee configures dialing rules incorrectly
> causing a bunch of 911 calls. You may also want to do a CDR search for 911
> calls and see if the bulk of them are coming from the same source.
>
> On 3/30/07, Jerri Robbins <jrobbins@mercurypay.com> wrote:
e intended recipient or person responsible for delivering this confidential communication to the intended recipient, you have received this communication in error, and any review, use, dissemination, forwarding, printing, copying, or other distribution of
this e-mail message and any attached files is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, received, or sent on its network. If you have received this confidential communication in error, please
notify the sender immediately by reply e-mail message and permanently delete the original message.[vbcol=seagreen]
>
>
> --
> kris seraphine
>
> --------------------------------------------------------
> This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. This communication may contain material protected by attorney-client, work product, or other privileges. If you are not the
intended recipient or person responsible for delivering this confidential communication to the intended recipient, you have received this communication in error, and any review, use, dissemination, forwarding, printing, copying, or other distribution of t
his e-mail message and any attached files is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, received, or sent on its network. If you have received this confidential communication in error, please n
otify the sender immediately by reply e-mail message and permanently delete the original message.
>
> To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com
>
> Dickstein Shapiro LLPhttp://www.DicksteinShapiro.com
> ========================================
======================================
>
>
--
kris seraphine
|