06-02-2009 09:40 PM - edited 03-18-2019 11:09 PM
I am running into some issues with getting calendaring working on our CUPS 7.0 deployment.
After a lot of trial and error it seems like I have overcome the certificate issue between CUPS and our exchange 2007 server.
The output below is the tracelog file with presence engine and presence Db info. And it looks as if the presence server is successfull in loging into the OWA backend (exchange server). I have set a test meeting in my calendar and set it to "show as busy". Calendaring is on on my CUPC client, yet the status on there still is not updated as "in a meeting".
any ideas?
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2094238 DEBUG -->OwaBackendAdapter.processRequest
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2094238 DEBUG uri: sip:dmink@arcbs.redcross.org.au@sme.arcbs.redcross.org.au:443
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2094238 DEBUG -->Calendar.attach sip:dmink@arcbs.redcross.org.au@sme07.arcbs.redcross.org.au:443
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2094238 DEBUG <--CalendarSubscription.ctor sip:dmink@arcbs.redcross.org.au@sme.arcbs.redcross.org.au:443
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2094238 DEBUG -->CalendarSubscription::attach: dmink@arcbs.redcross.org.au 0
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG -->QMS::SUBSCRIBE dmink@arcbs.redcross.org.au
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG -->SessionManager::allocateSession dmink@arcbs.redcross.org.au
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG serverport: smemel07.arcbs.redcross.org.au:443
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG <--SessionManager.ctor 162667480
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG <--SessionManager.clear 162667480
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG <--SessionManager.set 162667480 sme.arcbs.redcross.org.au:443 cupadmin calendar
06/03/2009 15:00:14.311 EPE|system.pe.pa.owa.backend 2128166 DEBUG <--SessionManager::allocateSession smem.arcbs.redcross.org.au:443
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2128166 DEBUG ---->QMS::SUBSCRIBE dmink@arcbs.redcross.org.au
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2128166 INFO send SUBSCRIBE dmink@arcbs.redcross.org.au 0
06/03/2009 15:00:14.312 EPE|debug.oam.metrics 2094238 DEBUG Using cached metric: pe.metrics.subscribe.sent.calendar.initial
06/03/2009 15:00:14.312 EPE|system.pe.oam 2094238 DEBUG PeMetrics::updateMetrics: incrementing metric- pe.metrics.subscribe.sent.calendar.initial
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2094238 DEBUG <--CalendarSubscription::doSUBSCRIBE: dmink@arcbs.redcross.org.au
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2094238 DEBUG <--CalendarSubscription::attach: dmink@arcbs.redcross.org.au
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2094238 DEBUG Calendar::attach succeeded.
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2094238 DEBUG <--Calendar.attach sip:dmink@arcbs.redcross.org.au@smemel07.arcbs.redcross.org.au:443
06/03/2009 15:00:14.312 EPE|system.pe.pa.owa.backend 2094238 DEBUG <--OwaBackendAdapter.processRequest
06-03-2009 04:41 AM
06-03-2009 08:05 PM
06-03-2009 08:09 PM
in addition to this seems like I am still having a certificate issue. unsure how to fix that.
06-03-2009 08:35 PM
We have to fix the certificate issue first.
Per the log message "SESSION_HOSTNAME_DOES_NOTMATCH_CERTIFICATE_HOSTNAME - rejected", the presence gateway you configured in CUPS does not match with the name in certificate.
I guess you used IP address in pres gw and DNS name in certificate?
Michael
06-03-2009 10:20 PM
Pretty much, I set it up on a exchange server that did not run OWA initially, based on IP address as hostname.
how do I go about this? remove the outlook gateway and re-add it?
06-03-2009 10:31 PM
06-04-2009 04:50 AM
The current setup looks good. You shouldn't have received certificate error.
If you did, you need packet capture between CUPS and Exchange.
Michael
07-09-2009 05:00 PM
I finally found some time to sort out the certificate issue (I have added alternative names to the certificate). that is now good.
I now have the following issue on the same deployment:
07/10/2009 10:07:17.290 EPE|system.pe.pa.owa.backend 2108634 DEBUG -->OwaBackendAdapter.clearCalendar sip:dmink@arcbs.redcross.org.au@smemel07.arcbs.redcross.org.au:443
|<:STANDALONECLUSTER><:10.40.123.85><:DETAILED><:0800>
07/10/2009 10:07:17.290 EPE|system.pe.pa.sip.subscribe 2082166 DEBUG subscription state string is: active;expires=622
|<:STANDALONECLUSTER><:10.40.123.85><:DETAILED><:0800>
07/10/2009 10:07:17.290 EPE|system.pe.pa.owa.backend 2108634 ERROR Exchange Server Transaction Failed: SUBSCRIBE sip:dmink@arcbs.redcross.org.au@smemel07.arcbs.redcross.org.au:443 3 Authentication failure on server; Could not authenticate to server
the thing is that when I try to log onto the exchange server (smemel07.arcbs.redcross.org.au:443) using dmink@arcbs.redcross.org.au as CUPS would, I can log on no problem.
Your help is greatly appreciated
07-09-2009 07:14 PM
What version is Exchange? Exchange 2003 SP1 is the minimum version supported.
Michael
07-09-2009 10:06 PM
We run Exchange 2007
07-10-2009 07:57 AM
Based on "Authentication failure on server", the service account does not have permission to access end users' mailboxes.
Assuming the account name and password was correct, you may run the command below on Exchange shell to check permissions:
Get-MailboxPermission johndoe -user cupsexch | Format-Table -autosize
Where 'johndoe' is the end user account. 'cupsexch' is the service account.
Michael
08-24-2009 09:30 AM
Did you ever find a resolution to your calendaring issue? I am experiencing the same issue and have not found a solution yet.
Thanks,
BC
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: