[cisco-voip] Repost - Attendant Console presence...

Jonathan Charles jonvoip at gmail.com
Mon Jun 11 17:40:41 EDT 2007


Yeah, found it.

But how do we change over without nuking the users out? I don't want
to have to go back and re-associate every device and create new PIN
numbers.



Jonathan

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


More information about the cisco-voip mailing list