<div>Guys thanks very much for your responses. I think I see a couple of options to try.</div>
<div>Thank you very much. If there is any other comments on this out there, please bring them forward.</div>
<div> </div>
<div>Steve<br><br> </div>
<div><span class="gmail_quote">On 6/6/05, <b class="gmail_sendername">Dave Temkin</b> <<a href="mailto:dave@ordinaryworld.com">dave@ordinaryworld.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">One problem with this is they will get no caller ID on the Nortel most<br>likely (due to issues with Nortel
Q.SIG). If this is acceptable then yes,<br>that would work...<br><br><br>On Mon, 6 Jun 2005, Wes Sisk wrote:<br><br>> You could almost get there by routing all calls to the CM side first.<br>> Configure a short forward no answer timer, and have the CFNA go to the
<br>> Nortel phone. Users that receive no answer when ip communicator is<br>> registered will have to wait a few extra ring cycles. Users that get no<br>> answer when IP Communicator is not registered will not notice a difference.
<br>><br>> IP Communicator users will have the option of answering with IP when IPC<br>> is registered, otherwise calls will route to their notel phones.<br>><br>> /Wes<br>><br>> Dave Temkin wrote:<br>
><br>> >Only way I found to do this was using a line-side T1 from the Nortel and<br>> >assigning each extension to a channel and setting them up as FXS lines.<br>> ><br>> >Ugly, but no, on the Nortel side it's not possible to present a call to
<br>> >both Q.SIG and a local phone without some very very expensive packages<br>> >(used for DR type scenarios)<br>> ><br>> ><br>> >On Mon, 6 Jun 2005, Steve G wrote:<br>> ><br>> >
<br>> ><br>> >>Hello,<br>> >>Is it possible to share an extension between a Nortel PBX phone and<br>> >>CCM4.0IP Communicator using QSIG to link the two together? My goal is<br>> >>to initially
<br>> >>have people using IP Communicator with the same extension as their Nortel<br>> >>Phone. This would make migration from TDM to IP phones very smooth.<br>> >><br>> >>Thank you,<br>
> >>Steve<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></blockquote></div><br>