CALL FAILED

Teacher

CALL FAILED

Ok, iPhone 4 and iPhone 3GS. Any attempts at outgoing calls: CALL FAILED. Second attempt, hit or miss. 3rd attempt usually works. Incoming is the same. Somebody calls and no ring... Rolls to voicemail. 2nd attempt usually works.
Message 1 of 52 (11,451 Views)
Contributor

Re: CALL FAILED

I just got my Microcell yesterday, I was so excited to get this and now I am having failed call attempts as well. It failed 3 times trying to make a call and then my iphone 4 seemed to lose connection to the microcell. Once it came back I was able to make a call. Whats the point in paying 150 for a device that is suppossed to fix these issues.

Message 31 of 52 (3,201 Views)
Contributor

Re: CALL FAILED

[ Edited ]

Well first of all, I love My Microcell. it has worked for me with no problems until now. but everything in this world will always have a problem. the point is either deal with the problem and solve it or stop complaining dang. eveyone wants everything perfect will guess what Life isnt perfect!!! Sorry im back The microcell will have its bugs here and there. unplug it or do a reset and see if it starts working again. or Deactivate it and reactivate it. if that doesnt work then call. Like i said i Have NO PROBLEMS with mine except my girlsfriends blackberry bold has call fails but not me! so i am currently looking into it for her.

 

 

Edit: i just deactivated the microcell, unpluged it. went through the steps to activate it again and everything is working now!!!

Message 32 of 52 (3,193 Views)

Re: CALL FAILED

Anyone experiencing this issue today, 12/10? I've had the MicrCell for over 6 months. The only issues I've had so far were fixed by rebooting the MicrCell and/or my internet router. But this morning I experienced the call failed issue. Called a clueless AT&T rep who was asking questions such as "what phone number did you call?", "how long have you had your MicrCell (shouldn't you have this info in your db?)".. Anyway, I tried rebooting everything but I still get call failed when using the MicrCell. Text message is fine. I have an iPhone 3gs.

Message 33 of 52 (3,086 Views)
Scholar

Re: CALL FAILED


repinheiro wrote:

Anyone experiencing this issue today, 12/10? I've had the MicrCell for over 6 months. The only issues I've had so far were fixed by rebooting the MicrCell and/or my internet router. But this morning I experienced the call failed issue. Called a clueless AT&T rep who was asking questions such as "what phone number did you call?", "how long have you had your MicrCell (shouldn't you have this info in your db?)".. Anyway, I tried rebooting everything but I still get call failed when using the MicrCell. Text message is fine. I have an iPhone 3gs.


unregister the MC and re-register - that seems to help in this situation....

 

 

Message 34 of 52 (3,065 Views)
Tutor

Re: CALL FAILED

I am in Orange Co, CA. Same issue. Very frustrated with ATT. Ironically had them sell me uverse internet and when the tech came out to install, was unable to do so and found out that I am not in the area receiving uverse service. He is an ATT employee and told me he would NEVER have ATT wireless because of the poor quality. VERIZON will be getting 5 new customers as soon as my contract is up with ATT!!!!

Message 35 of 52 (2,918 Views)
Highlighted
Teacher

Re: Call Failed

[ Edited ]

Unfortunately, the past several weeks have been a bit ridiculous with the MicroCell.  When I go into the call history on my BlackBerry, I see that every call I make or receive while on the MicroCell fails just short of the fifteen minute mark, without fail.

 

It seems pretty obvious at this point that, for whatever reason, the MicroCell is not actually capable of doing what it was advertised to do in congested markets.  Whether this is an issue of design or execution (or both) doesn't really make a difference, since AT&T seems incapable (or unwilling) at this point of solving the problem one way or another.

 

One can only hope that the Verizon iPhone will relieve some of the demand on AT&T's overburdened network.  If not, I'm going to have to seriously consider other options come contract renewal time...

Message 36 of 52 (2,850 Views)
Contributor

Re: CALL FAILED

I had the same issue Iphone 4. To fix, I setup QOS in my router. These are the ports numbers you will want to prioratize to high:

 

 NTP Traffic-123/UDP

 

 HTTPS over TLS/SSL for provisioning and management traffic- 443/TCP

 

 IPSec NAT Traversal for all signaling, data, and voice traffic- 4500/UDP

 

 IPSec Phase 1 prior to NAT detection, after which 4500/UDP is used- 500/UDP

 

Found the info on AnandTech's website.

Message 37 of 52 (2,130 Views)
Guru

Re: CALL FAILED

Strictly speking, the NAT tunneling on port 4500 is really the only thing you need to prioritize. The HTTPS and ISAKMP (port 500) only happens at the very beginning, and the NTP is not critical.

 

It is often much easier to simply prioritize by either the physical Ethernet port on your router or the Microcell's MAC address. But if port numbers are your only option, then just do UDP port 4500. 

Message 38 of 52 (2,115 Views)
Contributor

Re: CALL FAILED

Can you give more user friendly directions about how to do this?

Message 39 of 52 (2,096 Views)
Guru

Re: CALL FAILED

Not really; it's different on every router, and I don't have yours.

 

In any event, there's only one symptom that indicates that you have problems that QoS implementations will fix. That symptom is if other callers report hearing choppy audio from your end. That indicates that the outgoing packets are getting dropped and/or delayed. None of the other symptoms - and certainly not 'call failed' - can be adequately explained by uplink contention.

Message 40 of 52 (2,088 Views)
Scholar

Re: CALL FAILED


nsayer wrote:

Not really; it's different on every router, and I don't have yours.

 

In any event, there's only one symptom that indicates that you have problems that QoS implementations will fix. That symptom is if other callers report hearing choppy audio from your end. That indicates that the outgoing packets are getting dropped and/or delayed. None of the other symptoms - and certainly not 'call failed' - can be adequately explained by uplink contention.


Agreed. They are most adequately explained by insufficient gateway capacity

Message 41 of 52 (2,587 Views)
Contributor

Re: CALL FAILED

I get about 50% of my outgoing calls failing to connect. 

 

I drop calls that are connected.

 

And I get a lot of people telling me that my signal is broken up/ cutting in and out while I'm connected via M-Cell.

 

This thing really, really SUCKS.

 

ATT- FIX IT! 

 

I have a Sprint AirRave for my Fiance's phone and it works ALL THE TIME, and it NEVER DROPS Calls. So it's not me ATT.

 

It is YOU. Fix. It.

 

Jason

Message 42 of 52 (2,562 Views)
Contributor

Re: CALL FAILED

[ Edited ]

Just wanted to throw in my 2c.

 

I have an iPhone 4 with iOS 5.0

 

I also have a MicroCell, connected to an Airport Extreme router.

 

I've been able to reliably replicate an issue where the first call I try to place is failed, and if I try again immediately after it'll start working "perfectly".

 

If I reconnect to the MC or wait about 15-30 minutes, the issue crops up again.

 

I have a reserved IP address for the MC as well as port forwarding to it and default NAT host set to MC as well, but the issue persists. I don't know what kind of effect this has on incoming calls, but it seems to make initial texts to people take longer as well.

 

Edit: Pretty much just like the poster on page 3 here: http://forums.att.com/t5/3G-MicroCell/CALL-FAILED/m-p/2556233#M5062

Message 43 of 52 (2,506 Views)
Scholar

Re: CALL FAILED


Broderik wrote:

Just wanted to throw in my 2c.

 

I have an iPhone 4 with iOS 5.0

 

I also have a MicroCell, connected to an Airport Extreme router.

 

I've been able to reliably replicate an issue where the first call I try to place is failed, and if I try again immediately after it'll start working "perfectly".

 

If I reconnect to the MC or wait about 15-30 minutes, the issue crops up again.

 

I have a reserved IP address for the MC as well as port forwarding to it and default NAT host set to MC as well, but the issue persists. I don't know what kind of effect this has on incoming calls, but it seems to make initial texts to people take longer as well.

 

Edit: Pretty much just like the poster on page 3 here: http://forums.att.com/t5/3G-MicroCell/CALL-FAILED/m-p/2556233#M5062


It has nothing to do with your network settings. If your microcell has successfully connected, you should be ok on your end.

 

It has to do with the gateway (a piece of equipment at AT&T that your microcell talks to) refusing to accept the incoming call because it doesn't have any capacity left, and the gateways are AT&T's problem, not yours.

Message 44 of 52 (2,480 Views)
Contributor

Re: CALL FAILED

[ Edited ]

Exact same thing here. My wife and I have iPhone 4 and 4s respectively and we joke about how ridiculous this is that it takes 3 tries to make a phone call with the microcell. Having bad reception is difficult, not being able to make outgoing calls on the device that we have placed on our internet service to fix this issue is just insulting. We have Verizon fios and a very strong internet connection. http://www.speedtest.net/result/1540857318.png

 

ATT PLEASE ADDRESS THIS ISSUE, IT'S REAL..

Message 45 of 52 (2,445 Views)
Share this topic
Announcements

Welcome to the AT&T Community Forums!!! Stop by the Community How-To section for tips on how to get started.