I have not reconnected it. I am just going to wait till they ask us to hook them up.Quote:
Originally Posted by Russell
Printable View
I have not reconnected it. I am just going to wait till they ask us to hook them up.Quote:
Originally Posted by Russell
I've left it connected to the Internet, with a spare phone connected to Line 2 of the new device. I'm also letting it to DHCP to my main computer - a personal RT31P2 I have reboots on a regular basis and I'm curious if this will exhibit any similar symptoms.Quote:
Originally Posted by Xponder1
Edit: a 4-line phone now connected to both devices (standard issue and alternate) which are online. Please let me know if doing any of this is going to impact my ability to receive incoming on my regular ATA.
Is it possible to get http access to the box? Saw some lights flash - this box may be also exhibiting rebooting behavior, either spontaneous or VOIPo induced. Without access to the box it's not easy to determine.Quote:
Originally Posted by Russell
My RT31P2 rings both lines every few minutes - one short ring.
Sounds like the vm splash setting I believe.Quote:
Originally Posted by Russell
Seems to have gone away - next time I have voice-mail I'll see if there is a correlation.Quote:
Originally Posted by ptrowski
Tim,Quote:
Originally Posted by VOIPoTim
Waitin for your instructions to switch the device.
Yes, definitely VM Splash. New voice mail and sure enough we hear the short rings on a regular basis. Can't this be configured the same way as a PAP2T? Since the device is in our bedroom you can well imagine the wife's reaction to my "hobby" :-). And, it takes an awful long time for the VM Splash to go away after I delete the voicemail - I don't think it went away even then until I lifted and placed the receiver down a couple of times (I need to try this out to confirm).Quote:
Originally Posted by Russell
Thing is I don't think were officially testing them yet. I am sure it will not be much longer.Quote:
Originally Posted by Russell
I believe the rebooting on a regular basis was due to a configuration issue. Brandon tweaked something and it no longer reboots like the way it did before. VOIPo folk do remember that since this device can act as a router (and that's how I'm using it) customers can connect a computer to it and when it does it rebooting thing the computer's internet connection can potentially "freeze". That is, if this box is similar to my hacked RT31P2 I previously used where I would notice such freezing behavior, glance at my router and see it rebooting. Just something to keep in mind.
We're working on documenting what we want to test with them and will post that at the beginning of next week at the latest.
If anyone wanted to experiment in the meantime, you should be able to get incoming calls on them now after they reprovision.
Thanks for the update Tim.
I would like to try it out as well.
Yes, I can confirm that all four lines on my 4 line phone light up when I call the VOIPo number. Pretty sight! Tim, any reason not to leave both adapters on line (I've had them on line for quite some time now, but previously there was no incoming).Quote:
Originally Posted by VOIPoTim
Fwiw, the RT31P2 now feeds the house wiring (essentially replacing the PAP2T) as far as the numerous phones in the house are concerned. The PAP2T only feeds my 4 line phone.
RT31P2: Child from home complains that calls cannot be answered. Phone rings but when child picks up - silence. I called home and the calls went to voicemail. I'll attempt to verify this pm (and switch away from the RT31P2 if the issue is still present.
I have been waiting on the mentioned documentation before hooking mine up but I went ahead and hooked it up since you said that incoming calls should work after they reprovision.Quote:
Originally Posted by VOIPoTim
I logged in mine using the directions on linksys site and it does not appear to be setup to be provisioned by VOIPo. Everything is default settings. IYE-227622 is the ticket #
After posting this I found the manual for providers and logged into
http://192.168.15.1/Voice_adminPage.htm with no trouble at all. Nothing is configured.
Well after chatting with support this morning and having them remote in and determine something was screwy with the ATA because my settings I had put in to make it provision itself were not working and waiting hours for a reply I got tired of waiting and decided to try another step. I reset the ATA back to factory defaults, added the provisioning url and saved, reset by unplugging.
All stuff I had done before except I had not reset factory defaults.
Then like magic it decided to start working. Both lines working and confirmed can make both in and outgoing calls from both lines. My best guess is somehow the config file was corrupted. Weird but it works.:p
I found this to be funny because usually people are trying to unlock their ATA and I was trying to relock (provision) it.
Tim in Vpanel it says "You are currently connected to: sip-byod.voipwelcome.com" with options to change it. With the PAP2 I was on central. Should I leave it or is it safe to change it?
Device worked great until tonight. I received a call and the device lost its sip connections. I unplugged it and it connected again. Made a test outgoing call and that was fine. Made a couple test incoming calls and both failed. The phone would ring but it was dead air on this end followed by a busy tone. Submitted a ticket (Ticket ID: RSE-677109 ) and continued trying. Managed to receive two calls and then the device lost connection again and has not reconnected.
Waiting on support to reply before I reset it again.
Leave these on sip-byod.voipwelcome.com per support (dont change it in vpanel).
This had nothing to do with my issue (at the time of this posting I am working with support to resolve). I just wanted to share since I never got a answer to the question and thought it may help someone else.
See my posts #54 and 55 in this thread. After the incidents described therein, I switched away (had both ATAs on at the same time so not sure if that was an issue). Currently I only have the production PAP2T in service.Quote:
Originally Posted by Xponder1
Support just helped me get mine working again. It was fine for a day. I can now make outgoing calls and receive calls again. Russell I decided to start testing mine because you stopped posting about it. Thought maybe you had yours working :)Quote:
Originally Posted by Russell
I had mine running when I first got it, but took it down as Tim indicated they weren't ready yet.Quote:
Originally Posted by Xponder1
Are you testing yours on your main number? Early on, I sort of suggested that maybe Tim would assign a temp DID so that we could test it without the chance of messing up our main line.
Xponder, if you look at #54, you'll probably get an idea of how excited I was that morning. I then left for work. During which time a child at home couldn't receive calls and I didn't get back till late in the evening (see #55). Very upset spouse caused a termination of the experiment :-(. And, shortly thereafter we had visitors (wife's folk) for a week and I didn't want to have a phone system which was not "perfect" and production VOIPo was superb! Another variable: I'd also got a new 2-line phone in the kitchen at about the same time and I needed to confirm the silence on the calls was not due to family ineptly using the phone.Quote:
Originally Posted by Xponder1
It's configured to be a replacement for your ATA (main number), I believe.Quote:
Originally Posted by burris
Ya as Russell said its just my main number. I offered to experiment with it because I do not use the phone a lot and I have lots of other phones. I expect downtime. The guy in support apologized for the inconvenience but I told him not to worry about it because I enjoy this stuff and I can not help them fix it if I stick my pap2 back in every time I have a issue.Quote:
Originally Posted by burris
On a side note I tried leaving my pap2 and this thing connected at the same time but had issues. I think it may be because these are on another test byod server and the pap2 is on central.
Ya I had read your posts before. I just assumed since all had been quiet here for awhile that you got yours working. I will continue to report on mine. Still waiting on that list Tim :pQuote:
Originally Posted by Russell
Yes, when I had issues with not being able to answer I had both ATAs connected. The experimental one was feeding the house wiring and the production one was feeding the other two lines of my 4-line phone.Quote:
Originally Posted by Xponder1
So maybe it would work better if you leave the pap2 disconnected OR maybe support can put your pap2 on the byod server. Just a thought.Quote:
Originally Posted by Russell
But you're allowed to have soft-phones (connected to the byod server) concurrently with the PAP2T. Why is the having the RT31P2 with the PAP2T any different? Anyway, I was waiting on a yea or nay from VOIPo on whether it was allowable.Quote:
Originally Posted by Xponder1
Well I see a couple of problems with it. First they are on two different servers. That could cause issues. Second they are using the same ports. It's now 3:33PMCST and the ATA is still going strong.Quote:
Originally Posted by Russell
Isn't that also true when you use a softphone and ATA at the same time?Quote:
Originally Posted by Xponder1
It used to be until they put all the new softphones on some other server. I personally caused a network outage with my softphone/ata combo months ago.Quote:
Originally Posted by Russell
Another update for those of you with this device. Still no problems with the device. So its been up about 48 hours now.
plugged mine in today for first time in two weeks or so. Wont register today.
Normal support channels?? :D
Ya thats what I would do. I was going to report I had a issue with mine today but I think it was because i had two simul ring numbers setup. I removed the second number and life returned to normal.Quote:
Originally Posted by chpalmer
Thanks!
I just remembered that when I had it up before I had put it in parallel with my router up against the cloud.
Today I tried from behind the pfsense box. Ill give it a try paralleled again later after working hours....
Mine is pointed at west01 and I have no way to change it to byod in vpanel. Ill have to go back to the pap2 till support can look at it after the weekend....
:)
Does it connect?Quote:
Originally Posted by chpalmer
These are being provisioned to the BYOD server and using BYOD credentials.
Did you change the hostname to west manually? If so, the credentials are prob still the BYOD ones if they came from provisioning.
Mine is still working. I have tested the router and it works fine.