I've tested this before in my lab, and if you have two single line DNs the phone will attempt to use the next line for the transfer. Much like how you can conference 2 calls on two different lines in CME.<br><br>The use case was this -> Every user had two phone lines, the first was a shared DN (1000) and the second line was their personal (2XXX). They said that when they transferred calls the other person would know who was transferring it, and something had changed and prevented that. I didn't think that was possible, but after finding out that the phone would use the second line this was possible. Kind of a cool-but-clunky way of making it work.<br>
<br>-nick<br><br><div class="gmail_quote">On Sun, Nov 28, 2010 at 6:37 AM, Jim McBurnett <span dir="ltr"><<a href="mailto:jim@tgasolutions.com">jim@tgasolutions.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<div style="font-family: Arial,Helvetica,sans-serif; font-size: small; color: black;"><span style="font-family: Arial,Helvetica,sans-serif; font-size: small; color: black;">This is true us you are doing full consultative transfer.. For blind transfer you don't need that second line.<br>
<br></span><div><div></div><div class="h5"><br><br>-----Original Message----- <br><b>From:</b> Peter Slow [<a href="mailto:peter.slow@gmail.com" target="_blank">peter.slow@gmail.com</a>]<br><b>Received:</b> Saturday, 27 Nov 2010, 7:24pm<br>
<b>To:</b> Jason Aarons (US) [<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>]<br><b>CC:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> [<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>]<br>
<b>Subject:</b> Re: [cisco-voip] Call Transfer on CCME without dual-line?<br><br></div></div></div><div><div></div><div class="h5">
<font size="2"><div>According to the documentation, you just need more than one<br>
single-line DN on a particular phone. I vaguely recall having tested<br>
this, but in the event that I'm wrong, I'm pointing the finger at the<br>
documentation.<br>
<br>
I believe this carries over from how transfer worked before there were<br>
dual-line DNs. according to the command reference, dual-line was a<br>
feature added significantly after CME (ITS) was created.<br>
<br>
<a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_e1ht.html#wp1036270" target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_e1ht.html#wp1036270</a><br>
ephone-dn<br>
Cisco IOS Release Cisco Product Modification<br>
12.1(5)YD Cisco ITS 1.0 This command was introduced.<br>
12.2(8)T Cisco ITS 2.0 This command was integrated into Cisco IOS<br>
Release 12.2(8)T.<br>
12.2(15)ZJ Cisco CME 3.0 The dual-line keyword was added.<br>
12.3(4)T Cisco CME 3.4 The dual-line keyword was integrated into<br>
Cisco IOS Release 12.3(4)T.<br>
<br>
<br>
....On a different note, Ariel, I think you could probably ALSO do<br>
what you're wanting to do through the use of the huntstop channel<br>
command, which would keep calls from hunting to the second channel of<br>
a dual-line DN should the first be busy. See the below,<br>
<br>
<a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_h1ht.html#wp1022686" target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_h1ht.html#wp1022686</a><br>
huntstop (ephone-dn and ephone-dn-template)<br>
To disable call hunting for directory numbers or channels, use the<br>
huntstop command in ephone-dn or ephone-dn-template configuration<br>
mode. To reset to the default, use the no form of this command.<br>
huntstop [channel number-of-channels]<br>
no huntstop [channel number-of-channels]<br>
<br>
Syntax Description<br>
channel - (Optional) For dual-line and octo-line directory<br>
numbers. Prevents incoming calls from hunting to the next channel if<br>
the first channel is busy or does not answer.<br>
number-of-channels - Supported for octo-line directory numbers<br>
only. Number of channels available to accept incoming calls. Remaining<br>
channels are reserved for outgoing calls or features such as call<br>
transfer, call waiting, and conferencing. Range: 1 to 8. Default: 8.<br>
<br>
-Peter<br>
<br>
<br>
On Sat, Nov 27, 2010 at 5:19 PM, Jason Aarons (US)<br>
<<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>> wrote:<br>
><br>
> You need dual-line or octo-line.<br>
><br>
><br>
><br>
> Transfer places the call on hold, give you a second line…thus without dual-line or octo-line it won’t work -jason<br>
><br>
><br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of ROZA, Ariel<br>
> Sent: Friday, November 26, 2010 10:47 AM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] Call Transfer on CCME without dual-line?<br>
><br>
><br>
><br>
> Hi, guys!<br>
><br>
><br>
><br>
> Does anyone know if it Is possible to configure Call Transfers and Call forwards in CCME without configuring the lines as dual-line?<br>
><br>
> I have a requirement to disable call waiting and allow call transfers at the same time.<br>
><br>
><br>
><br>
> I am working with a CCME 4.1, but I can propose an upgrade if it´s required.<br>
><br>
><br>
><br>
> Regards,<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> ARIEL ROZA<br>
> Advanced Engineering<br>
><br>
><br>
><br>
> LOGICALIS<br>
> Perú 327 1er Piso - C.A.B.A. - Argentina - C1067AAG<br>
> Tel/Fax: +54 (11) 4344-0300<br>
> <a href="mailto:ariel.roza@la.logicalis.com" target="_blank">ariel.roza@la.logicalis.com</a><br>
> <a href="http://www.la.logicalis.com" target="_blank">www.la.logicalis.com</a><br>
> <a href="http://www.logicalisnow.com" target="_blank">www.logicalisnow.com</a><br>
><br>
> Por favor, piense en el medioambiente antes de imprimir este email.<br>
> La presente información se envía únicamente para el destinatario, y contiene información de carácter CONFIDENCIAL o PRIVLEGIADA.<br>
> La modificación, retransmisión, difusón, copia u otro uso de esta información por cualquier medio, por personas distintas al destinatario, están estrictamente prohibidas.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> ________________________________<br>
><br>
> 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.<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></font>
</div></div></div>
<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>