Anybody else have problems with voipo to voipo calls? All I get after 20+ seconds of dead air is fast busy signals.
Printable View
Anybody else have problems with voipo to voipo calls? All I get after 20+ seconds of dead air is fast busy signals.
Sometime that is an issue. I rarely talk to other VOIPo numbers.
I found that setting up a shortcut to the sip address is a good work-around.
I *think* ?
sip:voipo_number@in.voipwelcome.com assigned to a shortcut
Yes. Starting yesterday, dead air issues. All other calls to cell phones and landlines are OK. I submitted a ticket last night. Nothing has changed on my side, so I suspect something was changed on their side.....Quote:
Originally Posted by patoka
Hey guys -- can you advise if you are still having any further issues with VOIPo to VOIPo calls. We've been working on a fix for some long standing VOIPo to VOIPo issues this week and we hope to have it all rolled out shortly. In the course of rolling it out it is possible some of these intermittent issues are a result. Look forward to hearing back from you all, thanks!
Brandon, it's still not working. I'm now getting mostly fast busy signals. Sometimes it rings only to get dead air, only once did I reach the caller then it goes dead after 30 seconds with a fast busy signal. The other Voipo caller reports the same problem.Quote:
Originally Posted by VOIPoBrandon
Ticket ID: GUA-137605
Can you please PM me calling FROM # and calling TO #
Also preferably a phone number to reach you at so I can grab a network trace interactively with you.
Thanks!
________
Fourth generation subaru legacy history
We are experiencing the failing calls (Voipo-to-Voipo) as described by others. When the connection is successful, the calls disconnect almost immediately. We've tried several times to resume/complete our call. They continue to fail which is why I ended up "here". The problem began this afternoon PDT.Quote:
Originally Posted by VOIPoBrandon
Hey guys ----
I believe I've worked with everyone in this thread who has reported an issue privately.
Please do let me know if you guys continue to run into any further issues, or if any other newcomers are experiencing issues.
We think that we've fixed all "basic" on-network issues such as pure voipo to voipo calling.
Some issues have been reported with Call Routes, *67, etc. and we will be working through these reports and other various known issues.
Thanks for all of your input and cooperation!
________
Toyota opa
Brandon, this issue is back again. Calls disconnect after 20 seconds with a fast busy signal. Other Voipo caller reports same problem. It worked fine yesterday.
Hello,
Did this occurrence happen around 6 PM CST? Is it still occurring currently? Please advise -- thanks!
Around 6:20 pm CST. I tried twice. The calls went through ok, but disconnected after 20+ seconds with fast busy. The other Voipo caller tried to call but got nothing but dead air with no ring at all.
Hello,
Thank you for this information! I found an issue with another user around the same time and it was resolved, this will affect you as well. Please do let me know if you continue to run into any further issues. Thanks!
________
Toys kinky
Thanks, it's working good now. I noticed the Voipo calls are showing up in vPanel's call history log today.....nice to see this fix too.Quote:
Originally Posted by VOIPoBrandon
Looking forward to call forwarding and call routes being fixed as well........
Brandon,
Don't know if this is related or not, but when I call my Voipo fax line, my main number rings... :confused:
-Bret
Calling it from within the VOIPo network has this problem and if calling from outside the network it's fine?Quote:
Originally Posted by bretski
Correct. If I call my fax number from my cell, it works. If I call it from my main VOIPo line, it goes to my voicemail. If I call from my virtual number, the main line rings. Want me to open a ticket?Quote:
Originally Posted by VOIPoTim
Update: I went ahead and opened a ticket. Brandon resolved the issue. Thanks again, Brandon!
What about the issue with an ATA registered to the VoIPo server, and softphone/IP phone registered to to the BYOD server.
I currently have both the ATA and IP phone registered to the BYOD server because both would not ring, only one or the other, depending on which one registered last.
Has this interoperability issue been resolved, or is it still required that all devices register to the same server to receive calls?
After I started this thread tech support got me going again. Last night v-v calls failed again. I started a new ticket, this morning I can only call a voipo phone.
I have 3 pages of tech support tickets since I signed up, what's the record?
Around what time did the VOIPo to VOIPo issue occur? (please be timezone specific). Also do you currently have a ticket open? Please PM me the ticket reference ID. Lastly are you currently experiencing any issues? Please advise - thanks!Quote:
Originally Posted by patoka
It will no longer matter what server you are registered to in correlation to who you are placing an on-network call to.Quote:
Originally Posted by lifespeed
There are some current known issues / restrictions with VOIPo to VOIPo and simultaneous ring & call recording.
And to that I would add an issue with simultaneous ring when dialing VoIPo via SIP URI. Ring-in-order failed to forward to the mobile when dialing a VoIPo number (calling from another SIP provider) using SIP URI, but worked correctly using the PSTN number.Quote:
Originally Posted by VOIPoBrandon
It's getting better, I hope you continue to work on these remaining bugs.
Hi Brandon.
I to had VOIPo to VOIPo issues on 10/19/2010. I want to know if I need to do anything at this point? I will make a few test calls to my parents (other VOIPo party).
On 10/19 around 6:20PM central time, my dad called. We got disconnected around 30 seconds later with a busy signal. My dad thought he hit something on his cordless phone and I called him back, but same thing, disconnected and busy signal. I called him 5 times and we just got frustrated and called it a night as we kept getting disconnected.
Please advise and if you need more information from me. Thanks.
Justin
Brandon, my business partner and I have been having terrible problems with voipo to voipo calls since we switched to voipo, many months ago. 1 legged calls, disconnects, takes several dialings to connect, terrible call quality, etc. many, many calls to support, changed servers several times and even moved us both to same server (Texas) and it got even worse. He's in Toledo, so I had them move him to the East Coast Server and me (Anaheim) to the West Coast Server, but I'm not expecting much improvement. Can you give me the exact instructions on how to set up a sip shortcut? I've used this trick on some of my SIP trunk customers' systems with good results. I know how to do it with Asterisk IP PBX systems, but am not sure how to do it with VoIPo. Jim Sheehy @714-398-8249
Which phone number do you put in the Phone number field? My phone number or the other phone number? I'm pretty sure that "sip:9999999999@in.voipwelcome.com" is what goes in the "Forward to" field, where 9999999999 would be the voipo number I want to call. Do I use my voipo number in the "Phone Number" field or his number? I've used this trick with some of my SIP Trunk customers and know how to do it with an Asterisk IP PBX, but not with VoIPo. Thanks mucho. Jim Sheehy@714-398-8249
Do you mean for call forwarding?Quote:
Originally Posted by Hoser
You should always just use the phone number.
The SIP address stuff with @in.voipwelcome.com is only for advanced SIP calling from outside the VOIPo network to within the network.
Try using just the destination phone number in the phone number field.
Brandon,
FYI: I just sent you a message about another instance of Voipo-to-Voipo call problems.
Best,
-Bret