Hi all,
I was able to make it work by setting the filter to @ and I also set the Sender property.
Sorry for creating a ticket a little more trial and error did the trick.
Best Regards,
LP
Search found 26 matches
- 26 Aug 2019, 12:40
- Forum: Help
- Topic: Block ticket from being created using e-mail (NewTicketReject)
- Replies: 1
- Views: 1179
- 26 Aug 2019, 12:03
- Forum: Help
- Topic: Block ticket from being created using e-mail (NewTicketReject)
- Replies: 1
- Views: 1179
Block ticket from being created using e-mail (NewTicketReject)
Hi all, I'm trying to use the PostMaster::PreFilterModule###3-NewTicketReject configuration to reject all the e-mails that don't contain the ticket identification in the title. The customer can only open new tickets using the web interface, but replies can be done using the e-mail. I set the match s...
- 03 Apr 2018, 16:45
- Forum: Help
- Topic: [SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
- Replies: 6
- Views: 11016
[Solved] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
Hi, I will answer to my own question. Thanks for all the help Roy, I tried to discover a yml for the GenericTicketConnectorREST, for some reason, I was under the impression that this was a service available out of the box. After importing the service, everything start working again. So sorry if this...
- 03 Apr 2018, 16:19
- Forum: Help
- Topic: [SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
- Replies: 6
- Views: 11016
Re: Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
Just configured a service, but no change is visible. Must it be some particular kind of web service? Thanks for the help. YML: --- Debugger: DebugThreshold: debug TestMode: '0' Description: '' FrameworkVersion: 5.0.13 Provider: Transport: Config: KeepAlive: '1' MaxLength: '9999999999' Type: HTTP::RE...
- 03 Apr 2018, 14:03
- Forum: Help
- Topic: [SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
- Replies: 6
- Views: 11016
Re: Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
Hi Roy,
no, none, do I have to configure a custom web service to make this available?
Thanks for reply,
Luís Pinho
no, none, do I have to configure a custom web service to make this available?
Thanks for reply,
Luís Pinho
- 03 Apr 2018, 11:49
- Forum: Help
- Topic: [SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
- Replies: 6
- Views: 11016
Re: Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
Just tried an even simpler request and got the same result:
http://company.com/otrs/nph-genericinte ... myPassword
http://company.com/otrs/nph-genericinte ... myPassword
- 03 Apr 2018, 11:25
- Forum: Help
- Topic: [SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
- Replies: 6
- Views: 11016
[SOLVED] Trying to make a rest call fails. Log found: "Could not load web service configuration for web service"
Hi all, I made a small application a few months ago that made a rest call to create a special type of ticket using the GenericTicketConnectorREST. The code worked without any problem. I tried to run the application yesterday and I keep getting an error "The server did not return a complete resp...
- 22 Nov 2017, 19:41
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hi all,
our local Linux expert was able to configure sendmail correctly to work with Office 365.
Now, it takes only 1 seconds to sent all mails
Thanks for all your help
our local Linux expert was able to configure sendmail correctly to work with Office 365.
Now, it takes only 1 seconds to sent all mails
Thanks for all your help
- 22 Nov 2017, 16:41
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
2017-11-22 11_44_56-Framework -_ Core__Sendmail - SysConfig - Admin.png I see that its parameters are -i -f Those parameters do not matter as you've chosen "SMTPTLS" as the sendmail module, not "Sendmail" Maybe that's my way out of this, configuring the sendmail module to use of...
- 22 Nov 2017, 13:53
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hi all, looking at the configuration of the SendMail: 2017-11-22 11_44_56-Framework -_ Core__Sendmail - SysConfig - Admin.png I see that its parameters are -i -f I've search for sendmail module manual, and I see several version for it, can anyone point me to the correct manual? (I'm a bit rusty went...
- 22 Nov 2017, 12:55
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
You could set $Self->{Debug} to 1 (https://github.com/OTRS/otrs/blob/rel-5_0/Kernel/System/Ticket.pm#L87) and rerun the ticket creation. Then you'll see debug output in the logfile (set minimumloglevel in SysConfig to "debug"). You can go to SysConfig and search for "Ticket::Permissi...
- 22 Nov 2017, 12:34
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Everything thing seems to be ok.fcasal wrote:I would update to the last patch level 32, because they have corrected many options.
I also check again if the modules are well installed:
shell> perl /opt/otrs/bin/otrs.CheckModules.pl
I will try to upgrade...
- 22 Nov 2017, 12:32
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hi all, interesting, I created a group with only 3 agents, and the time went down from 40 to 15 seconds, then I invalidated\disabled the "Ticket create notification" and the create new ticket is immediate. So this problem is somehow related to sending e-mails to the agents. I only notice t...
- 22 Nov 2017, 11:33
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hummm, we are using office 365 smtp interface, let me try to change the server address for its IP and check any difference.wurzel wrote:Hi,
delays are very often DNS issues. Your error message does not indicate this, but you might check DNS anyway.
Flo
- 22 Nov 2017, 11:31
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
You could set $Self->{Debug} to 1 (https://github.com/OTRS/otrs/blob/rel-5_0/Kernel/System/Ticket.pm#L87) and rerun the ticket creation. Then you'll see debug output in the logfile (set minimumloglevel in SysConfig to "debug"). You can go to SysConfig and search for "Ticket::Permissi...
- 22 Nov 2017, 11:30
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hi,fcasal wrote:Which otrs version are you using?
And linux version?
OTRS:
Code: Select all
VERSION = 5.0.13
BUILDDATE = Wed Sep 14 19:58:44 CEST 2016
BUILDHOST = otrsbuild.otrs.com
Code: Select all
CentOS Linux release 7.4.1708 (Core)
Luís Pinho
- 21 Nov 2017, 20:39
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
Re: More than 40 seconds to reply to client after creating ticket
Hi, ERROR: OTRS-CGI-10 Perl: 5.16.3 OS: linux Time: Mon Nov 20 09:15:50 2017 Message: Need module! RemoteAddress: 192.168.201.254 RequestURI: /otrs/index.pl?Action=AgentTicketZoom;TicketID=2046 Traceback (7159): Module: Kernel::System::Main::Require Line: 77 Module: Kernel::System::Ticket::TicketPer...
- 21 Nov 2017, 19:15
- Forum: Help
- Topic: More than 40 seconds to reply to client after creating ticket
- Replies: 17
- Views: 6599
More than 40 seconds to reply to client after creating ticket
Hi, for some reason, OTRS is taking 40 seconds to close the create ticket GUI after the submit button is pressed. Looking at the admin interface, I'm able to see that every time someone opens a new ticket I get several errors per seconds (OTRS-CGI-10 Missing Module! - Screenshot attached) 2017-11-21...
- 14 Sep 2016, 01:39
- Forum: Developers
- Topic: Change Priority from Invalid to Valid without using the web interface
- Replies: 5
- Views: 3705
Re: Change Priority from Invalid to Valid without using the web interface
Really? Not even a chapter (I guess the ACL chapter, off course, how stupid of me)? With that great and wonderful help, full of useful information, I will just emulate the GUI requests using web requests get the cookies from the login, then request the session information based on the cookie and the...
- 13 Sep 2016, 18:26
- Forum: Developers
- Topic: Change Priority from Invalid to Valid without using the web interface
- Replies: 5
- Views: 3705
Re: Change Priority from Invalid to Valid without using the web interface
Use ACL to hide the P1 Priority in the webinterface, so it will still work in the Generic Interface Hi, I already tried to use ACLs to control this, but I wasn't able to find out how I could do this, I tried to restrict the P1 Agents only, and I didn't manage to find a way, I wasn't aware that I co...
- 13 Sep 2016, 15:11
- Forum: Developers
- Topic: Change Priority from Invalid to Valid without using the web interface
- Replies: 5
- Views: 3705
Change Priority from Invalid to Valid without using the web interface
Hi, the P1 priority is hidden from most users because only tickets opened by calls are allowed to open a P1. I would like to open tickets with P1 - Critical priority remotely. I'm able to open tickets remotely using the generic interface, but it will still verify if P1 priority is available, or not....
- 14 Jul 2016, 17:22
- Forum: General
- Topic: Create a note-internal using Generic Interface
- Replies: 3
- Views: 29235
Re: Create a note-internal using Generic Interface
Hi, I'm sending the information to create a note, no note is created and I'm getting this reply in the client: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an ...
- 14 Jul 2016, 16:00
- Forum: General
- Topic: Create a note-internal using Generic Interface
- Replies: 3
- Views: 29235
Re: Create a note-internal using Generic Interface
Hi jojo, thanks for the reply, ok, after your reply, I looked into the Article structure ( https://otrs.github.io/doc/api/otrs/3.3/Perl/Kernel/System/Ticket/Article.pm.html ) and notice that the Article Type determines if the Article is a note-internal. In the ticketupdate that is not so obvious to ...
- 14 Jul 2016, 15:01
- Forum: General
- Topic: Create a note-internal using Generic Interface
- Replies: 3
- Views: 29235
Create a note-internal using Generic Interface
Hi, all, I'm using a rest client to consume services from OTRS, I configured/install the GenericTicketConnectorRest.yml from https://github.com/OTRS/otrs/tree/master/development/webservices . And then I used a rest client for .NET to create a ticket for a customer (example: got a call from a client ...
- 06 Jul 2016, 11:40
- Forum: Help
- Topic: Limit the priority of customer users
- Replies: 3
- Views: 1671
Re: Limit the priority of customer users
Ok, thanks for reply 
- 01 Jul 2016, 17:08
- Forum: Help
- Topic: Limit the priority of customer users
- Replies: 3
- Views: 1671
Limit the priority of customer users
Hi all, is it possible to limit the list of priorities just to a customer user? Scenario: I'm using OTRS in a small project, but I don't want to allow the customers to create P1 tickets, so I set the P1 priority as invalid (it worked). But now, I want to be able to create P1s tickets but still maint...