[SOLVED] Touch pro hangs up when I call voicemail - Touch Pro, Fuze General

Hello, I have only had my touch pro a few days and when I try to access my voicemail I get to the part to enter my pin, then it tells me "first new message..." and then it hangs up. Is this a known issue? I tried searching the forum and in fact all of google, but nothing.
Any ideas?

I've had the same issue here in the Netherlands.
Disconnect when I called my own VM, also a disconnect when I tried to leave a message at a friend.
Both are in the TMobile network.
Just tried it again, but it workes ok now

solved
I figured it out for my phone. When I put my sim card in, the phone auto detects settings for sms, mms, data and voicemail. Here in Canada, providers have several different voicemail retrieval numbers and the phone autodetected the wrong one. I thought that since it did work at least somewhat, that the number was not the issue.
Contact your service provider and make sure your phone didn't choose the wrong retrieval number too

Related

T-Mobile UK Users - Important Information re Voicemail Issue

Anyone using, or planning to use, the HTC Touch Cruise on the UK T-Mobile network will very probably need to do a special setup on their device to get voicemail access working properly.
The symptom is that your callers will be able to leave you voicemail messages but you will not be able to pick them up from your phone. When you get a voicemail message you will get the notification but when you press the soft key to access voicemail it will dial the number but you will then get an error message saying "access to this number is barred" and the system will hang up on you.
If you try accessing voicemail by holding down the "1" key or by explicitly dialing the voicemail access number retrieved from the network (probably of the form "+44050<your mobile number minus the leading zero>" or ""+44068<your mobile number minus the leading zero>") you will get the same message. Dialing 222 will work but will also initiate a voicemail setup message each time and however many times you switch your phone on and off to reload the voicemail settings from the network it still won't work.
I just spent 2 days with the very helpful T-Mobile support to sort this out, ultimately getting escalated up two levels in the technical support group, until I got someone who recognised the problem.
The issue is simple to resolve. The problem is that the format of the voicemail access number that the T-Mobile UK network pushes down to the handset is incompatible with the HTC software on the Touch Cruise (and maybe other devices too). The thing the software doesn't like is the "+" at the beginning.
To fix it go to the Settings/Personal/Phone application and click the second tab ("Services"). Now select "Voice Mail and Text Messages" and click "Get Settings...". You should now see a screen with two access numbers populated, one for voicemail and the other for text messages. Both will probably start with "+44". The text message access number is OK so don't mess with that but the voicemail access number won't work with the UK network. Simply replace the "+" with "00" and click OK and then your voicemail should work as you expect.
I haven't tried accessing voicemail outside the UK so it is possible that the above might break your access when roaming and you might need to edit back the "+" when travelling. I'd be interested in knowing if anyone has any experience with non-UK access and a "0044..." setting rather than the default "+44...", does it dial the UK access number OK?
(Actually, I never looked at the mechanics of accessing voicemail outside the UK, does it still dial the UK number or does the host network automatically push an alternate local access number to your phone when you register with the network?)
- Julian
Nice on Julian. I bought an Orbit 2 on O2, but my number doesn't transfer to O2 for few days yet, so have been using my T-Mobile SIM, and also experiencing this problem.
Thanks for sharing the tip!
I'm on UK T-Mob Web&Walk. Switched the +44 entry to 0044...but my TC then coundn't send texts. Switched it back and fortunately can still access voicemail as well as send texts. Strange.
I'm with T-mobile running an old T-mobile sim card on my new TC, when first called voice mail it gave me a long introduction then said "turn of your mobile off and on again to not get this messages again", I turned TC to "air plain mode" back to on mode and everything was cool from there on.
It seems that not everyone have that problem OR T-mobile has sort out that problem after Julian told them about the problem. In any case, thanks Julian to share this with us.
PS (today after reading this post is the first time that I use voice mail with my new TC)
Similar problem on WM 6.5 Asus Crystal
I had exactly this problem with T-Mobile and WM 6.5.
T-Mobile technical support was excellent, ringing back on several occasions to ensure that the problem was fixed, even though my handset is not a supported model. Once I was put through to 2nd layer support they fixed it in seconds.
In a nutshell, if you text and voice service centre numbers begin with a +44......, change them to 0044......
This did not happen on my XDA Exec WM5.0, so appears to be a new thing in WM6.5?

SMS service center address

I cant send sms on touch pro. it says be cetain that your service center address is correct in settings. But I cant find the settings place where to put the service center phone number in.
And as usual the manual doesnt say anything about that not even speaking of mobile operators helpline.
Maybe such a thread is already there but I cant find such.
The settings for SMS service number are in Start>Settings>Phone, Services tab, then you tap "Voice Mail and Text Messages" and "Get Settings..."
Hope it helps!
Yep thanks but that I have found also thought thar was that but when cklicking it phone tries connecting with operator and then cant download anything from there. Everything else seems to work all right exept that when starting comes on some annoying screen with saying that does not recognise the operator.
Problem solved. Maybe will help someone else. It appearde that I had a quite an old SIM card and when changed to a new SIM card then the problem dissapearde and phone could get the voicemail and SMS settings from the operator without any problems.

[Completed] [Q] HTC One M8 can't make or receive calls

I'm rooted, running stock Lollipop Sense 6.0 software number 4.28.502.1
I can send and receive texts with no problem.
Whenever I try to dial a number the call immediately ends without even a dial tone. Whenever I get a call, I have no option to answer the phone, I receive no notification of an incoming call or of a missed call. In fact the only way I even know someone tried to call me at all is because YouMail sends me an email letting me know a voicemail was left.
Some background: I had been using the module/app "Blacklist" with the Xposed Framework for about 3 weeks. It had been working fine, without a hitch, in blocking 3 numbers from calling me. I don't know that this is the app that has caused the problem, but it has root permissions to end all calls prematurely and I had it in the settings to leave no notifications when it blocked a call from a number on my blacklist. So I figured that might be the best place to start.
First, I checked "Do Not Block Calls" w/in Blacklist, rebooted my phone, but nothing changed.
Then I unchecked the box next to its module in Xposed, rebooted, but nothing changed.
Then I uninstalled the module/app all together, rebooted, but nothing changed.
Then I did a system restore from 4 weeks ago but nothing changed.
So finally I did factory data reset...and still, nothing has changed.
SIM: Could it be the SIM card? I haven't physically done anything to it. And would it let me still send and receive texts but not calls? I've downloaded a basic SIM info app from the Play Store and everything seems to look normal. Regardless, I bought a cheap unlocked Blu phone from Amazon which should arrive May 30, 2015, so I'll pop my SIM into that and see if it lets me make calls.
If you have any ideas or can help me at all, I'd greatly appreciate it.
Hi, thank you for using XDA Assist. The best place to get information on your device is in it's specific forum here, http://forum.xda-developers.com/htc-one-m8 For your specific question try asking here, http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783

Problems Handling Phone Calls (Call Waiting, 3 way, etc.) Verizon S5 on AT&T Network

Problems Handling Phone Calls (Call Waiting, 3 way, etc.) Verizon S5 on AT&T Network
recently bought a used Verizon Galaxy S5 (SM-G900V). It came with the lollipop OS. My service provider is H2O wireless (on the AT&T Network. From the outset, I had problems with phone calls, text messaging.
1. When I'm in a call, I'm not able to dial (Like to enter numbers for automated systems).
*I solved this one by going to:
settings>applications>call>
Scroll down to DTMF tones and change setting to long.
2. When I'm in a call, I'm not able to click over to calls on call waiting. When I do try to click over, I still hear the original call for a few seconds and then both calls drop and I get an error message that says "no sim or invalid sim". If I don't answer the call, both calls drop and I get the same message. The same thing happens if a try to make a 3 way call.
3. If someone calls me and I try to call them back, the call redirects to turn it into an international call and the call doesn't go through.
*I solved this using an app called prefixer
4. If I try to text message someone who called me, I get an error message back saying the phone number is invalid.
I figured I would have to root my phone to be able to make some custom changes. I first had to downgrade to kitkat (android 4.4.2) and root it and then upgrade with root using some very helpful posts and resources found on this site (thanks). When I downgraded, problems 1 and 2 went away (for number 1, I had to change my network mode, but that solution didn't work when I went back to lollipop). After upgrading beack to lollipop, all of these problems were there, though I was able to resolve 2 of them, the other 2 are problematic.
I think theres a problem with the way the phone is handling the AT&T network signal since they have a different type of network from verizon but i don't know.
I'm will in try to install a custom ROM, change settings in service mode, etc. I just haven't come accross any info to point me towards the right instructions. Alternatively, I may trade or sell this phone ant get an AT&T based phone. What do you suggest?

some phone callers are always reaching disconnected message to my phone

I am looking for some information regarding a problem I am experiencing with my phone, I have 3 questions regarding it. I have stated them at the end of this lengthy post.
My phone is zte grand x2 model z850 and android build is 5.1, carrier is pcmobile in Canada.
The problem is that my android phone seems to work OK and receives calls correctly, but my doctor office, hospial booking office, and phones belonging to my workplace receive a tone followed by some type of reaching a disconnected number. My phone calling log shows no record of calls being received to phone.
The troubleshooting steps are sent email to pcmobile and received response to do a battery reset, pull out battery and sim card for at least one minute and reinstall. If it doesn't work call their customer support and get put through to tech support.
That did not work. Call to the tech support says that all 0:00 second calls end in response to some type of code (mentioned a specific code but I forget) and that it means my phone is responsible. She said android phones allow for rejecting calls based on various categories like toll free originating and such. And that the phones calls not getting through likely belong to a category I have blocked. She mentions just goto phone menu, settings, and something like call block, call reject and I will most likely find something there. If that doesn't work to do a backup and factory reset. To do that she says I need to call zte for help as she isn't allowed to help with it.
My zte phone interface only shows call barring settings with a few things like all incoming or incoming roaming, outgoing or outgoing roaming and that is it.
However it is possible that I came across via a web search a USSD code to ban telemarketers and used it. I just don't no what code it was or even if I did such a thing.
Anyway I called back their customer service to maybe get further help and had specific phone numbers and times of calls that were rejected by disconnected number messages from my workplace. To see if the problem could be isolated at my phone as a reason or maybe in the network somewhere. And was also wanting to know how I can unset the call reject if I have no interface to do it or undo it. Maybe even get confirmation that the noted calls are actually making it to my phone or getting dropped in the network. The new customer support first asked if it was a ported number and since it was, he checked with someone to see if it was a problem. The porting people said all calls were routed correctly through to my phone, but the customer support guy said there was no way to verify if my specific noted calls were included.
He mentions their tech support did not help with actual phone troubles, but he suggested I get another sim card and phone and use them in varios combinations with my phone and sim to get the working/ not working situations and isolate the problem. This I have not done yet as it seems like a lot of expense and jumping through hoops trying to fix a problem that seems like it should be able to be verified in a phone setting log somehow. He refused to put me through to tech support when I said I wanted him to anyway.
My emails with zte have them requesting I do a backup and factory reset, if that doesn't work then try a new sim card, if that doesn't work then book my phone for a repair with them.
So my question number 1 is:
Is there a USSD code that allows me to see settings or logs of such a call reject being used. I have tried *35**# which is supposed to show "incoming call barring" and it responds "Call barring Service has been disabled." My phone user interface doesn't provide for this as best as I can tell.
My question number 2 is:
What is the USSD code that I might have used to try and reject telemarketers which might issue tones that might indicate a disconnected number. I'm thinking this is the most likely reason for my troubles. I have been unsuccessful google searching for what I may have done. I find info on various USSD codes at this forum and elsewhere. But I'm not finding anything specific to help. I thought the *35**# would have helped but it doesn't. It is very possible I did do something like this with a USSD code which is causing my trouble.
.
Part 2 of this question is what would be the USSD codes to see the status or to unset such a thing.
My question number 3:
If there is no way to set status or see the status of call barring and rejecting logs or settings of the phone. If I do a phone reset, how is it possible that it could be the sim card instead. Does the sim card actually store call rejecting and barring settings as well.
Part of troubleshooting this involves me contacting third parties such as work, doctor, or hospital and asking them to try and call me and if not successful contact me someway else and tell me it was unsuccessful. I really doubt any of them want to do this for me more than once or twice. So I'm trying to gather info and limit my number of attempts. It would be real useful to be able to look up logs or settings somehow.
Would anyone know if the effect of *77 being used is that the caller experiences reaching a disconnected number. Or what do they usually experience.
In web searching possible codes I may have used, I came across the *77 code to reject anonymous callers. The *87 would be to unreject such a setting. Is there a method to check the current setting of either on or off somehow.
I am unable to test the specific phones getting the message of reaching a disconnected number. I will however have better access to one of the phones in three weeks time to see if *87 fixes my troubles.

Categories

Resources