<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.5700.6" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=609433114-11102006><FONT face=Arial
color=#0000ff size=2>No, it's not a device limitation but a line
limitation. When you call into TAPS and input your number the database
searches for that number. If there is more than one, it doesn't know which
profile to push out and fails. I'm not sure when or if they will fix this,
but I wouldn't imagine adding a few more IVR questions to determine which phone
it would be. Of course, to be of any use they would need text to speech
capabilities to read off the identifying records like "description" and
"display".</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Steve G [mailto:smgustafson@gmail.com]
<BR><B>Sent:</B> Tuesday, October 10, 2006 8:28 PM<BR><B>To:</B> STEVEN
CASPER<BR><B>Cc:</B> cisco-voip@puck.nether.net; Matt Slaga
(US)<BR><B>Subject:</B> Re: [cisco-voip] TAPS - Multiple Appearance
DNs<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>I could be wrong (I've been before), but can't you use taps to configure
the same DN on different phone types? Say, I have a 7960 and a 7912 with a
shared DN.</DIV>
<DIV> </DIV>
<DIV>Does that work?<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 10/10/06, <B class=gmail_sendername>STEVEN
CASPER</B> <<A
href="mailto:SCASPER@mandtbank.com">SCASPER@mandtbank.com</A>> wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Thanks
for the response.<BR><BR>Converting from a traditional PBX environment I
consider that a<BR>serious limitation. I wonder if there is any chance TAPS
can be used <BR>with shared lines in a future
release.<BR><BR>Steve<BR><BR>>>> "Matt Slaga (US)" <<A
href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</A>>
10/10/06 6:02 PM >>><BR>You cannot use TAPS with shared lines.
<BR><BR>-----Original Message-----<BR>From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>[mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</A>] On Behalf Of STEVEN CASPER<BR>Sent: Tuesday, October 10, 2006 1:19
PM<BR>To: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
[cisco-voip] TAPS - Multiple Appearance DNs<BR><BR>Is there any way that TAPS
can be used to add phones that have<BR>Multiple<BR>Appearance Directory
numbers?<BR><BR>Thanks!<BR>Steve<BR><BR><BR><BR>Steve Casper<BR>Voice
Technologies<BR>M&T Bank<BR>(410)
347-6026<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><BR>-----------------------------------------<BR>Disclaimer:<BR><BR>This
e-mail communication and any attachments may contain<BR>confidential and
privileged information and is for use by the<BR>designated addressee(s) named
above only. If you are not the <BR>intended addressee, you are
hereby notified that you have received<BR>this communication in error and that
any use or reproduction of<BR>this email or its contents is strictly
prohibited and may be<BR>unlawful. If you have received this
communication in error, please <BR>notify us immediately by replying to this
message and deleting it<BR>from your computer. Thank
you.<BR><BR><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></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>