Plum IVR Support

Posted: **Tue Jul 12, 2016 2:29 pm**

I was wondering if anybody could tell me why the following document doesn't actually log anything in the PlumVoice logs?

Code: Select all

<vxml application="root.vxml" version="2.0">
	<form>
		<block>
			<audio src="resources/sorry.mp3">I'm sorry.</audio>
			<audio src="resources/technical-difficulties.mp3">It looks like we're experiencing technical difficulties.</audio>
			<goto next="operator.transfer.vxml"/>
			<log>vRxN/6nY/az0MzEhHMT27nuRfDomWInNQh7KNwnl7nv5+L/v2rC4WpZ+5fj04GRMFG4akHpsGOwU8413tIKFLaGqt4VYjpYYBvjdeN6Zh190gzEcCgX4h1JKAOPmpM9tEKlBgs9D52Uj3Xm6+qAkBXrxyTRm34sn/qz/m8RTsm6E0OUg6jwvzRQ6AfQIQOu9G/WTd5vqWvziPdupvRkUtX0h3UO/pnof55U7lE+vQ+4mWGHfVivq0bfst6Op7vQb7stivgLiaOF8PFQjrXp5nROafxOprHqUYIvJQK2Icov+gfY11PaReNobq0zfTiljArxzvAVfE2VaSV6yqztgCa2R+7k1b+lcELkl4be7PEluJm6rk7fWAN6pVwN3uwGusoRsb+Z7M5oGCKawfz+UV6ovpWVjcy3C8HdzJSmXMB7OsJ3GxjpUwvVf1ZIaJ1zDAQxC3IRQA23wfe8KVNFcXk37d+JsjzhUuLNsoDi3RD4JPetMdF0j5z7l7n6rgAdFJ13D3izbv/Yf0cM+MHOpnJjdOzt6JdAvfYgihqyH08ypQkxThuqGuAK2H7z3l9wNtGmykwIBFj2sznvpKbxntssLKojeiVxjKHjMTfZvNXIbRjoDRyFU7hXzPsRmL4Sre1oAOMD5JTpNxiEOWi1InYJ+MMrS2G+Gd8hJzPQHIrCHuKyH6UeBoctpwIKnxVc/wVOc9uRK8Uf6D7Rr697lAfv+YCZ2q5qFE57esYRbBAtZq+LVE9aLJAHbKOHKXMtgXGZLz35GadowbCSGFc8WsyUetuoKWseBce1Vr/afm9o9KzFPhl281D1PK6KgYAcF3al1CKlUhQsJaIDV6LvP2r4jz6qeTQmfYFvo35KtSOczFXTHnw8D7LCix1gtNLzwT/QLn9VXddFP16gWXW9cbXafDQov+vRKhnm4s7AQ1IAbu3OY4VATIRGFHNauWeWtAi4pjRM8cSCNecYxcEBJwy3eH92zXOFtkEmU1tN8wOnoWHjKX2XF0PqMaD8DYyEygdroeXxDkk3KmdITRYQjn0QphrJhpNKXTlYJLKgHT1ssRZqX/07Ht37Ss2ybzpLfGBq20Nc5UjToOjVckxBW1F5Xn331eGofEuPhK+ql3dK31Sha+LXg4I2lyD4SPeY4UiHDlR46BxRWH6GjF9WlzYREk2br2TemyZuKwnz13x5lUXRxC2SBXnElze1KYrnTVBss8XaS6l1AxxZ73a0SJfVfkJnxaq7rTYmrSivJsXeS0FJX+fib66K/+HSfizhiLnwJzbm8HNYAt6nUAdH11gV0pDPfwsYnKZ0u46zjgG6aZTk5ac4mWPLPux+kAGxZklucqnneUJ2E9Rm/ltsXhA==</log>
		</block>
	</form>
</vxml>

FYI, the base64-encoded string you see within the log element is a serialized, encrypted exception object.

Am I correct in assuming that storing an arbitrary length base64-encoded string is allowed by the PlumVoice platform?

Posted: **Tue Jul 12, 2016 3:11 pm**

Hi Clayton,

This should work. We just tested that same code and see it showing up in the call log and and session logs for today. Where are you currently looking for this value?

Regards,
Plum Support

Posted: **Tue Jul 12, 2016 3:25 pm**

Hey thanks for the prompt reply.

I'm looking for this value to pop up in my call logs.

Typically, when I use the log element, it'll show up in the call logs with a green background so its easy to pick out.

I'm not able to find this particular entry (encoded string) anywhere in my call logs when that VXML document is executed.

Posted: **Tue Jul 12, 2016 3:32 pm**

Hey Clayton,

When we ran your code we removed the transfer part and did see that item showing up. However, looking over your code again, it looks like you have a <goto> right before the log. When a goto is encountered, the application logic jumps to that other page and therefore your log tag is never encountered, which is why you aren't seeing it in your call logs. If you flipped the order of these lines:

Code: Select all

<goto next="operator.transfer.vxml"/>
         <log>vRxN/6nY/az0MzEhHMT27nuRfDomWInNQh7KNwnl7nv5+L/v2rC4WpZ+5fj04GRMFG4akHpsGOwU8413tIKFLaGqt4VYjpYYBvjdeN6Zh190gzEcCgX4h1JKAOPmpM9tEKlBgs9D52Uj3Xm6+qAkBXrxyTRm34sn/qz/m8RTsm6E0OUg6jwvzRQ6AfQIQOu9G/WTd5vqWvziPdupvRkUtX0h3UO/pnof55U7lE+vQ+4mWGHfVivq0bfst6Op7vQb7stivgLiaOF8PFQjrXp5nROafxOprHqUYIvJQK2Icov+gfY11PaReNobq0zfTiljArxzvAVfE2VaSV6yqztgCa2R+7k1b+lcELkl4be7PEluJm6rk7fWAN6pVwN3uwGusoRsb+Z7M5oGCKawfz+UV6ovpWVjcy3C8HdzJSmXMB7OsJ3GxjpUwvVf1ZIaJ1zDAQxC3IRQA23wfe8KVNFcXk37d+JsjzhUuLNsoDi3RD4JPetMdF0j5z7l7n6rgAdFJ13D3izbv/Yf0cM+MHOpnJjdOzt6JdAvfYgihqyH08ypQkxThuqGuAK2H7z3l9wNtGmykwIBFj2sznvpKbxntssLKojeiVxjKHjMTfZvNXIbRjoDRyFU7hXzPsRmL4Sre1oAOMD5JTpNxiEOWi1InYJ+MMrS2G+Gd8hJzPQHIrCHuKyH6UeBoctpwIKnxVc/wVOc9uRK8Uf6D7Rr697lAfv+YCZ2q5qFE57esYRbBAtZq+LVE9aLJAHbKOHKXMtgXGZLz35GadowbCSGFc8WsyUetuoKWseBce1Vr/afm9o9KzFPhl281D1PK6KgYAcF3al1CKlUhQsJaIDV6LvP2r4jz6qeTQmfYFvo35KtSOczFXTHnw8D7LCix1gtNLzwT/QLn9VXddFP16gWXW9cbXafDQov+vRKhnm4s7AQ1IAbu3OY4VATIRGFHNauWeWtAi4pjRM8cSCNecYxcEBJwy3eH92zXOFtkEmU1tN8wOnoWHjKX2XF0PqMaD8DYyEygdroeXxDkk3KmdITRYQjn0QphrJhpNKXTlYJLKgHT1ssRZqX/07Ht37Ss2ybzpLfGBq20Nc5UjToOjVckxBW1F5Xn331eGofEuPhK+ql3dK31Sha+LXg4I2lyD4SPeY4UiHDlR46BxRWH6GjF9WlzYREk2br2TemyZuKwnz13x5lUXRxC2SBXnElze1KYrnTVBss8XaS6l1AxxZ73a0SJfVfkJnxaq7rTYmrSivJsXeS0FJX+fib66K/+HSfizhiLnwJzbm8HNYAt6nUAdH11gV0pDPfwsYnKZ0u46zjgG6aZTk5ac4mWPLPux+kAGxZklucqnneUJ2E9Rm/ltsXhA==</log>

That way the log tag comes first and will always occur before your application jumps to the transfer page. That should do the trick and you should see that value show up in your call log. Hopefully that helps!

Regards,
Plum Support

Plum IVR Support

Having Trouble with Log Element

Having Trouble with Log Element

Re: Having Trouble with Log Element

Re: Having Trouble with Log Element

Re: Having Trouble with Log Element