<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
how often do you expect to be in SRST? that should be the exception
and not the rule.<br>
<br>
Nick Kassel wrote:
<blockquote
cite="mid253FAE7A06B11B49A3A29770B2B8BAFC648246@CSEXCH01.charles-stanley.co.uk"
type="cite">
<pre wrap="">Forgot to mention we are using CM 4.1(3)SR1
-----Original Message-----
From: Nick Kassel
Sent: Wednesday, February 22, 2006 3:44 PM
To: 'Wes Sisk'
Subject: RE: [cisco-voip] Attendant console & shared lines
Wes
We would like to use the attendant console for one of our branch
offices, they have a receptionist who sits on her own and then all the
other staff in one open room, the reason we would like to use a shared
line in the hunt group is so if she is busy or unavailable the calls
will go through to the main room and ring on all the phones so anyone
can answer it. The shared line would sit as the second DN in the hunt
group. Also in SRST for our main line coming in the only way we can get
all the phones to ring at the same time would be to have shared lines.
We did look at broadcast hunt groups for our main numbers but due to the
SRST issue and also the problem of not being able to set up a unity
mailbox for the main line decided not to go with them.
Nick
-----Original Message-----
From: Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>]
Sent: Wednesday, February 22, 2006 2:30 PM
To: Nick Kassel
Cc: <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
Subject: Re: [cisco-voip] Attendant console & shared lines
it depends on where you use the shared line and what version of CM you
are on.
we say DO NOT DO IT because CTI control of shared lines does not work
well. There are several call flows and state transitions that do not
work and cause the CTI application (TCD in this case) to become
confused.
AC client itself in older version of CM would allow you to attempt to
control a shared line and that appeared to work until you hit one of the
untested state transitions. The the client went dumb. Later versions of
ACClient will not even allow you to open/control a shared line for this
reason.
It's just not a good idea to use ACClient to attempt to control a shared
line.
A shared line can exist in a huntgroup with some mixed results, but why?
Why not just use a broadcast huntgroup?
/Wes
Nick Kassel wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I know in the documentation is says that you must not use shared lines
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">with the attendant console but I have been told by someone that this
can be done, I would like to use 1 shared line in the hunt group, has
anyone tried this before and does it work?
</pre>
</blockquote>
<pre wrap=""><!---->************************************************************************
***********************
</pre>
<blockquote type="cite">
<pre wrap="">The information contained in this e-mail is strictly confidential,
</pre>
</blockquote>
<pre wrap=""><!---->some or all
</pre>
<blockquote type="cite">
<pre wrap="">of which may be legally privileged. It is for the intended recipient
</pre>
</blockquote>
<pre wrap=""><!---->only.
</pre>
<blockquote type="cite">
<pre wrap="">Access to this e-mail by any other person is prohibited. If you are
</pre>
</blockquote>
<pre wrap=""><!---->not the
</pre>
<blockquote type="cite">
<pre wrap="">intended recipient, any use, disclosure, copying, printing,
</pre>
</blockquote>
<pre wrap=""><!---->distribution of,
</pre>
<blockquote type="cite">
<pre wrap="">replying to or any action taken or omitted to be taken in reliance on
</pre>
</blockquote>
<pre wrap=""><!---->this
</pre>
<blockquote type="cite">
<pre wrap="">e-mail, is prohibited and may be unlawful. Please contact the sender
</pre>
</blockquote>
<pre wrap=""><!---->immediately
</pre>
<blockquote type="cite">
<pre wrap="">should this e-mail have been incorrectly addressed or transmitted.
You accept that any instructions are deemed to have been given at the
</pre>
</blockquote>
<pre wrap=""><!---->time the
</pre>
<blockquote type="cite">
<pre wrap="">recipient(s) accesses them and that delivery receipt does not
</pre>
</blockquote>
<pre wrap=""><!---->constitute
</pre>
<blockquote type="cite">
<pre wrap="">acknowledgement or receipt by the intended recipient(s). You accept
</pre>
</blockquote>
<pre wrap=""><!---->that there
</pre>
<blockquote type="cite">
<pre wrap="">may be a delay in processing the instructions received from e-mails
</pre>
</blockquote>
<pre wrap=""><!---->after
</pre>
<blockquote type="cite">
<pre wrap="">Charles Stanley has received them. You are advised that urgent, time
</pre>
</blockquote>
<pre wrap=""><!---->sensitive
</pre>
<blockquote type="cite">
<pre wrap="">and confidential communications should not be sent by e-mail.
You acknowledge that e-mails are not secure and you accept the risk of
malfunction, viruses, unauthorised interference, mis-delivery or
</pre>
</blockquote>
<pre wrap=""><!---->delay.
</pre>
<pre wrap=""><!---->************************************************************************
************************
</pre>
<blockquote type="cite">
<pre wrap="">
Charles Stanley & Co. Ltd
Registered Office: 25 Luke Street London EC2A 4AR
Tel: 0207 739 8200 Fax: 0207 739 7798
Registered in England No. 1903304
Charles Stanley Sutherlands and Tozer Wingate are divisions of Charles
</pre>
</blockquote>
<pre wrap=""><!---->Stanley & Co. Ltd
</pre>
<blockquote type="cite">
<pre wrap="">Authorised and Regulated by the Financial Services Authority, Member
</pre>
</blockquote>
<pre wrap=""><!---->of the
</pre>
<blockquote type="cite">
<pre wrap="">London Stock Exchange, International Securities Markets Association,
</pre>
</blockquote>
<pre wrap=""><!---->and The London International Financial Futures &
</pre>
<blockquote type="cite">
<pre wrap="">Options Exchange.
This footnote also confirms that this email message has been swept by
</pre>
</blockquote>
<pre wrap=""><!---->McAfee
</pre>
<blockquote type="cite">
<pre wrap="">VirusScan and SurfControl Email Filter software.
</pre>
</blockquote>
<pre wrap=""><!---->------------------------------------------------------------------------
</pre>
<blockquote type="cite">
<pre wrap="">_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>