<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY
style="WORD-WRAP: break-word; khtml-nbsp-mode: space; khtml-line-break: after-white-space">
<DIV dir=ltr align=left><SPAN class=371395519-17102006><FONT face=Tahoma
color=#0000ff size=2>The customer is thinking the 1st line is the ACD
extension. The 2nd line is a personal extension. Only IPCC can call
Line 1. Anyone may call line 2. Neither line will have
voicemail. </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> Matt Slaga (US)
[mailto:Matt.Slaga@us.didata.com] <BR><B>Sent:</B> Tuesday, October 17, 2006
8:30 AM<BR><B>To:</B> Wes Sisk; Carter, Bill<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> RE: [cisco-voip] Send line busy
when on 1st line<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=390252813-17102006><FONT face=Arial
color=#0000ff size=2>Actually, this would be the first customer to be able to
use CallBack that I have seen to date. You know, that new feature that no
one can use, well, except this one.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=390252813-17102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=390252813-17102006></SPAN><SPAN
class=390252813-17102006></SPAN><SPAN class=390252813-17102006><FONT face=Arial
color=#0000ff size=2></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> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Wes
Sisk<BR><B>Sent:</B> Tuesday, October 17, 2006 9:21 AM<BR><B>To:</B> Carter,
Bill<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Send line busy when on 1st line<BR></FONT><BR></DIV>
<DIV></DIV>you could configure line1 to callforwardbusy to voicemail and set
busy trigger=1 on the line.
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>however, this does not address how anyone will call line2.� Should line2 be
callable on the system or is it reserved for outbound calls?</DIV>
<DIV>or possibly, is the customer thinking of line2 as the 2nd line to do a
transfer, in which case you can just use 1 line configured as above.</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>/Wes</DIV>
<DIV><BR>
<DIV>
<DIV>On Oct 16, 2006, at 10:01 PM, Carter, Bill wrote:</DIV><BR
class=Apple-interchange-newline>
<DIV><SPAN class=372465601-17102006><FONT face=Tahoma size=2>I have a strange
request from a customer.� They will have DNs configured on line 1 and 2.� There
will be no connection between the two lines, they are just standalone
lines�(i.e. line partition 1, line 2 partition 2).</FONT></SPAN></DIV>
<DIV><SPAN class=372465601-17102006><FONT face=Tahoma
size=2></FONT></SPAN>�</DIV>
<DIV><SPAN class=372465601-17102006><FONT face=Tahoma size=2>Here is what they
want.� When they are talking on the first DN, they don't want to receive calls
on line 2.� Basically they want the line to ring busy.</FONT></SPAN></DIV>
<DIV><FONT face=Tahoma size=2></FONT>�</DIV>
<DIV align=left><STRONG><FONT face=Tahoma size=2></FONT></STRONG>�</DIV>
<DIV align=left><STRONG><FONT face=Tahoma size=2>Bill
Carter</FONT></STRONG></DIV>
<DIV align=left><FONT face=Tahoma size=2>Sr. Business Communications
Analyst</FONT></DIV>
<DIV align=left><FONT face=Tahoma size=2>Sentinel Technologies</FONT></DIV>
<DIV align=left><FONT face=Tahoma size=2>(O) 217.391.5015</FONT></DIV>
<DIV>�</DIV>
<DIV style="MARGIN: 0px">_______________________________________________</DIV>
<DIV style="MARGIN: 0px">cisco-voip mailing list</DIV>
<DIV style="MARGIN: 0px"><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A></DIV>
<DIV style="MARGIN: 0px"><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A></DIV></DIV><BR></DIV>
<P>
<HR SIZE=1>
<P></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><pre>
This email may contain proprietary and confidential information for the sole use of the intended recipient.
Any review, retransmission, dissemination, or other use of this information by persons or entities other than
the intended recipient is prohibited. If you are not the intended recipient, please contact the sender and
delete all copies. To the extent that opinions are expressed in this message, they are not necessarily the
opinions of Sentinel Technologies or any of its affiliates, employees, directors, officers or shareholders.
</pre></BODY></HTML>