Quote:
Originally Posted by VOIPoTim
Nope- I just plugged it in when I got it. Ive never been into it...
Ive got a ticket in about a request and made a note in a reply about the no incoming...
:)
Printable View
Quote:
Originally Posted by VOIPoTim
Nope- I just plugged it in when I got it. Ive never been into it...
Ive got a ticket in about a request and made a note in a reply about the no incoming...
:)
Still going strong guys. The problem I had like last week was because I had two numbers in simul ring. I got a email from support saying they are aware. Removing the second number fixed it.
It's a very nice ATA.
Have you used the router functions on it at all?Quote:
Originally Posted by Xponder1
Ya it works fine.Quote:
Originally Posted by VOIPoTim
I don't use this device, and I generally don't like to use the router functions of an ATA because they are rarely as good as a dedicated router. However, one advantage of having an ATA-router combination device is that you can easily bypass your LAN for purposes of testing VoIP problems (which are usually LAN-related). Routers can generally be set up to do PPPoE authentication, for example, and can be configured to have a routable public IP address (I don't think the PAP2 can do this except as a simple DHCP client). And while you are testing, your computer can still reach the internet (again, not possible where the PAP2 gets the public IP address). Once the VoIP problems are resolved, you can always turn off the device's router functions and go back to using a dedicated router if you choose.
I'm wondering whether these considerations played a part in VOIPo's trying out this device, or is it just because you can get a good deal on them?
Both. A competitor in CA had a few thousand of these and preferred Grandstream devices. We will never touch Grandstream devices again....so we traded.Quote:
Originally Posted by caseydoug
LOL Hands down you got the good end of that deal.Quote:
Originally Posted by VOIPoTim
Quote:
Originally Posted by Xponder1
No Doubt!
Been solid here since the config file was fixed up.. ;)
I'm sure you've mentioned it somewhere in this thread ... but things change. Are you using the test devlce as a replacement for the original or are you running both in parallel?Quote:
Originally Posted by Xponder1
I asked Tim about this early on, but don't remember if there was an answer.Quote:
Originally Posted by Russell
I'm not they will both register if in parallel.
I have problems trying to register in parallel, even with the two adapters on separate public IP addresses...
And Brandon confirmed these problems would happen.
Yes, I know and ran it in this mode for a while but had some issues at which point I pulled the plug. The purpose of the question was to determine if both adapters simultaneously on was considered a scenario that was expected to work and if Xponder was doing so.Quote:
Originally Posted by burris
I also suggested awhile back that maybe they could assign a temp DID for the testers...that way we could leave it hooked up and any testing wouldn't interfere with our main line.
I don't remember if I heard back..
I disconnected my PAP2 and I am using this instead. I did however "try" to make it work with both but it was a epic fail. Once you get it up and running you should not need the PAP2. It works fine.Quote:
Originally Posted by Russell
Just an update for you guys --- you now should be able to use both the RT31P2 device and PAP2T / etc in parallel. We've made a change that will now allow this.
Happy Testing!
________
Glass Pipes
Well I am happy with device as is but this will make some of the others more likely to use theirs. Sounds good.Quote:
Originally Posted by VOIPoBrandon
Just re-enabled that line on my pap2 so both devices now active and seems to be working correctly...
:)
If you hook up both ATAs and they are both provisioned to your main number along with the clone feature, what is the process?Quote:
Originally Posted by chpalmer
Things are getting pretty hairy, I'd say!Quote:
Originally Posted by burris
It should be fine actually. All should ring.Quote:
Originally Posted by burris
Well, I plugged in the RT31P2 (in addition to the PAP2T). Phone lines lit up on the front console of the RR31P2. vPanel showed the device as registered. Checked dial tone on all 4 lines. But, within a matter of minutes the phone LEDs went dark on the RT31P2. Working fine as a router (the computer on which I'm typing this gets its wired connection from the RT31P2). But the phone's dead on it. I really don't want to open a ticket for something like this.
Looking at the voice admin page I see: "Can't connect to login server".
Looking further I see the proxy set to "sip-east01.voipwelcome.com". Shouldn't it be the byod server for these test devices? Should I just get the credentials and server from BYOD in vPanel? What do others have?
Its not set to auto-provision?
I thought they were to be plug&play like the PAP2T?
BYOD- here... was on west01 when I first got it but support moved it over...
Ya support will have to reprovision it and you should either submit a ticket or use the online chat. Does not take them long to fix it at all. It must be on byod or it wont work.Quote:
Originally Posted by Russell
Opened a ticket.Quote:
Originally Posted by Xponder1
Btw, for VOIPo folks reading this, it'd be nice to have a Priority drop down when opening a ticket. I typed in "Low priority" in the ticket. Perhaps you get so few tickets that it doesn't matter but it'll give you a sense for how important the customer considers the issue.
Has anyone used this behind a router yet?
I have my RT plugged in behind my router along with the PAP2 and in and out works fine..Quote:
Originally Posted by VOIPoTim
Better question...has anyone noticed anything not working on them?
Any features you've tried and had issues with?
Only issue worth mentioning I noticed right after reading this message from you. I looked at my ATA and the lights were out. Contacted support via chat and they fixed something on their side and had me reset my ATA. Then I tested a call and could dial out but not receive a call. So they changed something else and had me reset it again. Now it works. When I asked what was changed they said somehow my SIP credentials were reset on your side.Quote:
Originally Posted by VOIPoTim
Any idea how that happened? Maybe one of the recent changes?
Thanks,
Something I did notice with SIP ports..
PAP2 is provisioned for ports 5060-5061
RT is provisioned for ports 5061-5062
Doesn't appear to be causing any problems, but should any of the ports overlap with a setup like this?
Both of mine are 5060 and 5061. Not reporting this as an issue but stating a fact. Brandon fixed mine last night so it now registers. They're both online at present. I need to test incoming after which I'll make the RT31P2 feed the house wiring. Notice it does a ring splash with voicemail which the PAP2T did not - I like the ring splash.Quote:
Originally Posted by burris
That means your router is doing its job correctly :DQuote:
Originally Posted by Russell
Same ports, different internal IPs.
But now that I think of it,
In devices, I have the real world IP.
I only have the PAP2T so no worries here.
Do both your ATAs report the same IP and the same Ports???
I know. That's why I said, "Not reporting this as an issue but stating a fact." :-) when I responded to Burris' comment about common ports.Quote:
Originally Posted by usa2k
It reboots every once in a while. Which kills your internet connection for everything behind it when it does. Just did it a few minutes ago and I saw a "network cable unplugged" popup in my XP box. Since this is a freebie it's no biggie. However, I wouldn't want to put devices behind it for which I want excellent uptime. And also there's a slight window in which you can miss a call - this behavior is probably shared with the PAP2T as some kind of VOIPo config "feature".Quote:
Originally Posted by VOIPoTim
Quote:
Originally Posted by VOIPoTim
Not yours but I used the last one I had with my Voipo numbers with no issues...
Although I reported that it was working with both ATAs behind the router, last night I had an inconvenient experience as a result..Quote:
Originally Posted by Russell
Forever it seems, I keep my simulring activated to my cell and it has worked flawlessy. Last night, however, after going to sleep and having shut off my cell, we got a few calls from my wife's brother up North...the phones rang once--CID appeared--but line was dead. After the second call, we called back to find out that my wife's sister was injured. Her brother said he left 2 messages, but I couldn't figure out how as our answer machine was empty.
The messages went to my cell voice mail.
Anyway, I looked at the VPanel and with no intervention from me, both ATAs were now using the same SIP ports. Changed by itself since earlier in the day.
I removed the RT ATA and all went back to normal.
Lesson...don't experiment when you're not there to intervene if something goes South..
Since I got it, I have used it off and on, always behind the router, and in addition to PAP2T.
I had to reset it from back button originally since it would not connect, once done, and populating provisioning field, it provisioned and connected right away, not a single hiccup so far.
When I power it up, shows up in vpanel. Phone connected to it rings with PAP2T connected phones, and essentially works like a cloned line.
I have setup distinctive rings for some of my phone numbers in vpanel, and it works great on both PAP2T and rt31P2.
My router is MONOWALL.
dvijen
Burris, a little OT, but what is the normal behavior when simulring is active and your cell is turned off? I mean without the new ATA, does your VOIPo line ring?Quote:
Originally Posted by burris
With the PAP2 or with my SPA2102 even when the cell is off, my VOIPo line rings.Quote:
Originally Posted by caseydoug
I suspect the instance of 2 ATAs sharing the SIP ports may have caused the problem, and as I mentioned, even though it worked earlier in the day, something changed at night that caused both ATAs to latch on to the same SIP ports. Earlier in the day, only one port was duplicated.
If you have simulring with your cell in effect and your cell is off and you get a call, presumably your cell's voicemail will answer the call almost right away - (of course your VOIPo line will ring once before the call reaches your cell network and voicemail answers). So, wouldn't you get the exact behavior you've described?Quote:
Originally Posted by burris
Burris, essentially you're expecting Google Voice behavior with Call Presentation in effect?