Alternate Device Testing

**VOIPoTim** · 08-31-2009 02:31 PM

Better question...has anyone noticed anything not working on them?

Any features you've tried and had issues with?

**Xponder1** · 08-31-2009 03:48 PM

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.

Any idea how that happened? Maybe one of the recent changes?

Thanks,

**burris** · 08-31-2009 06:33 PM

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?

**Russell** · 08-31-2009 07:43 PM

Originally Posted by burris

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.

**usa2k** · 08-31-2009 08:13 PM

Originally Posted by Russell

Both of mine are 5060 and 5061.

That means your router is doing its job correctly

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

**Russell** · 08-31-2009 09:46 PM

Originally Posted by usa2k

That means your router is doing its job correctly

Same ports, different internal IPs.

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.

**dvijen** · 09-01-2009 06:23 AM

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

**Russell** · 08-31-2009 10:07 PM

Originally Posted by VOIPoTim

Better question...has anyone noticed anything not working on them?

Any features you've tried and had issues with?

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".

**burris** · 09-01-2009 05:51 AM

Originally Posted by Russell

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".

Although I reported that it was working with both ATAs behind the router, last night I had an inconvenient experience as a result..

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..

**caseydoug** · 09-01-2009 07:38 AM

Originally Posted by burris

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

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?