Delay when placing calls

[gjlieber]

I also did some digging on open ports on my router and found this article on the issue with 3G microcells

http://www.anandtech.com/show/3626/att-3g-microcell-a-comprehensive-exploration/4

It recommends that the following ports be opened in the firewall:

123/UDP

443/TCP

4500/UDP

500/UDP

Essentially you create a custom firewall port configuration with these ports open, and then assign it to the 3G microcell.

I have done this, and it seems to be consistently getting calls connected in under 6 seconds which is on par with regular cell connection times.

The biggest challenge is guessing what the internal IP address is of the 3G Microcell. There is not an easy way to do this as the Microcell is locked down hard with no console interface or easy way to ping it.

[nategold]

I have had this problem recently.  Talked to tech support and they had me reset my network settings on my iPhone 4.  This definitely fixed it!  Outgoing calls are fast, no mucking with the router.

Downside - you lose wifi network saved passwords.

[nategold]

I take it all back - the fix was only temporary.  Sometimes outgoing calls are still crazy slow to connect.  Incoming seems fine.

[Otto Pylot ACE - Professor]

---

gjlieber wrote:

I also did some digging on open ports on my router and found this article on the issue with 3G microcells

http://www.anandtech.com/show/3626/att-3g-microcell-a-comprehensive-exploration/4

It recommends that the following ports be opened in the firewall:

123/UDP

443/TCP

4500/UDP

500/UDP

Essentially you create a custom firewall port configuration with these ports open, and then assign it to the 3G microcell.

I have done this, and it seems to be consistently getting calls connected in under 6 seconds which is on par with regular cell connection times.

The biggest challenge is guessing what the internal IP address is of the 3G Microcell. There is not an easy way to do this as the Microcell is locked down hard with no console interface or easy way to ping it.

---

Using the above port settings, you have to assign an IP address to the MicroCell using it's MAC address and DHCP. The MicroCell is a totally closed system so there will be no way to access it. It's fairly easy to do, at least with an AEBS.

[nategold]

gjlieber wrote:

I also did some digging on open ports on my router and found this article on the issue with 3G microcells

http://www.anandtech.com/show/3626/att-3g-microcell-a-comprehensive-exploration/4

It recommends that the following ports be opened in the firewall:

123/UDP

443/TCP

4500/UDP

500/UDP

Essentially you create a custom firewall port configuration with these ports open, and then assign it to the 3G microcell.

I have done this, and it seems to be consistently getting calls connected in under 6 seconds which is on par with regular cell connection times.

The biggest challenge is guessing what the internal IP address is of the 3G Microcell. There is not an easy way to do this as the Microcell is locked down hard with no console interface or easy way to ping it.

---

Using the above port settings, you have to assign an IP address to the MicroCell using it's MAC address and DHCP. The MicroCell is a totally closed system so there will be no way to access it. It's fairly easy to do, at least with an AEBS.

--------------------------------------------------------

If you port forward those ports to the Microcell, doesn't that preclude other devices on the network from using them?  If so, this seems very wrong.

Nate

[Otto Pylot ACE - Professor]

---

Otto Pylot wrote:

---

Using the above port settings, you have to assign an IP address to the MicroCell using it's MAC address and DHCP. The MicroCell is a totally closed system so there will be no way to access it. It's fairly easy to do, at least with an AEBS.

---

Adding to my above post, we have 5 cell phones in our immediate family. 2 iPhone 3GSs, and three old Samsungs. We have extended the approved list to include other family members which includes another iPhone 3GS, an iPhone 4, and two other phones of unknown manufacturer. None of the phones have any difficulty at all making or receiving calls, no delays, and messaging is fine. I think once you get a good GPS lock and setup a permanent  tunnel using the above settings to a Version 2 MicroCell, you'll be fine. Even if they update the system again. At least I hope so

[Otto Pylot ACE - Professor]

---

If you port forward those ports to the Microcell, doesn't that preclude other devices on the network from using them?  If so, this seems very wrong.

Nate

---

I don't believe so. My router is setup with it's basic default settings and the only device connected to it via the LAN ports is the MicroCell, and like I said, it has a dedicated IP address. All other connections are done wirelessly. We have lots of devices connecting at various times while someone else is using the MicroCell and we've never had any problems connecting to the inet or have noticed any drop in speeds at all. We've been streaming Netflix while someone chats away on their cell phone and have never had any problems.

[gjlieber]

nategold wrote:

Using the above port settings, you have to assign an IP address to the MicroCell using it's MAC address and DHCP. The MicroCell is a totally closed system so there will be no way to access it. It's fairly easy to do, at least with an AEBS.

--------------------------------------------------------

If you port forward those ports to the Microcell, doesn't that preclude other devices on the network from using them?  If so, this seems very wrong

I guess I was not clear that these settings are not done to the Micro Cell but rather are a configuration that is created in my 2Wire AT&T router's firewall.  After these port configs are created and saved on the router, then they are simply assigned to the 3G microcell's IP address.  Guessing the IP address is the only tricky part as you cannot assign a static IP address to the Microcell.  If the microcell is rebooted, there is a good chance that it will pick a new IP address from the Router's pool, and then you will have to assign the port config to the new IP address.

[AnClar]

Not to be a party pooper, just to provide another viewpoint on open/forwarded ports and the MCell...I have a v.2 MCell, a Linksys WRT610N router and McAfee firewall.  The MCell is configured to be behind the router, not in priority mode.  I have not forwarded any ports for the MCell, nor have I opened those ports in the firewall, although I do have IPsec passthru enabled.  To this point my MCell has worked perfectly so I don't know what to make of the necessity of opening or forwarding ports.  It hasn't been necessary for me thus far.

[Otto Pylot ACE - Professor]

I guess I was not clear that these settings are not done to the Micro Cell but rather are a configuration that is created in my 2Wire AT&T router's firewall.  After these port configs are created and saved on the router, then they are simply assigned to the 3G microcell's IP address.  Guessing the IP address is the only tricky part as you cannot assign a static IP address to the Microcell.  If the microcell is rebooted, there is a good chance that it will pick a new IP address from the Router's pool, and then you will have to assign the port config to the new IP address.

---

I've power cycled my AEBS, DSL modem etc, and still had no problem with the MicroCell reconnecting with GPS and the 3G signal. Sounds to me that your router, or your setup, needs to be reconfigured. I know you can't configure your MicroCell so it has to be done within your router.  Sorry if I sound like an support person, and that's not my intent, but if your entire network is hardwired, then you'll need to contact AT&T on how to configure it. It's not that difficult.

[MyDogHasFleas]

---

If you port forward those ports to the Microcell, doesn't that preclude other devices on the network from using them?  If so, this seems very wrong

answer:  well, yes, so if you have another server that requires being able to listen on these ports for incoming requests, that's not going to work.  

 ---------------------------------------

I guess I was not clear that these settings are not done to the Micro Cell but rather are a configuration that is created in my 2Wire AT&T router's firewall.  After these port configs are created and saved on the router, then they are simply assigned to the 3G microcell's IP address.  Guessing the IP address is the only tricky part as you cannot assign a static IP address to the Microcell.  If the microcell is rebooted, there is a good chance that it will pick a new IP address from the Router's pool, and then you will have to assign the port config to the new IP address.

---

answer:  well that's not really the way most routers work, including the 2wire routers I've seen.  They remember devices by name and tie that to the MAC address, and so the pinholes (opened ports) follow the device around even if they are assigned a new IP address by DHCP.

Another way to do it is to configure the router to always assign the same IP address via DHCP to the Mcell.  This is also not hard to do with the 2wire routers with which I am familiar.

[nategold]

Here is my take on this.

I got the microcell about a month ago.  It did not have the delay until a few weeks ago for me.  I can temporarily fix it by *any* of the following means:

1. Reboot the microcell.

2. Reset the iPhone 4 network settings, but don't do this as it is only temporary and does the same thing as #3.

3. Put the iPhone in airplane mode, wait, and back out again.  If it does *not* say Searching... then it will not fix it.  If it does say Searching... and reacquires the mcell then it is fast again - only temporarily.

Last year when I tried the mcell, the iPhone 4 always needed to be put into airplane mode and out again to see the mcell when I came into the house.  Now it always sees it, but I think something is amiss causing the delay.  I do *not* believe that it is router settings, but I could be convinced if someone has the problem and permanently fixes it with router settings.  From my understanding, port forwarding those ports is pretty dangerous as others on the network won't be able to use them then.

I urge all of you to open cases with tech support.  Direct line is (866) 246-7344.  Some of those folks are pretty good.  The person I talked to yesterday said they do not have access to this forum.  So I believe it is just us talking amongst ourselves.  Open a case like I did, call back, annoy them, get them to look at this.

Nate

[Otto Pylot ACE - Professor]

---

AnClar wrote:

Not to be a party pooper, just to provide another viewpoint on open/forwarded ports and the MCell...I have a v.2 MCell, a Linksys WRT610N router and McAfee firewall.  The MCell is configured to be behind the router, not in priority mode.  I have not forwarded any ports for the MCell, nor have I opened those ports in the firewall, although I do have IPsec passthru enabled.  To this point my MCell has worked perfectly so I don't know what to make of the necessity of opening or forwarding ports.  It hasn't been necessary for me thus far.

---

I'm not entirely convinced that port forwarding is needed either, but that was the only way I could get mine to work after AT&T's disastrous upgrade. I never had to do that before. I just haven't had time to go back, disable port forwarding, and see what happens. It seems to me, or is apparent to me, that AT&T still doesn't have their *stuff* together and there isn't one fix that's going to work for everyone throughout AT&T's entire service area.

[Otto Pylot ACE - Professor]

Another way to do it is to configure the router to always assign the same IP address via DHCP to the Mcell.  This is also not hard to do with the 2wire routers with which I am familiar.

---

That's the way I've configured mine.

[nategold]

My experience with this is that if you haven't used the mcell in a while it will be very slow for the first call.  If you quickly make another outgoing call it is fast.  And then when you leave it idle for a while it will be very slow again.

[thively]

---

AnClar wrote:

Not to be a party pooper, just to provide another viewpoint on open/forwarded ports and the MCell...I have a v.2 MCell, a Linksys WRT610N router and McAfee firewall.  The MCell is configured to be behind the router, not in priority mode.  I have not forwarded any ports for the MCell, nor have I opened those ports in the firewall, although I do have IPsec passthru enabled.  To this point my MCell has worked perfectly so I don't know what to make of the necessity of opening or forwarding ports.  It hasn't been necessary for me thus far.

---

Well working on my "theory" I believe the issue would depend on the router and firewall.  I have a D-Link DIR-655.  It's possible the Linksys software running on your router is better at identifying that this is supposed to be a persistent VPN connection and keep the ports active.  Or perhaps it's just more lenient in this regard.

While you should not have to do port forwarding, it's possible this aleviates the issue on particular brands/models that seem to cause the problem.

I'm not even sure port forwarding is even the right answer but it seems to have worked in my case.. at least on this router on this ISP.

I also have an M-Cell at work.  It's on a Netgear router (not sure what brand) and on AT&T 6Mbps DSL.  I have never done any special configuration to that router.   I have never experience any delay on incoming or outgoing calls nor have the other 8 people that also use the MCell (and I've asked them)

[mxnick]

I have the issue, same as everyone else. I had an iphone 3 for a while, and the propblem was intermittent. I switched to the iphone 4, and got a GPS antenna for my MCell, and now the problem (delay) happens with EVERY call. It is very, very annoying and unreliable. Will try calling the above listed tech support number. There are too many people with the same issue on this forumn for there not to be a solution. Oh, and I am in the SF Bay Area (Los Gatos).

[nsayer]

---

mxnick wrote:

There are too many people with the same issue on this forumn for there not to be a solution.

---

Don't be so sure. AT&T has demonstrated repeatedly that they do not care about whether the Microcell works or not. If it works for you, then great. If not, then there is nothing they can or will do for you. The last suggestion I got from an AT&T employee was to sell my Microcell on eBay.

[TXCraig]

Same problem here! Houston TX

I've had this problem too but its intermittent.  Some times it will, some times it won't.  There is no pattern.

[nategold]

I often get this problem on the first call after not using the phone for a while.  First call often times out, then retrying works pretty quickly.  I opened a case with tech support (866) 246-7344 and then they closed it, claiming it was my setup.  The person also claimed that they monitor this forum, which I question.  I made them open a new case.  I suggest all of you having this intermittent problem open a case with them and then maybe it will get their attention.

[MyDogHasFleas]

I get this problem too, like others it comes and goes.  Sometimes it takes 10 seconds to place the call, sometimes only a second or too.  It's not a huge issue, but it is annoying.  I do have my ports forwarded BTW so that's not a fix.  

[nategold]

I am now getting this on almost all calls.  All of you having problems with this - open a case with tech support at (866) 246-7344.  The more the better.  And if they close the case without fixing it, like they did with me, insist that they open another one.

[nategold]

As mysteriously as it was happening on every call, now it is fixed on every call.  I think AT&T did something.  Did it get better for anyone else?

[buffyandsneaky]

turn off wifi on your phone when you are wanting to place a call using the microcell... I decided to try this because I was getting about a 60 second delay before the call would connect, and often i would get call failed.  I am thinking that the phone device gets confused with which signal it should be using.  I have an Iphone and so does everyone else in the fam... they too have to turn off wfi before placing a call.  I only turn on wifi when i need it and leave it off the rest of the time.

Hope this helps

[nategold]

Turning off wifi is not an option.

[thively]

Apparently after a while the connection seems to drop due to inactivity so when trying to place a call you have to wait upwards of 30 seconds for the connection to re-establish. So when Making a call it has to wait and sometimes times out (failing.)
The reason turning off wifi works is because this forces the phone to start using 3G data over the MCell which causes the MCell to link up so that it's ready to go by the time you place that call.

This may be why I never seem to have this problem at work where we have 9 people sharing the MCell. Theres always something going on and it never goes dormant. But for folks at home which may go hours without actually using the MCell for calls or data, by the time you go to use it, it's not ready. This should be fixable. I have an Ooma VoIP phone system (land line phone replacement) and I have never had a delay placing call on it. It uses a similar method of keeping a VPN connection alive with the servers.

[nsayer]

I've asked my wife to do this, and if she doesn't, I'll try it myself when I get home.

Trouble is, if it helps, then it's still on AT&T to fix the underlying problem. Because it's not a really tenable workaround.

It seems to me like the workaround would simply be to send a single ICMP echo request down the tunnel once every couple minutes or so. I'd be completely gobsmacked if they weren't already doing such a thing.

[nategold]

Problem is back for me often.  Turning off wifi is not something I will do, and not even sure it works to fix it.  Very mysterious why it suddenly worked well for a day and is back to its old tricks now.

[chasd]

nsayer,

Absolutely correct!

Meanwhile  I opened a case for the problem and, if they ever call me back, I will read your post verbatim.

[nsayer]

There may be something to this. My wife's phone spent the day with wifi on and I placed a call and it took a while to go through. I spent the evening with wifi off and placed a call and it went through immediately.

Now, that one anecdote isn't enough to establish a pattern, but it's encouraging.

If it turns out to be something real, then I still say it's downright astonishing that the Microcell isn't set up to send keepalive traffic to prevent exactly that sort of problem.