<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Re: [cisco-voip] Intercom and Extension Mobility?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>That is correct. Icom will only show/work with base designated phone. Wonder if anyone knows if it will be supported in an upcoming release.?<BR>
<BR>
Joe<BR>
<BR>
----- Original Message -----<BR>
From: cisco-voip-bounces@puck.nether.net <cisco-voip-bounces@puck.nether.net><BR>
To: cisco-voip@puck.nether.net <cisco-voip@puck.nether.net><BR>
Sent: Mon Aug 31 19:17:11 2009<BR>
Subject: [cisco-voip] Intercom and Extension Mobility?<BR>
<BR>
I'm reading the description of how Intercom works with Extension Mobility,<BR>
and it seems like the two of them won't work together.<BR>
<BR>
If I'm parsing the docs, even under 7.1, if a user uses EM because they<BR>
travel to another office, and they have Intercom enabled on the EM profile,<BR>
but the default device (I'm assuming they mean hard phone) is set for the<BR>
phone in their home office, the Intercom _will not appear_ on the phone<BR>
that they've logged into at the remote office? Even if EM is configured to<BR>
only allow a single login?<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
</FONT>
</P>
</BODY>
</HTML><HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>