[cisco-voip] Extension Mobility, Emergency Calls

[Jonathan Charles]

I personally NEVER use the 9. at ... it is an administration nightmare and
makes troubleshooting far more difficult.

If your emergency number is 999 and your access code is 9, then 999 and 9999
are both set as urgent priority, the 9999 pattern will NEVER be selected.
(the 999 will match first and the system will not wait for further digits).

This will work fine.



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/4e73f30d/attachment.html