[cisco-voip] Extension Mobility, Emergency Calls
Patrick Diener
patrick.diener at gmail.com
Tue Mar 6 08:50:38 EST 2007
Since you do not move your actual physical devices, i don't think you
can use the device mobility feature to achieve your goal.
since a calling search space decides on which site emergeny calls will
leave your IPT domain use a seperate css on devices located at your
main site and devices located at the branch.
to maintain calling restrictions for each individual extension
mobility user, you can use a specific css on each device profile. The
css on the device profile and the css on the device on which the user
is logged in will be combined.
e.g.
Partitions:
PSTN (assigned to all route patterns which will point to the PSTN at
the main site)
EMERGENCY_SITE1 (emergency route pattern pointing to PSTN at Site1)
EMERGENCY_SITE2 (emergency route pattern pointing to PSTN at Site2)
CSS:
PSTN_Site1 = PSTN, EMERGENCY_SITE1
PSTN_Site2 = PSTN, EMERGENCY_SITE2
To a device located at Site1 assign css PSTN_Site1, to a device
located at Site2 assign css PSTN_Site2...
helpful?
Patrick
On 3/6/07, Kalle Tetto <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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
More information about the cisco-voip
mailing list