I have a Nexmo DID that points to Restcomm cloud. If I call this number it get to my Restcomm app fine.
BUT if I setup a call forward on my phone and call my phone number, the call is forwarded to the Nexmo DID and then I get a 'That number doesn't exist' message.
I think the issue is that there must be a confusion between my Phone number and the Nexmo number and Restcomm look at my number which it doesn't know instead of the Nexmo number...
Any idea how to get this to work?
Thanks
Did you try adding your phone number as Phone Number in Restcomm tied to your application ?
Related
Recently I've tried creating a Kaizala account. I used an Irish mobile number. The mobile number began with +35386XXXXXXX. Another mobile I tried was the same but +35383X... Requesting a call to verify the number also does not work. Neither method sends any form of communication to the phone.
I tested a French mobile number to see if it would work and it did & I was able to setup an account.
I tested again after a week from first noticing this issue, and it remained for the Irish mobiles.
Anyone else experiencing this in other countries or know why it's happening?
I have been trying to create an account on digits with a Google Voice number. Whenever I enter my Google Voice phone number, the digits login screen simply shows an infinite loading icon. When checking the console, I see that a 403 message was generated for "digits (dot) com / sdk / login" and the following error message was returned:
"We cannot send a text message to this phone number because its operator is not supported".
The voice account was created about 12 hours ago.
I am not sure if Google Voice is supported, but now that Digits has been acquired by Google, I think its only logical that it should be supported.
It is important that I get this account to work, because I need it in order have a "developer account" for testers to use in the App Store review process.
I would like to know if there is anything that I can do about this, or if there is any type of help I can get from the team.
"We cannot send a text message to this phone number because its operator is not supported".
Seems pretty cut and dry there. A lot of services don't allow the use of a Google Voice number because it is a VOIP number. It is relatively easy to get a GV number, so some services block/don't whitelist their (and other VOIP's) numbers to prevent bots or mass accounts from abusing their services.
Whatever their reason is, it still doesn't work. As for actually getting it to work, I would contact the team and see if they can do anything, but it doesn't look like there is something you can do.
I would like to listen on the user's phone dialing. If I recognize that the dialed number is something that my app defined as a non-real-call (like starting with #####) I would like to cancel the call and start my own application. This is doable in Android. Can it be done on iPhone?
Thanks,
Simon
I can see why you would want to to this. Eg dialing a special number to direct the call through an internet service instead of the main network.
It is not however possible on standard (ie non-jail-broken) iOS. You can get something similar with URL schemes.
I'm wanting to move away from using $phonenumber#$provider domain because it is too limited in usability.
Is there a SMS service with a good API (prefer HTTP/s, XML, JSON) that allows you to send from a specific phone number?
The reason I want it to come from a specific phone number is because I have a Google Voice number I use for my business...
Since you want to use your google voice phone number maybe you just want to send the SMS though google voice. One way to connect w/ google voice is to use the Asterisk software. You would use Asterisk to talk to google voice over the SIP protocal - documented here:
http://michigantelephone.wordpress.com/2010/05/21/how-to-use-google-voice-for-free-outgoing-calls-on-an-asteriskfreepbx-system-the-easy-way/
and
http://eggie5.com/10-installing-asterisk-on-osx
For example I did this and then I interface asterisk from ruby code and can make calls, sms, etc.
Twilio will let you set the FROM number to any Twilio number that you own. Of course, you'd have to give up your Google Voice phone number. I'm pretty sure you won't find any SMS service that allows you to set the FROM number to an arbitrary number (just think of the mess it would cause).
See comment below indicating that the Google Voice number could be ported to Twilio.
How to get the phone number of the device in Symbian?
According to the GSM specs, only the IMSI is required to be available on the SIM card.
The actual phone number MSISDN is stored on the HLR database in the operator's network and does not need to be available on the SIM card or transmitted to the phone.
So no matter what technology you are using (Symbina, Java ...) you can never count on being able to consistently get your own phone number from the device or SIM. You might be lucky if the operator stores it on the SIM or if the phone provides the user with a possibility to enter it manually, but it does not have to be this way.
As Pat has said, although there are APIs for accessing the "own number" slot on the SIM, rarely in my experience is this slot filled.
The usual strategy for obtaining the phone number for a connected application is to send an SMS as part of a verification process. Either:
Programatically send an SMS from the handset to your server (lots of good SMS gateway interconnect providers out there). The SMS will arrive at your server 'from' the number of the handset (or the SIM to be more correct). Of course the SMS should contain some token so the server can link it with a given session/user.
This has the advantage that you don't need the user to enter their own phone number (which is fraut with subtle difficulties given few folks understand how to format numbers in E.164 format). One disadvantage is that the process can cost your user money (one SMS).
Have the user enter their phone number (web site or on the handset) and connect to your server, passing that phone number. Have the handset then wait for an SMS to arrive that you send from your server. If this SMS does indeed arrive, you have verified the phone number they entered as correct and valid. Obvious disadvantage is that this relies on the user to enter their number correctly - again, given the plethora of ways of writing phone numbers around the world, its not as trivial as it sounds to normalise numbers to E.164....
Alas, neither of these methods are bullet-proof, particularly because SMS is an unconnected transport. Depending on GSM network load, the load of your gateway provider, phase of the moon and direction of window blowing an SMS can take a second to a month to arrive (yes, I do have experience of the latter). The mean delivery time is often in the seconds, but you do have to play with the operation timeout and might have to tweak it on a geographical and GSM network basis.
[And no, don't rely on delivery reports - even more unreliable than SMS delivery]
FYI: Actually i have found this.
http://www3.symbian.com/faq.nsf/AllByDate/100335073FFD8FEF80256E3200571A49?OpenDocument
But the fact is, the phone number is not always stored in SIM. The operator chooses to do it or not!
You can't. Afaik.
Check this discussion:
http://discussion.forum.nokia.com/forum/showthread.php?t=65117
It is not generally possible to get the MSISDN from a Symbian device (or BREW, or any other platform). We've tried.