Avaya Support Forums  

Go Back   Avaya Support Forums > IP Office Contact Center

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11-21-2014, 10:31 AM
sfrits sfrits is offline
Whiz
 
Join Date: Mar 2011
Posts: 49
sfrits has 10 reputation points
Default Reports to Email

Need to send reports automatically to User. Is all I need the FQDN for the Customers SMTP mail server and the email address of the User? Have reports set to automatically output, just need to get to User via email.
Reply With Quote
  #2  
Old 11-22-2014, 06:59 AM
kruegerb kruegerb is offline
Genius
.
 
Join Date: Oct 2013
Location: Stuttgart-Germany
Posts: 276
kruegerb has 12 reputation points
Default

1. step: configure SMTP Server: IPOCC UI -> Administration ->configuration -> Service menu-> special settings: type in the name of the SMTP Server, optional the name of the domain.
2. step: configure Email address in report: IPOCC UI -> Supervision _> Reporting -> open the report, go to Basic data, Output , choose medium, Select the Additionally send as email check box, Enter the email address and subject

Reply With Quote
  #3  
Old 11-11-2016, 01:03 AM
verma62 verma62 is offline
Brainiac
 
Join Date: Apr 2015
Posts: 59
verma62 has 10 reputation points
Default

Hi Krugerb,

I am trying to do it but facing some issues on which I am working. However I am not able to understand here is that when the email will be sent what will be the "FROM" address used.

As this is working without smtp authentication and we are not defining any user authentication details.

Request your guidance on same.

Thanks,
Rajat Verma
Reply With Quote
  #4  
Old 11-14-2016, 08:54 PM
fothma fothma is offline
Aspiring Member
 
Join Date: Nov 2016
Posts: 2
fothma has 10 reputation points
Post g700 console port

Hi there,

I have a problem. I want to access service port g700. So, I used console cable serial to rj45and managed to access. but i have a problem where i cant type any words. when the "login >" appear.. i want to type root, but nothing happen.
Why i could not type? pls advice


thanks

Fariz
Motorola Solutions
Malaysia
Reply With Quote
  #5  
Old 11-15-2016, 11:16 AM
lebon lebon is offline
Genius
.
 
Join Date: Feb 2010
Location: France
Posts: 217
lebon has 10 reputation points
Default

He's the "bug" ;-(
https://kb.avaya.com/kb/index?page=c...=1479136239658

As of IPOCC release 10, SMTP authentication is still not supported in automatic email reporting.

Possible Workaround:
1.Create an email topic.
2.Create an External Destination.
a.This should be your external email target.
3.Create a TaskFlow for the email topic.
a.This should route to an External Destination token.
4.Configure the relayhost and authentication settings in the C3000 SMTP connector.
5.Set the Scheduled report to target the email topic’s email address

The idea is to send the report scheduler to the Topic email then the Task Flow will route that email to the external destination using the SMTP connector settings.
Reply With Quote
  #6  
Old 11-21-2016, 06:25 AM
verma62 verma62 is offline
Brainiac
 
Join Date: Apr 2015
Posts: 59
verma62 has 10 reputation points
Default

Hi Lebon,

Thanks for your detailed description.

But I have a doubt here, steps 1-4 are absolutely ok and work without any issues.

Problem in step 5 is if in daily reports we define the to address as Task flow email address (created in step 1-4), how will system will route it to topic and not to smtp server as defined in configuration.

Actually I tries this as well but wasn't able to make it working. I am not sure if I am making some mistakes here.

As a workaround I installed hMail server and sent the mail from IPOCC reporting to one of address created in hmail server, configured the property to forward all the emails here to one of destination(This is address where we need to send the reports finally) and it worked.
Reply With Quote
  #7  
Old 11-21-2016, 10:44 PM
marquardt marquardt is offline
Guru
.
 
Join Date: May 2014
Location: Stuttgart - Germany
Posts: 190
marquardt has 14 reputation pointsmarquardt has 14 reputation points
Default see also

https://support.avaya.com/forums/showthread.php?t=10629

The smtp sender for reporting mails works without authentication.

The SMTP connector is NOT used for sending reports per E-mail.

You can use the SMTP connector (and the appropriate settings for the relay host). But then you have to configure some settings.

1. Creale in the IPOCC a topic for E-mail, example reporting@ipoccserver
2. In the configuration set the reporting settings to the IPOCC Server.
SMTP Server ipoccserver
Domain: ipoccserver
3. Send the report to the internal E-Mail address, example reporting@ipoccserver
4. Create an external Destination (example@googlemail.com)
5. Create a taskflow for the topic. Connect to an external Destination.
6. The report will be send internal to the topic and then with the
faskflow to the external destination (via SMTP connector)
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:53 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.