<div>Ah Yes. That is why I have heard the TAPS lady say "enter the telephone number..." She was refering to the external mask.</div>
<div> </div>
<div>Thank you, that is good information!</div>
<div> </div>
<div>Steve<br><br> </div>
<div><span class="gmail_quote">On 10/11/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">Got a response from the Cisco IP Telephony Forum that pointed me to<br>this:<br><br>Using TAPS to Configure Shared-line Phones
<br>If you are planning to use TAPS to configure shared-line phones, you<br>must create unique external mask for each shared-line phone. Enter a<br>unique combination of numbers and asterisks (*) for the external mask.<br>
For more information, see<br><a href="http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20093">http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec20093</a>.<br><br><br><br><br>>>> "Matt Slaga (US)" <
<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>> 10/11/06 10:34 AM >>><br>No, it's not a device limitation but a line limitation. When you call<br>into TAPS and input your number the database searches for that number.
<br>If there is more than one, it doesn't know which profile to push out<br>and<br>fails. I'm not sure when or if they will fix this, but I wouldn't<br>imagine adding a few more IVR questions to determine which phone it<br>
would be. Of course, to be of any use they would need text to speech<br>capabilities to read off the identifying records like "description"<br>and<br>"display".<br><br>________________________________
<br><br>From: Steve G [mailto:<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>]<br>Sent: Tuesday, October 10, 2006 8:28 PM<br>To: STEVEN CASPER<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a>; Matt Slaga (US)<br>Subject: Re: [cisco-voip] TAPS - Multiple Appearance DNs<br><br><br>I could be wrong (I've been before), but can't you use taps to<br>configure<br>the same DN on different phone types? Say, I have a 7960 and a 7912
<br>with a shared DN.<br><br>Does that work?<br><br><br>On 10/10/06, STEVEN CASPER <<a href="mailto:SCASPER@mandtbank.com">SCASPER@mandtbank.com</a>> wrote:<br><br> 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<br>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<br>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<br>STEVEN<br>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<br>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,<br>please<br> notify us immediately by replying to this message and deleting
<br>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><br><br><br><br><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></blockquote></div><br>