Blocking Calls from 'Unknown'

<< < (8/9) > >>

Uncle_Wiggley:
Quote from: azrobert on September 02, 2014, 08:26:43 pm

I'm having trouble using Internet Explorer with Tropo. In the past my Tropo scripts weren't getting updated with IE. I have an older computer running Vista with Chrome installed. Chrome worked perfectly with Tropo.

For this script I had a Tropo App I don't use, so I thought I would modify it instead of creating a new App. I used IE and it seemed to update, but when I looked at it again it wasn't updated. If someone told me this I would think he was wacko. I never had a problem like this with IE.

Are you using Internet Explorer?

Anyway, I created another App from scratch using the following script:

Code:

<?php
say("http://www.thisisarecording.com/z/z/206-201-0000X.mp3");
say("http://www.thisisarecording.com/z/z/206-201-0000X.mp3");
hangup();
?>

First, the previous script worked for me. It took a few seconds before the message was played after it answered the call. I removed the optional Answer command. It didn't make a difference. I removed the blank lines and changed the last command back to Hangup.

I created a Speed Dial to test it like this:
sp2(9991425987@sip.tropo.com)

If you want to test, the above is the actual number for my App.  I feel uncomfortable leaving this App public, so I will be deleting it in a few days.

Edit:
First, I am far from a Tropo expert. The script doesn't force the call to end. When I test it with a Speed Dial the call stays in session until I hang up. That is why I changed the last command to Reject, but I got the same result.

Edit2:
I just noticed a error with the previous script. I inserted a blank as the 1st character of the script when I did the cut and paste. I don't know if this would cause a problem.

Edit3:
The App stopped answering. I think Tropo is having problems.

Edit4:
The App is working again without any changes.
Using IE going thru MY FILES (Instead of MY APPS) to update the script worked.







I did all my editing with Chrome.

I am trying to use your Tropo App, but get the same results as mine: short ring and then nothing except some very faint pulsating static.

I'm changing the the X_InboundCallRoute for my SP2 voice service to include the following rule:

{(MHangup):sp2(9991425987@sip.tropo.com)}, ...

Not sure if the problem has something to do with transferring a call on sp2 to sp2 again.

The call does make it to Tropo, but I can't hear the result for some reason.

azrobert:
I did all my testing with a Speed Dial.
I just now changed the X_InboundCallRoute for a GV account to the following and it worked.
{sp2(9991425987@sip.tropo.com)}

Can you run your App from a browser?
Log into Tropo.
Click on your App.
There are 2 places you can call the App.
On the top right or bottom of the page.
You will get a pop-up keypad.
Click on the phone symbol on the bottom left.
You might get a 2nd pop-up.
Click on the circle next to Allow.

Uncle_Wiggley:
Quote from: azrobert on September 03, 2014, 06:55:45 pm

I did all my testing with a Speed Dial.
I just now changed the X_InboundCallRoute for a GV account to the following and it worked.
{sp2(9991425987@sip.tropo.com)}

Can you run your App from a browser?
Log into Tropo.
Click on your App.
There are 2 places you can call the App.
On the top right or bottom of the page.
You will get a pop-up keypad.
Click on the phone symbol on the bottom left.
You might get a 2nd pop-up.
Click on the circle next to Allow.



There isn't a phone number associated with my app, but I don't think it is my app because I get the same results with your app. It must be something else, probably on the Obi side of things.

azrobert:
You don't have to dial a number.
Click on "Call my App from browser".
Then click on the Phone symbol.
You don't dial a number.

Uncle_Wiggley:
Quote from: azrobert on September 03, 2014, 07:22:26 pm

You don't have to dial a number.
Click on "Call my App from browser".
Then click on the Phone symbol.
You don't dial a number.


OK, I get the same results as with forwarding the Obi calls.

The call answers, then silence, then hangs up.

Navigation

[0] Message Index

[#] Next page

[*] Previous page