We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics

Callout takes almost 5 minutes to execute

Questions and answers about IVR programming for Plum DEV

Moderators: admin, support

Post Reply
SGTAdmin
Posts: 8
Joined: Tue Jul 02, 2013 7:40 pm

Callout takes almost 5 minutes to execute

Post by SGTAdmin »

Hi All,

We are trying to build an application that needs callout feature and are currently using a test login for this. The issue we are facing is, it takes more than 5 minutes for Plum to make an outbound call after we send the request. This is prohibitive for our application. Is this happening because we are using test account?

Below document describes the lifecycle and times:

The lifecycle is:

1. We send HTTP POST to plum with several params:

16:51:53.372 [RMI TCP Connection(2)-10.168.200.86] INFO c.t.m.service.DefaultCalloutService 163 - /makeCall sending request with params: {login=[xxx@xxx.com], pin=[xxxx], phone_number=[tel:+123123123123;ani=123123123123], start_url=[http://xx.xx.xxxx.250:8080/rest/callout/start], result_url=[http://xx.xx.xxx.250:8080/rest/callout/result], message_reference=[-661498084], call_parameters=[2]}


2. Plum checks our /start and /result servlets whether url returns HTTP OK:
16:51:54.325 [http-bio-8080-exec-1] INFO c.t.m.service.DefaultCalloutService 238 - Plumvoice requested /start with params: {}
16:51:54.872 [http-bio-8080-exec-2] INFO c.t.m.service.DefaultCalloutService 270 - Plumvoice requested /result with params: {}

3. Plum requests our VXML scripts from /start url

16:52:30.981 [http-bio-8080-exec-3] INFO c.t.m.service.DefaultCalloutService 238 - Plumvoice requested /start with params: {call_parameters=2, message_reference=-661498084, phone_number=tel:+ 123123123123;ani=123123123123, call_id=34926719, callee_type=voice, campaign_parameters=}

4. Plum should send HTTP request to our /result url with callee_type, message_reference and so on, but it don’t do it even 5 minutes after we receive response for our POST from item #1.

16:56:55.196 [RMI TCP Connection(2)-10.168.200.86] ERROR c.t.m.service.DefaultCalloutService 198 - Error handling request to /makeCall for phone_number=+123123123123callee_type was not received for phone_number=+123123123123, message_reference=-661498084 for 300000 ms

If take a look at the plum page it shows call with message_reference=-661498084 as completed with callee type “voice”. http://hosting.plumgroup.com/developer_ ... n_id=29881
And actually, the call performed successfully.

support
Posts: 3632
Joined: Mon Jun 02, 2003 3:47 pm
Location: Boston, MA
Contact:

Re: Callout takes almost 5 minutes to execute

Post by support »

Hi,

The issue you described should be resolved at this time. There was an issue earlier this week that impacted a small subset of users where callback URLs were not being executed in certain cases. Our team was made aware of this and resolved the issue a few hours after your comment was posted. Please let us know if you experience any further issues in your testing.

Regards,
Plum Support

SGTAdmin
Posts: 8
Joined: Tue Jul 02, 2013 7:40 pm

Re: Callout takes almost 5 minutes to execute

Post by SGTAdmin »

Hi,

It seems to be working now.

Thanks,
Kavin

Post Reply