When I call another phone from my Voipo-connected phone, I don't hear the other phone ringing. There is silence until someone answere the phone or it goes to the persons voice mail. Is this a general problem with Voipo? How can I fix it?
Printable View
When I call another phone from my Voipo-connected phone, I don't hear the other phone ringing. There is silence until someone answere the phone or it goes to the persons voice mail. Is this a general problem with Voipo? How can I fix it?
This problem seems to be cropping up more and more lately. When I started a couple months ago with VOIPo I didn't have it. But over the past couple weeks I'd say I see this on about 50% of my outbound phone calls. Usually I just hang up and try the call again and it works. Another bug on the VOIPo side.
I can call from my phone but can't receive calls. Used tech support yesterday. Spent the whole day on the problem with no fix. Called again today and a different tech said my number forwarding won't be complete for 10 days so I won't be able to receive calls. They should have told me that in the 1st place. I thought it was going to be a plug and play type of thing.
Also the tech yesterday logged into my computer to reconfigure. Now I can only get online if my adapter is hooked up to my DSL modem. If I unhook the adapter and just use my modem to get online it won't work. So far......not happy! Way to much time wasted. Plus this is a business line so not a lot of room for error!
I just hooked my Voipo service up. I have an intermittent problem of making a call, but I do not hear the ringing of the dialed number either. Is there something I need to further do to correct this?
Most of the issues described in this thread sound like NAT issues. 99% of issues customer experience are related to routers/NAT. What happens in some cases is that the router lets the "signaling traffic" through but then when the audio stream connections on a different port it blocks it thinking it's unrelated or "malicious traffic". Many routers to try to be smarter than they are basically.
This can usually be connecting our device directly to your modem (if it doesn't have a router built in) or by assigning a static IP to the device and setting up port forwarding for ports 5004-65000 UDP to it.
Ultimately there's nothing we can do to force traffic through a router except help you configure the router to handle it. Issues that are sporadic are even more likely to be NAT related like this because the ports are randomly chosen and sometimes (when it works with no issues) we could be in one port range and then other times (when you have issues) it's in a different port range that the router doesn't like.
99% of the time it's NAT/routers that cause issues. Our support team can try to help you diagnose, but if you are having issues and don't setup port forwarding it's almost 100% guaranteed that you'll continue to have them.
I have an AT&T 2Wire 2701HG-B router. I have NO idea what you are talking about "port forwarding"? My technical ability is "plug it in and play", if it doesn't work, I am screwed. If more is needed from me, I am already out of the game. So what do we technical dummies need to do?
Tim,
While what you say is true for some cases I strongly feel there is a problem on Voipo's side. I have the proper ports forwarded and an IP assigned to the device. The problem comes and goes as it wants to. And like I've stated here in this forum over and over my previous Voip provider didn't have any of these problems that Voipo has. I used the same internet provider and modem for the 3 years I had VYL Media. It worked 100% of the time. Blaming the customers set up or equipment is getting really old. It's a problem on the Voipo side and it has been getting worse. And just like clockwork it will clear up for a couple weeks and then the problem comes back slowly at first and gets worse. It's a continuous cycle. I came here to save money. I think I made a mistake to be honest. Don't know if Voipo cut corners with their equipment or what. But your service just doesn't work as well as others.
I too am now encountering this issue - the last two calls I made (one yesterday and one today) had just silence until the call was picked up. I do use port forwarding. Ticket has been filed.
If you experience this, please send call examples to support@voipo.com with Call Samples for Tier II in subject.
We still don't see anything on our end or any patterns but it does sound like several people are having the issue. With call samples maybe we can look closer and find a pattern. It's possible it's a particular upstream carrier that if we see a pattern (such as all the same carrier) then we could isolate.
I sent the requested information to your support people this morning. I received an email response back that basically did not even address the issue nor the information I gave. All the tech did was deflect blame once again for problems that are obvioulsy not on the customer side. It was a complete waste of my time to send the information you requested. Obviously VOIPo has no desire to fix this issue. Only to deflect the blame as usual. I have requested my account be cancelled.
What is your ticket number?Quote:
Originally Posted by ram1220
XAX-506533. I have canceled my account and support has closed the ticket. But you are welcome to review it.
I did the port forward as suggested by the Voipo techs, in fact, I spent an hour on the phone with AT&T, and they did it for me while I was on the phone with them. AT&T took control of my computer and did it remotely as I watched and talked with them. To my dismay, I still have the problem of the phone that I dialed not ringing. Getting a tad frustrated here.
Support asked me to unplug my adapter for 30 seconds and reconnect it so it could get updated configuration. The next call I made I could hear the ringing.
I will give it a try. At this point, I will try just about anything. I hope I made the right decision going to this service. Been through enough hell with Magic Jack.Quote:
Originally Posted by holmes4
I rebooted the adapter, and made a call, it worked. I will cross my fingers and hope it continues, but, I will not hold my breath.Quote:
Originally Posted by markbet
I made a couple calls this A.M. and not only did I not hear the ringing on the other end, it just disconnected me and gave me a dial tone. Opened another ticket. :confused:
I think the Voipo techs got the bugs worked out. I asked the tech if the problem was on my end, or Vopio's end, he told me that it was mainly the settings in my adapter that was out of sorts. They made the changes, and all seems to be good.
Hi all,
I have had ongoing tickets with support with the same occasional no ringing heard. Like some have said, it comes and goes -- today had two calls with no ringing and then the other side picked up.
It's not a showstopper problem, but is annoying. I have the problem with the router set both ways -- port forwarded/static IP and no special settings.
What I don't understand is the call is obviously ringing the other end, or they would not pick up. It is the local adapter that generates the ringing voltage so you can hear it, correct? So isn't it something internal to the ATA?
Thanks,
Mike
I am still having an intermittent problem with making a call, and not being able to hear the ringing of the phone on the number that I dialed. It is obviously ringing, because if I stay on the line long enough, as in listen to dead air, either someone answers, or I get the answering machine. More irritating than anything. Ticket ZWY-859344
I keep being told it is my firewall settings that is causing the problems I am experiencing. So, I opened up my router/modem, went to the firewall settings and printed a screen shot of the information of how my router is set up and sent it to the Voipo techs. They said that my settings are correct. By process of elimination, that only leaves the problem on Voipo’s side, and they, the techs, suggested the same thing. They keep tweaking the adapter on their end, I hope they get it figured out at some point. Sometimes I can hear the dialed numbers ring, and sometimes I can’t, it seems to come and go. Maybe an exorcism is in order, to get rid of any lingering poltergeists in their system.
Do you have a static IP addressed to the voip adapter. If you do; as an experiment, you can go into the router and turn ON the "DMZ" and point it to the static IP address of the voip adapter. This basically opens ALL PORTS and forwards them to the voip adapter. if this works, then you know it's a ports issue.
As for the firewall, you should turn OFF in the router: SPI. That is a firewall in the router. Also, there is a section called ALG. It lists programs like SIP. Turn off the ALG. If you really want a firewall for your computers you can install a software firewall like Zonealarm or Blackice on your computers and protect them locally. But SPI and ALG on in the router can definitely cause issues with voip. good luck.
When I call a person, I can not hear the phone ringing, but, when I ask the person that I just called if their phone was indeed ringing, they say yes, it was, I just can not hear it ring. To weird for me. I would think it is on Voipo's end, not mine.
As far as the firewall goes, Voipo said that I am good to go. They took control of my computer, and set it up as I watched, so I would assume that the problem is on Voipo's side.
No problem. Just mentioning that SPI is a firewall setting on a router that can affect inbound traffic if it was on. Also, that SIP under the ALG area was meant for software SIP like skype and such, and can block communications with a hardware device like a voip adapter that wants SIP. Just something to look at. Not saying that is the answer, just that many have had issues with voip and those 2 settings.
I'm not sure how much detail you really care about here, but this can actually be tracked back to one of a few different things.
Not all audio you hear comes from the network
For example, when you pick up the phone you hear a dial tone, but that's actually generated by the device that VOIPo sent you. In fact, that device can generate every sound the phone network uses from ringing sounds, to busy signals, to the sound you hear for call waiting.
Not all calls are handled the same
This is the part that gets confusing. The ringing that you hear on a call can actually be generated in 2 different ways. Say you want to call 444-555-1234. After you finish dialing the number on your phone, the ATA device generates a request to the VOIPo servers that looks a little like this:
VOIPo's servers can respond back with something like what you see below. The "180 Ringing" response means that your adapter should generate the ringing sound.Quote:
INVITE sip:14445551234@someregion.voipwelcome.com SIP/2.0
{A bunch of other stuff goes in the packet guts, mostly things like your username, what codecs your device supports, and what UDP port you will receive audio on}
... but they can also respond back with something that looks like this:Quote:
SIP/2.0 100 Trying
SIP/2.0 180 Ringing
SIP/2.0 200 OK
{ This signals that the call has been answered and gives the remote IP handling the audio for the call }
This option uses what is known as "early media" because you get audio from the PSTN before the call is answered, so in this case the ringing sound actually comes directly from the PSTN. This is essential for dialing things like AT&T 800-number teleconference services because AT&T doesn't actually signal the call as being answered until after you've entered a valid conference pin code.Quote:
SIP/2.0 100 Trying
SIP/2.0 183 Session Progress
{ This is a bit unique in that you get an IP for call audio before the call is answered }
SIP/2.0 200 OK
{ Here the call is answered, and you get an IP for where the audio will go to/from -- it's usually the same as the Session Progress IP }
As was already mentioned, a lot of routers include a feature called SIP ALG. What it's supposed to do is read all of the SIP status messages and read things like what port your ATA says it will use for a call, and what IP your provider says will be used for the call audio, and automatically open a hole in the firewall and create a NAT mapping to get that traffic to the ATA. The problem is that SIP ALG sometimes has problems reading the SIP packets, and sometimes skips some altogether like the "183 Session Progress" packets -- when that happens, you have problems with incoming audio.
Since you're having intermittent problems, as an outside observer with limited knowledge of how VOIPo is setup these would be my first 3 guesses:
1) Your adapter isn't properly generating a ringtone for calls made on carriers that don't support early audio. If you go to your Call History and click on calls you can see a reference ID for each call. If you can provide to VOIPo support which calls had ringing and which calls didn't, they should be able to track down the carrier they used for each call and use that to troubleshoot further.
2) You have a router in front of your ATA with SIP ALG or similar functionality and it's eating some of the "183 Session Progress" messages, or preventing the correct NAT mappings from being setup.
3) VOIPo has a rarely used carrier that is being used to terminate some of your calls, and VOIPo's SIP gateways aren't properly translating call progress codes when relaying status to your ATA.
Spaeth; excellent comments. There's a lot about voip that people don't understand, and when there's a problem, it can be difficult to discern where that problem is. I noticed when VoipO was first starting up and I was Alpha testing with them, we had a certain problem. After a lot of experimenting, I found that the problem only existed when I called a certain state. The problem got narrowed down to one of the partner providers passing the packets. So that too is a good experiment to try. Do you get the no ringing with ALL calls, or only certain people/places you call. Not saying that a customer should have to know how to do any of this. They shouldn't. But voip is still a novelty/niche market. It's not something my 80 year old parents are going to buy. Matter of fact; probably 98% of the 2000 people who work with/for me have traditional phone service. Of the other 2% there's those with "Digital Voice". (Cable company's version of voip, but only in town. They hand off to the Ma'Bell). Besides me, maybe 2-3 others have "True Voip".
Another part of Voip that most people don't understand is that to make a voip phone call, it takes 2 separate parts. You have the SIP (Session Initiation protocol) Which is the part that initiates the call. It usually goes through the voip provider. (I am not 100% if VoipO is doing it this way, but most do). You connect to VoipO via the internet, they send your request through their network of leased lines to the destination you are trying to call. The SIP initiates the handshake. Your request is usually then handed through Ma'Bell (PTSN) because most calls are to a land line or cellular. Once the initiation has been established, the 2nd part kicks in. That's the RTP. (Real-time Transport Protocol). That's the part where your actual voice packets in the conversation is attached to. The UDP protocol. That traffic however doesn't follow the SIP. It normally doesn't go from you to VoipO and back out. Once the SIP has the initiation established, the RTP takes a direct route (As direct as the internet can be considering they use LCR for traffic) to the handoff gateway at the PTSN. Then your voice is converted back to analog and on to the final phone.
The problem of not hearing the other end ring in your phone is not uncommon. Unfortunately, the cause is also uncommon. You'll find that some are in the Router, having SIP ALG and SPI turned on. Some routers it's a problem; some it isn't. Some, the voip adapter actually needed a firmware upgrade. Some had port problems with the customer and the server. (They changed the server in the voip adapter config and it fixed it). Some had problems in the proxy settings using a domain name and it got corrected by putting in the actual IP address. (DNS Issue). Bottom line, there can be numerous reasons for this problem. But if it's any consolation, a simple google search will show that this problem has been reported by customers of just about every voip provider on the planet. It sucks when it happens to us personally; but the problem isn't personal.
Well it happens to me with, so far, one number. Here's what's happening and why I don't see how it can not be on Voipo's end.
I call number (AT&T Wireless cell phone - area code 661) from my softphone (Bria iPad edition).
No ringing, goes to voicemail after several seconds of quiet.
I turn off WIFI bypassing router (and ATA) and use Verizon data network on iPad. Call number again.
No ringing, goes to voicemail after several seconds of quiet.
I switch dialing out account from Voipo to Callcentric (they have pay-as-you-go plan) in softphone. Call number again.
Rings! Goes to voicemail after several rings.
Clearly the no-ringing is happening when I dial out using Voipo and not when I use Callcentric. This appears to have nothing to do with the ATA or router. Any thoughts?
In all 3 of your experiments, it goes to voicemail. Forget if you hear ringing or not. Can you call the other end. Are you saying that with callcentric, if you call the at*t wireless cell phone, it DOES RING the actual cell phone? Or do you simply hear a ringing in the headset? As spaeth was saying, it doesn't matter what you hear. The ONLY REASON phone companie put a dial tone on the phone, is to make you think the phone works. As you know, there's no dial tone on a cell phone.
Now; if you're saying that you can call the AT&T cell phone from call centric and it actually rings the cell phone and it can answer your call; then yes, there is an issue. You say it HAS TO BE voipo's end. That's not necessarily true. However; for the average customer, who doesn't know how voip works, all they care about is THEIR END; meaning their phone and internet; and VOIPO's end; meaning everything else. There's a lot more in between. But for the customer, they shouldn't care about thatl.
So; IF you can call a specific number with callcentric and the other end rings, and they can answer it; but you CAN'T when using VoipO, then open a ticket with voipo. Give them the number you are trying to call and that it won't connect. I have that problem at work ALL THE TIME. I will have a customer call up and say they can't call a specific number. Find out that a new prefix has been added in a state or country and my PBX isn't programmed for that area code or prefix. I add the number, and all is good.
Another test is to see if you can call ANOTHER 661 area code AND PREFIX phone that is similar to the one you can't connect to. Life is simple. We make it harder than it really is. But open a ticket with voipo, once you know what the true problem is, and they can definitely help you. If you don't have all the facts and are assuming certain things work or don't work, then it could take voipo a long time to figure out what the problem is. Remember; you are on Voip, and you're trying to connect to cell phone and land lines. That's 3 different technologies, with 3 different providers. What you describe is not unusual and happens every day; even with cell phones and land lines. Landlines have over 100 years of experience making a process to catch these issues. Cellular and voip have to sometimes catch these issues one at a time.
Christcorp: Thank you for the thorough response. All I'm saying, really, is that when I call said number using Voipo, I don't hear any ringing. I just get silence until the other end picks up or goes to voicemail. When I call the same number using Callcentric, I hear ringing until the other end picks up or goes to voicemail. I bypassed the router and ATA just to show that it was not specific to those devices.
Since this is only a minor annoyance and, as you mentioned this is new technology, I didn't bother writing a ticket. I saw this thread and thought I'd share my experience.
Unlike you, I opened a ticket for it. After all, this may be an issue that, sooner or later, may lead to a bigger problem. :)Quote:
Originally Posted by Stingray2U
I also bypassed my router by hooking up the VOIPO adapter to the cable box. That didn't solve the problem. I then took my VOIPO adapter with me and tried it on a friend's cable modem (different ISP) - same problem.
The funny thing is that everything on my end used to work fine until Saturday, July 28th, 2012. Nothing changed on my end, so, if VOIPO could track down what changes they made that day (or the night before) on my line, it may lead to a solution.
Finally! Registered now, you can see me. I too have been having the very same issues with dead air on my handset, ringing on the other end, person picks up and I don't hear a thing. My case is a tad different as I hear nothing during the progress of the call - no dialtone, no ring, no pick-up, no voicemail, no termination of call, nada.
After reading several posts, I powered down for 1 min, then powered back up. My phone seems to be working right now. I also opened a ticket though, as NO calls were working for two days, inbound nor outbound.
Hopefully, they will take a look at it first thing on Monday morning. My friends all think I am a crackpot for doing VOIPo, turn me into a salesman, let's get this fixed! :-)