We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics
Search found 5 matches
- Wed Jun 12, 2019 3:46 pm
- Forum: Plum DEV Q&A
- Topic: recordcall - dtmf tones not audible in call recording
- Replies: 2
- Views: 7444
recordcall - dtmf tones not audible in call recording
I'm implementing the recordcall funcionality as outlined in the documentation... https://www.plumvoice.com/docs/dev/voicexml:properties:recordcall I'm able to successfully record the call and post the resultant audio file to my server. When listening to the recorded call I can hear the voice prompts...
- Fri Jul 27, 2018 10:49 am
- Forum: Plum DEV Q&A
- Topic: Callee type in logs and call result callback are different
- Replies: 5
- Views: 8606
Re: Callee type in logs and call result callback are differe
We're still seeing that the session.connection.callee_type is not populated...The same behavior as my first post.
- Thu Jul 12, 2018 8:42 am
- Forum: Plum DEV Q&A
- Topic: Callee type in logs and call result callback are different
- Replies: 5
- Views: 8606
Re: Callee type in logs and call result callback are differe
Are there any updates on your investigation. It's been over a month?
- Mon Jun 04, 2018 12:01 pm
- Forum: Plum DEV Q&A
- Topic: Audio files not cached
- Replies: 1
- Views: 3683
Audio files not cached
I've read the following caching references in the documentation. http://www.plumvoice.com/docs/dev/developer_reference:caching https://www.plumvoice.com/docs/dev/voicexml:tags:audio My goal is to have Plum cache my audio files (.wav) for a period of time. Below is snippet of the vxml with how I'm pr...
- Tue May 29, 2018 7:42 pm
- Forum: Plum DEV Q&A
- Topic: Callee type in logs and call result callback are different
- Replies: 5
- Views: 8606
Callee type in logs and call result callback are different
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... {phone_number=tel:+1XXXYYYZZZZ;ani=+1XXXYYYAAAA, call_id=55004729, message_reference=073d92b1-9f67-4b46-...