Twilio unable to forward/transfer call

1
votes

I have an app that dials a phone number, gives a set of instructions, and then forwards the call to a specified phone number. Currently when I press the digit to transfer the call it just pauses and hangs up. Not sure what im doing wrong.

  1. This is the initial instructions. If the number 1 is pressed it is supposed to transfer to transfer.xml, which is under # 2.

    <?xml version="1.0" encoding="UTF-8"?> <Response> <Gather timeout="10" action="http://1.1.1.1/twimlet/transfer.xml" numDigits='1' finishOnKey='1'> <Say>"Dummy Text Dummy Text"</Say> <Say>"Please press 1 to transfer this call. Or nothing to hang up."</Say> </Gather> </Response>

  2. If the caller presses #1 then it is supposed to send them to this xml file, and transfer the current call to the number under dial. But currently it just hangs for 2 seconds and drops the call.

    <?xml version="1.0" encoding="UTF-8"?> <Response> <Say>"Transferring you to a court clerk"</Say> <Dial timeout="60" callerID='+14393523419'> <Number>8125277222</Number> </Dial> </Response>

Am I doing something wrong with my xml? Not sure why it is dropping.

2
ruby-on-railsxmltwiliotwilio-twiml
Have you checked Monitor within your Twilio dashboard? Something like this is normally because something returned an error and checking the alerts in Monitor might show what happened. – philnash
Yes no errors... Iptables are off as well. I thought maybe my syntax was wrong? – Colton Seal
Could you send your Account SID to [email protected] and I'll have a look in the back end to see if I can find what's going on. – philnash

2 Answers

1
votes

Twilio developer evangelist here.

Your action in your <Gather> is pointing towards the URL http://1.1.1.1/twimlet/transfer.xml. That looks like a local network address rather than a publicly available URL. If that IP address is not available to Twilio, then the call will not be able to continue.

Try using relative URLs instead of absolute ones. Twilio will happily follow the path /twimlet/transfer.xml.

Let me know if that helps!

0
votes

Hm could it be because finishOnKey is set to 1 in your <Gather> verb? So, it's taking it as you end the call? Have you tried setting it to finishOnKey=""?