<div>The Cisco Best practices is to not assign emergency numbers to the device profile for EM, but to the individual phone.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>This way you can do planet-wide Extension Mobility and include CSSs on the device for the localization.</div>
<div> </div>
<div> </div>
<div> </div>
<div>Jonathan<br><br> </div>
<div><span class="gmail_quote">On 3/6/07, <b class="gmail_sendername">Kalle Tetto</b> <<a href="mailto:tettokalle@hotmail.com">tettokalle@hotmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi all,<br><br>I want to deploy a Callmanager cluster, and all phones should use<br>Extension Mobility. We have 2 sites, with one DDI range. All calls come
<br>in through the main site. All calls should leave at the Main Site,<br>except the emergency calls. But if someone moves from the main site to<br>the second site, and he wants to dial emergency numbers, he will also<br>
leave at the main site. Now my question, I want to use Device mobility<br>to prevent this. Is this possible or is there any other way to use<br>Extension Mobility in our company and always select the nearest gateway.<br><br>
All the best and many thanks<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br>