Issue 193 in restcomm: High Priority RCML Defects with RestComm in New AWS Marketplace Instance

[rest...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Version-1.0.0.FINAL

New issue 193 by lylepr...@gmail.com: High Priority RCML Defects with
RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

- No DialCallSid request parameters sent to StatusUrl if call is never
answered via a <Dial> verb
----- To reproduce use the <Dial> verb and watch request parameters sent to
StatusUrl. No DialCall parameters are present.

- <Gather> Verb is looping by default and never continues on to next Verb
if no digits are pressed.
----- Use the <Gather> verb and do not press any digits. It continually
loops.

- startConferenceOnEnter="true" should not actually start the conference if
you are the first person in the conference room
----- Use the <Conference> Noun in a <Dial> verb
with "startConferenceOnEnter" set to true and enter the conference. It will
immediately beep and begin. This is different than Twilio's behavior. Also,
why would you want to begin a conference with only one person in there?

-no "sendDigits" or "url" attributes available for <Uri> Nouns.
----- This is very critical! the URL attribute especially!


I'll be testing the Live Call Modification functionality through the Rest
API tomorrow.

-Lyle

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[rest...@googlecode.com]

Comment #1 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Hi Guys! Any update on this?

[rest...@googlecode.com]

Updates:
Status: Accepted
Owner: jean.deruelle
Cc: ivelin.a...@gmail.com gvage...@gmail.com
Labels: TelScale-Restcomm-7.1.2.GA Component-Logic Roadmap-Fix

Comment #2 on issue 193 by jean.deruelle: High Priority RCML Defects with

RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

hi lyle,

on Gather issue : I used this RCML :
<?xml version="1.0" encoding="UTF-8"?>
<Response>
<Gather action="/restcomm/gather.jsp" method="GET" timeout="10"
finishOnKey="*">
<Play>http://127.0.0.1:8080/restcomm/audio/demo-prompt.wav</Play>
</Gather>
<Say>Gather ended with no DTMF</Say>
</Response>

and when no digits are pressed it calls the action URL but it's no looping
for me. Can you confirm this is the behavior you noticed ?

[rest...@googlecode.com]

Comment #3 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Ahh. That is the issue then. The action URL should not be called if no
digits (no action) occurs.

I just ran the same template through Twilio and confirmed that the action
URL is not accessed if no digits are pressed. If no keys are pressed
RestComm is sending through blank Digits, when it shouldn't send through
the Digits parameter at all...it should just continue the XML without
making any additional request.

-Lyle

[rest...@googlecode.com]

Comment #4 on issue 193 by jean.deruelle: High Priority RCML Defects with

RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

OK Thanks. I confirmed I just fixed the issue. It should be available at
the end of the month with the next version of the AMI or through an update
mechanism

[rest...@googlecode.com]

Comment #5 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Wow. Cool! All four of these things are already fixed? You guys are fast!

[rest...@googlecode.com]

Comment #6 on issue 193 by jean.deruelle: High Priority RCML Defects with

RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

LOL, no I wish though :D only the Gather issue so far. In the future please
open a ticket per issue, it makes it easier to track down.

[rest...@googlecode.com]

Comment #7 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Would you like for me to move the others to separate issues now?

On Friday, October 11, 2013, wrote:

[rest...@googlecode.com]

Comment #8 on issue 193 by jean.deruelle: High Priority RCML Defects with

RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

yes if you can, that would make it easier to track down. Thanks Lyle

[rest...@googlecode.com]

Comment #9 on issue 193 by gvage...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Hi Lyle,

Regarding issue:

-no "sendDigits" or "url" attributes available for <Uri> Nouns.
----- This is very critical! the URL attribute especially!

What you are looking is the url attribute for call screening as described
here: https://www.twilio.com/docs/api/twiml/sip#attributes ?

Please confirm.

Thanks
George

[rest...@googlecode.com]

Comment #10 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

Thats correct George. We use this to prevent people's voicemail systems
from answering phone calls as well as to announce calls to them. For
example, ours by default says: "Press any key to accept the call from Lyle
Pratt about Support Request".

[rest...@googlecode.com]

Comment #11 on issue 193 by lylepr...@gmail.com: High Priority RCML Defects

with RestComm in New AWS Marketplace Instance
http://code.google.com/p/restcomm/issues/detail?id=193

It would also be nice if it could be configured so that the OTHER legs of
the phone call were not canceled until two callers were actually bridged
(by pressing a key). Twilio does not allow that, and its a longstanding
source of pain for many developers.

-Lyle