[cisco-voip] Extension Mobility, Emergency Calls

[Jonathan Charles]

For the US, 911 is the emergency number... for Germany, it is 110, for the
UK, Hong Kong, Singapore, it is 999... In Australia, it is 000, etc...

You would create a pattern: [accesscode].[emergency number] and another, for
just [emergency number]

This is because in most US states, someone visiting your site should be able
to just pick up the phone and dial 911 (even if they do not know your access
code)... Interestingly, in some states the VoIP installer is criminally
liable for these patterns being properly set up.

What we generally do is create a partition for each site with a
distinguished name, Chicago911PT, NewYork911PT, Atlanta911PT and dump the
911 pattern in to there.

We then assign that partition (plus the internalPT) into a CSS for each
site, and assign that to all the hard phones at that site.

For device profiles, we assign class of restrictions (CSS) to each user and
do not assign any emergency services.

The CSSs are concatenated together (as stated earlier) so that users can
dial 911 and it always goes out the local gateway...



Jonathan

On 3/7/07, Kalle Tetto <tettokalle at hotmail.com> wrote:
>
> Hi, one additional question, if the 9 is used to dial out and emergency
> calls are 999, UK i think or 911, could there be a problem. Normally the
> CSS from the EM is taken and then the CSS from the phone. I'm wrong now?
>
> so it would first find the 9.@ route patterns and then 999 or 9999. Or
> is there also the longest match prefered?
>
> All the best
>
> Jonathan Charles schrieb:
> > The Cisco Best practices is to not assign emergency numbers to the
> > device profile for EM, but to the individual phone.
> >
> > This way the CSSs will be concatenated together and they will get 911
> > (or 110, or whatever) based on the phone they log in to, not their
> > device profile.
> >
> > This way you can do planet-wide Extension Mobility and include CSSs on
> > the device for the localization.
> >
> >
> >
> > Jonathan
> >
> >
> > On 3/6/07, *Kalle Tetto* <tettokalle at hotmail.com
> > <mailto:tettokalle at hotmail.com>> wrote:
> >
> >     Hi all,
> >
> >     I want to deploy a Callmanager cluster, and all phones should use
> >     Extension Mobility. We have 2 sites, with one DDI range. All calls
> come
> >     in through the main site. All calls should leave at the Main Site,
> >     except the emergency calls. But if someone moves from the main site
> to
> >     the second site, and he wants to dial emergency numbers, he will
> also
> >     leave at the main site. Now my question, I want to use Device
> mobility
> >     to prevent this. Is this possible or is there any other way to use
> >     Extension Mobility in our company and always select the nearest
> gateway.
> >
> >     All the best and many thanks
> >
> >     _______________________________________________
> >     cisco-voip mailing list
> >     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> >     https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070307/1af22832/attachment.html