Page 1 of 1
Callee type in logs and call result callback are different
Posted: Tue May 29, 2018 7:42 pm
by cbjugstad
When executing an outbound call I'm observing two different values related to
callee type.
The result_url Callback indicates that the callee_type is "voice" the POST I receive on my result_url...
Code: Select all
{phone_number=tel:+1XXXYYYZZZZ;ani=+1XXXYYYAAAA, call_id=55004729, message_reference=073d92b1-9f67-4b46-a8a1-403039e9b075, result=completed, callee_type=voice, attempts=1, last_attempt_timestamp=Tue, 29 May 2018 19:32:51 -0400, duration=52}
The log for the same call suggests that the
callee type was "answeringmachine" ...
Tue 29 May 2018 07:33:20 PM EDT:
Callee Type Detected: answeringmachine
Additionally when I try to follow the example here...
http://www.plumvoice.com/docs/dev/plumd ... ming_notes
...and access the global variable
session.connection.callee_type it doesn't seem to have a value assigned.
Can anyone provide any insight on
callee type behavior I'm seeing?
Re: Callee type in logs and call result callback are differe
Posted: Thu May 31, 2018 7:53 am
by support
Hi,
We are investigating this issue, and we will let you know as soon as we have more details.
Regards,
Plum Support
Re: Callee type in logs and call result callback are differe
Posted: Thu Jul 12, 2018 8:42 am
by cbjugstad
Are there any updates on your investigation. It's been over a month?
Re: Callee type in logs and call result callback are differe
Posted: Thu Jul 12, 2018 9:26 am
by support
Hi,
Our apologies for the delay in response. Our engineers have investigated the empty values you were seeing for session.connection.callee_type and a fix has been pushed out that should resolve this issue. Regarding the callee_type post parameter that is being sent to the result_url this is provided for backwards compatibility purposes for legacy customers. Both the start_url and result_url will receive a generic callee_type value of "voice". These values are not mentioned in our documentation and should be ignored. At this point the only correct callee type value provided by our platform is the variable session.connection.callee_type. Please let us know if you are still seeing empty values for that variable.
Regards,
Plum Support
Re: Callee type in logs and call result callback are differe
Posted: Fri Jul 27, 2018 10:49 am
by cbjugstad
We're still seeing that the session.connection.callee_type is not populated...The same behavior as my first post.
Re: Callee type in logs and call result callback are differe
Posted: Tue Jul 31, 2018 2:33 pm
by support
Hello,
Can you provide some sample code that demonstrates the issues you are experiencing. Below is the code we used to test the
callee type variable access and it is working as expected. The code first attempts to collect any answering machine play back and prompts the user to press 1. If the caller presses a button it immediately jumps to the "voice" section. If there is no DTMF press the system will reference session.connection.callee_type and jump to fax, answeringmachine or human based on the asynchronous callee_type and it also explicitly logs that
callee type that was detected. If this does not help resolve the issue please provide us with sample code and we will investigate further.
Regards,
Plum Support
Code: Select all
<?xml version="1.0"?>
<vxml version="2.1">
<property name="inputmodes" value="dtmf"/>
<form id="callee_type_detection">
<record name="vm" finalsilence="1s" maxtime="30s">
<property name="interdigittimeout" value="10ms"/>
<prompt bargein="false"><break time="1s"/></prompt>
<prompt>Hello! This is a call from Company X Y Z. Please press any key to accept this call.</prompt>
<filled>
<if cond="vm$.termchar != null">
<goto next="#voice"/>
</if>
<throw event="noinput"/>
</filled>
<noinput>
<log expr="session.connection.callee_type"/>
<if cond="session.connection.callee_type == 'answeringmachine'">
<goto next="#answeringmachine"/>
<elseif cond="session.connection.callee_type == 'fax'"/>
<goto next="#fax"/>
</if>
<goto next="#voice"/>
</noinput>
</record>
</form>
<form id="answeringmachine">
<block><break time="2s"/>Sorry we missed you, please call us back at: 555-555-1234</block>
</form>
<form id="fax">
<block><disconnect/></block>
</form>
<form id="voice">
<block>Hello human, welcome to the IVR call flow.</block>
</form>
</vxml>