I started the recent thread "What happens when POP setting in ATA not same as voip.ms portal?" and I thought my problems were over when I changed everything from toronto6 to toronto5.
Turns out a new problem developed today, don't know exactly when, but I was dealing with a live-chat but had to cut it short - and I don't think they can help!
New problem is that I get dialtone, I dial any number (even a did belonging to another voip.ms account) I think I get 1 or 2 rings, then I get fast busy. This is with two ATA's (SPA112) that were working perfectly for a month or two (I had the problem with them where I think someone had logged into the user account and did a call forward to a UK number). These ATA's are no longer login-accessible from the web. The receive calls fine. Calls that are attempted don't show up in voip.ms call log.
Voip.ms thinks that the ATA's outgoing traffic is somehow "trapped" in our lan, but I don't buy that. Another theory is that there's too much sip-port traffic hitting our wan-side - we don't have a good handle as to how to see that yet. We were messing around with an ER3 lite but went back to our old router (never turned it off) and still this problem remains. Power-cycled everything and still can't dial out. But dialing in is fine.
Any ideas what's going on here?
Maybe next thing I'll try is hard-code toronto5 server IP into the ATA.
↧