?<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [cisco-voip] Repost - Attendant Console presence...</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText81222 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>There is an attribute for the
ipPhone field under every User Object in AD.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Brian</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net on
behalf of Jonathan Charles<BR><B>Sent:</B> Mon 6/11/2007 5:18 PM<BR><B>To:</B>
Patrick Diener<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Repost - Attendant Console presence...<BR></FONT><BR></DIV>
<DIV>
<P><FONT SIZE=2>OK, here is an update... I know why it is broken, but don't know how<BR>
to fix it easily.<BR>
<BR>
Customer is AD integrated. AD has 10-digit extensions for the numbers.<BR>
Only 4-digit on the phones.<BR>
<BR>
LDAP brought in numbers that don't match phone extensions.<BR>
<BR>
How can we fix this without modifying the AD telephone number?<BR>
<BR>
Under LDAP integrations, there is a listing for an ipPHone field...<BR>
where is this in AD?<BR>
<BR>
<BR>
<BR>
Jonathan<BR>
<BR>
On 6/4/07, Patrick Diener <patrick.diener@gmail.com> wrote:<BR>
> the SUBSCRIBE CSS is used for the new "SIP based" presence feature of<BR>
> 5.0 and higher (BLFs, Presence enabled Call Lists, etc...)<BR>
> If a "normal" CSS restricts the Route Patterns where a call setup (in<BR>
> SIP a INVITE message RFC 3261) can be routed to, the SUBSCRIBE CSS<BR>
> regulates from which extensions presence information can be retrieved<BR>
> (done using the SIP SUBSCRIBE message RFC 3265). Hence if you are<BR>
> restricted by the SUBSCRIBE CSS to send a SUBSCRIBE message to an<BR>
> extension no presence info can be retrieved...<BR>
><BR>
> if that applies at all to AC, I don't know...<BR>
><BR>
> Regards<BR>
> Patrick<BR>
><BR>
> On 6/4/07, Jonathan Charles <jonvoip@gmail.com> wrote:<BR>
> > Ah, something new...<BR>
> ><BR>
> > What is a subscribe CSS???<BR>
> ><BR>
> ><BR>
> ><BR>
> > Jonathan<BR>
> ><BR>
> > On 6/4/07, Justin Steinberg <jsteinberg@gmail.com> wrote:<BR>
> > > give this a shot. for your 'ac' user, ensure that you have a<BR>
> > > properly configured 'subscribe css' that has visibility to the<BR>
> > > partitions for the dn's you want to monitor.<BR>
> > ><BR>
> > > i know the subscribe css definately plays a role with presence but<BR>
> > > cant remember if ac needs this or not.<BR>
> > ><BR>
> > > justin<BR>
> > ><BR>
> > > On 6/4/07, Jonathan Charles <jonvoip@gmail.com> wrote:<BR>
> > > > Which users, the AC users or the AC-special user?<BR>
> > > ><BR>
> > > > Or the end-users?<BR>
> > > ><BR>
> > > ><BR>
> > > ><BR>
> > > > Jonathan<BR>
> > > ><BR>
> > > > On 6/4/07, Matt Slaga (US) <Matt.Slaga@us.didata.com> wrote:<BR>
> > > > > AC gets it's pseudo "presence information" from the user accounts.<BR>
> > > > > These accounts need to be application users, and they need the CTI super<BR>
> > > > > provider set as well. 4.x worked the same way. Call routing is based<BR>
> > > > > on pilot points, user information comes from ac account being associated<BR>
> > > > > with devices.<BR>
> > > > ><BR>
> > > > > -----Original Message-----<BR>
> > > > > From: Jonathan Charles [<A href="mailto:jonvoip@gmail.com">mailto:jonvoip@gmail.com</A>]<BR>
> > > > > Sent: Monday, June 04, 2007 1:24 PM<BR>
> > > > > To: Matt Slaga (US)<BR>
> > > > > Cc: Patrick Diener; cisco-voip@puck.nether.net<BR>
> > > > > Subject: Re: [cisco-voip] Repost - Attendant Console presence...<BR>
> > > > ><BR>
> > > > > Yes.<BR>
> > > > ><BR>
> > > > > AC works fine, except for presence.<BR>
> > > > ><BR>
> > > > ><BR>
> > > > ><BR>
> > > > > Jonathan<BR>
> > > > ><BR>
> > > > > On 6/4/07, Matt Slaga (US) <Matt.Slaga@us.didata.com> wrote:<BR>
> > > > > > Well, did you create the pertinent users for 5.x?<BR>
> > > > > ><BR>
> > > > > ><BR>
> > > > > <A HREF="http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_ad">http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_ad</A><BR>
> > > > > > ministration_guide_chapter09186a00806b7f16.html#wp1145819<BR>
> > > > > ><BR>
> > > > > ><BR>
> > > > > ><BR>
> > > > > > -----Original Message-----<BR>
> > > > > > From: Jonathan Charles [<A href="mailto:jonvoip@gmail.com">mailto:jonvoip@gmail.com</A>]<BR>
> > > > > > Sent: Monday, June 04, 2007 12:18 PM<BR>
> > > > > > To: Matt Slaga (US)<BR>
> > > > > > Cc: Patrick Diener; cisco-voip@puck.nether.net<BR>
> > > > > > Subject: Re: [cisco-voip] Repost - Attendant Console presence...<BR>
> > > > > ><BR>
> > > > > > There is no DCD... it is ccm5.1.1b<BR>
> > > > > ><BR>
> > > > > ><BR>
> > > > > > Jonathan<BR>
> > > > > ><BR>
> > > > > > On 6/4/07, Matt Slaga (US) <Matt.Slaga@us.didata.com> wrote:<BR>
> > > > > > > Check to make sure you created the "ac" user in DCD with password<BR>
> > > > > > 12345.<BR>
> > > > > > ><BR>
> > > > > > > -----Original Message-----<BR>
> > > > > > > From: cisco-voip-bounces@puck.nether.net<BR>
> > > > > > > [<A href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Jonathan<BR>
> > > > > > > Charles<BR>
> > > > > > > Sent: Monday, June 04, 2007 11:19 AM<BR>
> > > > > > > To: Patrick Diener<BR>
> > > > > > > Cc: cisco-voip@puck.nether.net<BR>
> > > > > > > Subject: Re: [cisco-voip] Repost - Attendant Console presence...<BR>
> > > > > > ><BR>
> > > > > > > Yeah...<BR>
> > > > > > ><BR>
> > > > > > > AC works fine... except for this... someone suggested the Windows<BR>
> > > > > FW,<BR>
> > > > > > > but it is disabled... someone else suggested disabling their AV...<BR>
> > > > > but<BR>
> > > > > > > I haven't tried it yet.<BR>
> > > > > > ><BR>
> > > > > > ><BR>
> > > > > > > Jonathan<BR>
> > > > > > ><BR>
> > > > > > > On 6/4/07, Patrick Diener <patrick.diener@gmail.com> wrote:<BR>
> > > > > > > > I suppose CTI Manager Service and the CTI User and Password that<BR>
> > > > > is<BR>
> > > > > > > > used by the TCD service has been checked...<BR>
> > > > > > > ><BR>
> > > > > > > > and the AC Application has been downloaded from the currently<BR>
> > > > > > running<BR>
> > > > > > > > CCM Version...<BR>
> > > > > > > ><BR>
> > > > > > > > Regards<BR>
> > > > > > > > Patrick<BR>
> > > > > > > ><BR>
> > > > > > > > On 6/4/07, Jonathan Charles <jonvoip@gmail.com> wrote:<BR>
> > > > > > > > > OK, so, we have installed attendant console on four different<BR>
> > > > > PCs,<BR>
> > > > > > > no<BR>
> > > > > > > > > hunt groups, just a user with AC and the main number on her<BR>
> > > > > > phone...<BR>
> > > > > > > > > she routes the calls where they need to go...<BR>
> > > > > > > > ><BR>
> > > > > > > > > For speed dials and the directory we just have the question-mark<BR>
> > > > > > of<BR>
> > > > > > > doom...<BR>
> > > > > > > > ><BR>
> > > > > > > > > How do we get presence to work?<BR>
> > > > > > > > ><BR>
> > > > > > > > > I have tried all of the previous suggestions... setting the<BR>
> > > > > > > interface,<BR>
> > > > > > > > > etc. No luck...<BR>
> > > > > > > > ><BR>
> > > > > > > > > Call Control is up, the user is online... I have no idea why<BR>
> > > > > this<BR>
> > > > > > > doesn't work.<BR>
> > > > > > > > ><BR>
> > > > > > > > ><BR>
> > > > > > > > ><BR>
> > > > > > > > > Jonathan<BR>
> > > > > > > > > _______________________________________________<BR>
> > > > > > > > > cisco-voip mailing list<BR>
> > > > > > > > > cisco-voip@puck.nether.net<BR>
> > > > > > > > > <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
> > > > > > > > ><BR>
> > > > > > > > _______________________________________________<BR>
> > > > > > > > cisco-voip mailing list<BR>
> > > > > > > > cisco-voip@puck.nether.net<BR>
> > > > > > > > <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
> > > > > > > ><BR>
> > > > > > > _______________________________________________<BR>
> > > > > > > cisco-voip mailing list<BR>
> > > > > > > cisco-voip@puck.nether.net<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 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>
> > > > > ><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>
> > > > ><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>
> > > > _______________________________________________<BR>
> > > > cisco-voip mailing list<BR>
> > > > cisco-voip@puck.nether.net<BR>
> > > > <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
> > > ><BR>
> > ><BR>
> > _______________________________________________<BR>
> > cisco-voip mailing list<BR>
> > cisco-voip@puck.nether.net<BR>
> > <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
> ><BR>
> _______________________________________________<BR>
> cisco-voip mailing list<BR>
> cisco-voip@puck.nether.net<BR>
> <A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
><BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
<A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></FONT></P></DIV>
</BODY>
</HTML>