• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

3CX CFD Http Requests Crash

Status
Not open for further replies.

it145

Trainee Partner
Basic Certified
Joined
Feb 4, 2014
Messages
24
Reaction score
3
Using the latest 3CX Call Flow Designer v15.0.5433.0
Using 3CX (Linux) 15.5.10244.4

I thought the problem was caused by some C# external script at first, so I created a new very simple project that simply uses the "HTTP Requests" component. I have tried both GET and POST examples and call a very simple PHP script that literally just echoes the value 1 back. I upload the VAD app to a dedicated Queue, the queue service restarts and all is good. However no matter what I've tried (as I said this is now a really simple http call) the program errors as soon as the HTTP component is called. A relevant exert from the log file is as follows:

Code:
18/05/18 12:58:01.515|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - Callflow - MainFlow - CallID BALHTSLWSLXB] Trace: Start executing component 'validateNumberGet'
18/05/18 12:58:01.524|100008| Inf|30|0003|: Call(YDGWTIDFHCZL) has been terminated (reason: Unknown)
18/05/18 12:58:01.528|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - WebInteractionComponent - CallID BALHTSLWSLXB] Trace: Start executing component with uri='http://my.webserver/3cx/dummy/?tel=1234567' - httpMethod='GET' - contentType='' - content''
18/05/18 12:58:01.532|100049| Trc|75|0003|: PlugIn[my-vad-app-v1 - CallHandler - CallID YDGWTIDFHCZL] Trace: OnInboundCallTerminated: obj='200'
18/05/18 12:58:01.580|100046| Trc|75|0003|: DBG: CMNotify(BALHTSLWSLXB): NewQCall, legId 2402
18/05/18 12:58:01.592|100046| Trc|75|0003|: DBG: CMNotify(BALHTSLWSLXB): LegStateChanged, legId 2402
18/05/18 12:58:01.995|100050|Stat|75|0003|: Statistics:
Current state report:
== Queues:
  * Queue 810 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 811 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 803 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 804 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 812 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 813 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 899 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
== Agents:
  - Ag.101 Dial:101 Logged-IN Reg: Yes; Qs: [+810 +811 +803 +804 +812 +813]
  - Ag.110 Dial:110 Logged-IN Reg: Yes; Qs: [+810 +811 +812 +813]

18/05/18 12:58:11.419|100050|Stat|75|0012|: Statistics:
Poll processor state:
=Normal requests:
=Total: 0 requests / 0 active

18/05/18 12:58:21.426|100050|Stat|75|0012|: Statistics:
Poll processor state:
=Normal requests:
=Total: 0 requests / 0 active

18/05/18 12:58:31.433|100050|Stat|75|0012|: Statistics:
Poll processor state:
=Normal requests:
=Total: 0 requests / 0 active

18/05/18 12:58:32.030|100050|Stat|75|0003|: Statistics:
Current state report:
== Queues:
  * Queue 810 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 811 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 803 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 804 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 812 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 813 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
  * Queue 899 cin: act=0/stat=0 poll=0 serv=0
    # Calls in polling pool:
    # Calls in servicing pool:
== Agents:
  - Ag.101 Dial:101 Logged-IN Reg: Yes; Qs: [+810 +811 +803 +804 +812 +813]
  - Ag.110 Dial:110 Logged-IN Reg: Yes; Qs: [+810 +811 +812 +813]
18/05/18 12:58:32.649|100030| Err|10|0018|: PlugIn[my-vad-app-v1 - Callflow - MainFlow - CallID BALHTSLWSLXB] ERROR: Error executing last component: System.AggregateException: One or more errors occurred. (A task was canceled.) ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at my-vad-app-v1.WebInteractionComponent.executeStart(QMExtendAPI iface, String id)
   at my-vad-app-v1.WebInteractionComponent.Start(QMExtendAPI iface, CallQueue callQueue, QueueCall queueCall, ActiveConnection activeConnection, TimerManager timerManager, Dictionary`2 variableMap, TempWavFileManager tempWavFileManager, PromptQueue promptQueue)
   at my-vad-app-v1.Callflow.ProcessStart()
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<---
18/05/18 12:58:32.650|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - Callflow - ErrorFlow - CallID BALHTSLWSLXB] Trace: Start executing component 'logError'
18/05/18 12:58:32.651|100023| Inf|30|0018|: PlugIn[my-vad-app-v1 - LoggerComponent - CallID BALHTSLWSLXB] INFO: Ring back ERROR
18/05/18 12:58:32.651|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - Callflow - ErrorFlow - CallID BALHTSLWSLXB] Trace: Start executing component 'errorHandlerAutoAddedFinalDisconnectCall'
18/05/18 12:58:32.655|100008| Inf|30|0003|: Call(BALHTSLWSLXB) has been terminated (reason: Unknown)
18/05/18 12:58:32.665|100049| Trc|75|0003|: PlugIn[my-vad-app-v1 - CallHandler - CallID BALHTSLWSLXB] Trace: OnInboundCallTerminated: obj='487'
18/05/18 12:58:32.692|100046| Trc|75|0010|: DBG: DB command QMgrPlugIn.QCallTrack+Record is executing
18/05/18 12:58:32.695|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - Callflow - ErrorFlow - CallID BALHTSLWSLXB] Trace: OnCallTerminated for component 'errorHandlerAutoAddedFinalDisconnectCall'
18/05/18 12:58:32.696|100049| Trc|75|0018|: PlugIn[my-vad-app-v1 - Callflow - DisconnectFlow - CallID BALHTSLWSLXB] Trace: Start executing component 'logDisconnect'
18/05/18 12:58:32.696|100023| Inf|30|0018|: PlugIn[my-vad-app-v1 - LoggerComponent - CallID BALHTSLWSLXB] INFO: Ring back DISCONNECT
18/05/18 12:58:32.739|100033| Trc|75|0013|: Call update(Del): cid=417, dn=899, internal=<empty>, external=101, ac_stat=Connected, leg=2402; att='BALHTSLWSLXB,'
18/05/18 12:58:32.748|100033| Trc|75|0013|: Call update(Del): cid=417, dn=Ext.101 M Office, internal=<empty>, external=899, ac_stat=Connected, leg=2401; att=',f346ed7c8e1b4ba7a8232c07b01c156a'
18/05/18 12:58:32.780|100046| Trc|75|0003|: DBG: CMNotify(BALHTSLWSLXB): LegRemoved, legId 2402
18/05/18 12:58:32.782|100046| Trc|75|0003|: DBG: BALHTSLWSLXB: [2401]
18/05/18 12:58:32.784|100046| Trc|75|0003|: DBG: CMNotify(BALHTSLWSLXB): LegRemoved, legId 2401
18/05/18 12:58:32.784|100046| Trc|75|0003|: DBG: BALHTSLWSLXB: []
18/05/18 12:58:32.784|100046| Trc|75|0003|: DBG: CMNotify(BALHTSLWSLXB): CallTerminated, legId 2401
18/05/18 12:58:32.784|100022| Inf|30|0003|: QCall(BALHTSLWSLXB) has finished
18/05/18 12:58:41.439|100050|Stat|75|0012|: Statistics:
Poll processor state:
=Normal requests:
=Total: 0 requests / 0 active

Any thoughts, help would be greatly appreciated?
 
Last edited:
Do you have the complete log to share? The details of the second exception are the ones we need to check to understand the problem. And you cut the log just there...
 
Thanks very much for looking at this and it has me stumped at the moment. No matter what I do it fails to do a simple "HTTP Request". I have tried other components before this, playing wav files etc and this all works fine but it always jumps to the "Error Handler Flow" the moment it reaches the HTTP component.

I've even recently added a call that generates a push notification inside the PHP page but this never gets called and yet works fine if the page is opened directly from the browser.

Finally, if you call the queue from an extension (or from an external call via the IVR) there is a long delay of approximately 18 to 20 seconds before anything happens. Originally when I added a play prompt at the beginning there would still be a long delay always before the prompt would play?

I look forward to anyone's valued assistance.
 
Looks like you have other problem there. Maybe the connection can't be established, and you're experiencing the HTTP request delay. You should not experience any delay at the beginning of the callflow, pretty sure this is related to the exception you see.
 
Thanks very much for this, you pointed me in the right direction and it seems the NAT Loopback for the web service all behind the firewall was not working. Using a local IP (which is fine) and now everything works.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,605
Messages
748,774
Members
144,717
Latest member
sprice352
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.