| [Voip.ms] No ringback heard on outgoing calls. Having lots of intermittent problems lately with not hearing ringback when making outbound calls on Voip.ms. The called phone rings and, if answered, the calls complete, but the caller does not hear any ringback signals - just silence until the call is answered. We're using various Grandstream devices (GXP2100, GXP2124, etc). I have a trouble ticket opened with Voip.ms (no response yet), but I'm hoping some of you folks may have suggestions. |
|
 XCOMdigitalnUllPremium
join:2002-06-10
Spring, TX | Sorry no issues here.
--
[nUll@dcypher ~]$ |
|
azmike
join:2012-07-19
Phoenix, AZ | reply to lilarry
Am having very similar issues. Any outbound call takes roughly 15 seconds until I hear ringback. However the calls do eventually complete.
I just tested by calling my cell phone, ringback and ringing of my cellphone happen almost simultaneously. Again roughly 15 seconds after placing the call. Los Angeles, Seattle, Dallas and New York all exhibit this behavior for me.
Seems to be a recurring voip.ms issue. Oh and by the way Vitelity termination takes about 4 seconds. |
|
Reviews:
 ·Start Communicat..
 ·voip.ms
 ·Rogers Hi-Speed
| reply to lilarry
I've had this happen on occasion, dating back to February or March - around the time I started using VoIP. It didn't do it for a while, but lately it's been a bit more frequent, and it doesn't seem to matter which server (I've had it happen on montreal, chicago and newyork). The next call usually works fine, so I haven't reported it (yet) because I can't reproduce it "at will". |
|
garys_2kPremium
join:2004-05-07
Farmington, MI | I think they should be made aware of even transient issues so they get a heads-up about issues. Inconsistent problems are the worst to fix, but they still ought to be on their radar. |
|
| reply to lilarry
said by MichelR:I've had this happen on occasion, dating back to February or March - around the time I started using VoIP. It didn't do it for a while, but lately it's been a bit more frequent, and it doesn't seem to matter which server (I've had it happen on montreal, chicago and newyork). The next call usually works fine, so I haven't reported it (yet) because I can't reproduce it "at will".
I've noticed it on and off for quite some time myself, but it has gotten particularly bad over the past couple of weeks.
said by garys_2k:I think they should be made aware of even transient issues so they get a heads-up about issues. Inconsistent problems are the worst to fix, but they still ought to be on their radar.
I agree. Intermittent problems are extremely frustrating. They really need to be able to duplicate it in order to diagnose, and sometimes just doesn't duplicate at will. You can make 1000 test calls, give up, and then the problem happens on call 1001. That being said, the matter should still be reported. They need to know, and hearing from many customers might help them validate and diagnose the problem.
Meanwhile, I'm just wondering if there's something in the router or network that could be causing this. UDP 10000-20000 is open, SIP-ALG is disabled. What may I be missing? |
|
| reply to garys_2k
I just realized I had created a ticket about this several days ago, so I just updated it and added a link to this thread. |
|
azmike
join:2012-07-19
Phoenix, AZ | reply to lilarry
I just had to dig a bit more. Here's a capture from wireshark. To be specific it took 13.023 seconds until I heard ringback on this attempt (notice lines 11 and 13).
|Time | www.xxx.yyy.zzz |
| | | 69.147.236.82 |
|0.000 | INVITE SDP ( telephone-event) |SIP From: sip:myvoipmsacct@seattle.voip.ms To:sip:5551231212@seattle.voip.ms
| |(30874) ------------------> (5060) |
|0.110 | 407 Proxy Authentication Required |SIP Status
| |(30874) <------------------ (5060) |
|0.203 | ACK | |SIP Request
| |(30874) ------------------> (5060) |
|0.269 | INVITE SDP ( telephone-event) |SIP From: sip:myvoipmsacct@seattle.voip.ms To:sip:5551231212@seattle.voip.ms
| |(30874) ------------------> (5060) |
|0.392 | 100 Trying| |SIP Status
| |(30874) <------------------ (5060) |
|13.415 | 183 Session Progress SDP ( telephone-event) |SIP Status
| |(30874) <------------------ (5060) |
|13.512 | RTP (g711U) |RTP Num packets:134 Duration:2.659s SSRC:0xC6D3B1E4
| |(7576) ------------------> (14924) |
|13.638 | RTP (g711U) |RTP Num packets:134 Duration:2.659s SSRC:0x7D65BC54
| |(7576) <------------------ (14924) |
|16.200 | CANCEL | |SIP Request
| |(30874) ------------------> (5060) |
|16.313 | 487 Request Terminated |SIP Status
| |(30874) <------------------ (5060) |
|16.313 | 200 OK | |SIP Status
| |(30874) <------------------ (5060) |
|16.442 | ACK | |SIP Request
| |(30874) ------------------> (5060) |
|
|
|
|
azmike
join:2012-07-19
Phoenix, AZ | reply to azmike
FWIW calls to my cellphone are the only constant at the moment. That is they are taking ~14 seconds. Almost every other call I make is taking 3 or 4 seconds...??? |
|
| reply to lilarry
I have been having the same issue as well but it only happens when voipms has issues with one of their other proxies and registers those customers to the proxy im using. I notice that all of my devices will be registered to tampa, the one I always use, and then to the proxy voipms is having issues with. Once they fix the proxy issues and im only registered to one proxy, my problems go away.
I opened a ticket about it but was told just to change my proxy which does not solve the problem IMO. This has happened to me 3 times in the matter of one month and Im considering porting the 10 numbers I have with them to another provider. |
|
| Same issue here. It happens on and off. It's pretty frustrating and I'm actively looking for a company to port our 3 DIDs. |
|
| reply to lilarry
Right now all of my devices are registered to tampa, toronto, and toronto2. Keep in mind im only suppose to be registered to tampa, all of my aastra phones are telling me "no service". My cisco devices show "no registration", and the one linksys ata is registered but no ringback tone. WTF! |
|
 crazyk4952Premium
join:2002-02-04
united state
kudos:1
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| reply to lilarry
I have had this issue with voip.ms off and on for the last several months (maybe as long as a year), too. I now use a different provider for outgoing calls because of this issue.
It would be great if they could fix this issue so I don't have to maintain balances with multiple providers! |
|
SCADAGeo
join:2012-11-08
N California
kudos:1 | reply to lilarry
said by lilarry:Having lots of intermittent problems lately with not hearing ringback
I'm hoping some of you folks may have suggestions.
I can understand how frustrating it can be when you're a reseller and your customers are complaining.
Unfortunately, there is nothing you can do - it's a resource issue at the VoIP.MS servers, and they are working on it:
I wonder if they are accepting volunteers for the late alpha testing phase or beta testing phase?
BTW - I am making the assumption that "alpha servers" are servers in the alpha testing stage, as opposed to having a server with alpha processors (which were awesome for their time).
said by garys_2k:I think they should be made aware of even transient issues so they get a heads-up about issues. Inconsistent problems are the worst to fix, but they still ought to be on their radar.
It's been on their radar for a while, and the resource issue has been alluded to:
said by lilarry:I agree. Intermittent problems are extremely frustrating. They really need to be able to duplicate it in order to diagnose, and sometimes just doesn't duplicate at will. You can make 1000 test calls, give up, and then the problem happens on call 1001. That being said, the matter should still be reported. They need to know, and hearing from many customers might help them validate and diagnose the problem.
It's easy to catch programmatically.
Support employees, programmers, sys admins, and others that have access to the systems can use tools such as vmstat, top, iostat, nmon, ipcs, Ganglia, or check the CDR's for call disposition.
said by lilarry:Meanwhile, I'm just wondering if there's something in the router or network that could be causing this. UDP 10000-20000 is open, SIP-ALG is disabled. What may I be missing?
You're not missing anything.
said by azmike:I just had to dig a bit more. Here's a capture from wireshark. To be specific it took 13.023 seconds until I heard ringback on this attempt (notice lines 11 and 13).
|0.000 | INVITE SDP ( telephone-event) |SIP From: sip:myvoipmsacct@seattle.voip.ms To:sip:5551231212@seattle.voip.ms
Great job! You've abstracted the server farm (POP), you're treating it as a system (black box), and testing input and output. 
Your result is pointing directly at the resource issue, and the value is usable as a data point in the creation of a metric.
You will be able to create other metrics if you continue on this path.
said by crazyk4952:I have had this issue with voip.ms off and on for the last several months (maybe as long as a year), too. I now use a different provider for outgoing calls because of this issue.
It would be great if they could fix this issue so I don't have to maintain balances with multiple providers!
I believe that any good contingency plan would offer multiple options.  |
|
| reply to lilarry
long running problem, recommend you switch carriers, have not had good luck with them for the past few months at all, like an overcapacity problem or bad servers maybe |
|
MartinMVoIP.msPremium,VIP
join:2008-07-21 | reply to lilarry
After finding what I think is the ticket for this customer, we've had our staff trying to replicate the issue in lots of ways. So far we've not been successful but we switched the carrier for the customer.
If someone in that thread experiencing this issue could send me an exact scenario on how I could try to duplicate this issue, I would appreciate. (In private)
Account Number, Number Dialed, Server used, device/software used, timestamp and of course Ticket #, if you don't already have one, please open one.
--
Martin - VoIP.ms |
|
| said by MartinM:After finding what I think is the ticket for this customer, we've had our staff trying to replicate the issue in lots of ways. So far we've not been successful but we switched the carrier for the customer.
You found the right ticket - it's me. Changing the carrier has not helped. Indeed it has added a new issue: Now there is a 30 second delay before calls go through.
said by MartinM:If someone in that thread experiencing this issue could send me an exact scenario on how I could try to duplicate this issue, I would appreciate. (In private)
I've added the CDRs to the ticket. I wish I knew how to duplicate it at will, but it always happens eventually if you make enough test calls. (Damn - I hate intermittent problems).
Martin, I will private message you on this - but I really would appreciate a response this time. |
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| Please keep us posted on this issue, as I would really like to switch back to voip.ms for my outbound provider when this issue has been resolved.
MartinM, I do not have any examples of this happening. Usually, I would just be so impatient waiting for outgoing calls to complete that I just hang up before completion. Then they do not show up in the call log.  |
|
| reply to MartinM
I haven't had any problems on my last few calls - it's pretty much felt like a normal landline for the past few days. |
|
 mozerdLight Will Pierce The DarknessPremium,MVM
join:2004-04-23
Nepean, ON | reply to lilarry
I am having the same issue today and what is really annoying is when I enter the extension number nothing happens.
I was using the Atlanta server --- so I switched back to the Montreal server and now when I enter the extension number it now works but no ring-back when placing the call to this specific client. Now I know that my client very recently switched all their lines from Bell POTS to Rogers VoIP so maybe there is a tie-in to that -- will have to give it some time and see if this sorts out before end of January.
Perhaps there are numerous changes taking place with people switching from Bell POTS to VoIP and the "Telephone System" is having trouble adjusting to all these changes.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
