I have 4 devices showing up in Vpanel right now. Things seem to be working fine, but I thought it was a little strange.
Printable View
I have 4 devices showing up in Vpanel right now. Things seem to be working fine, but I thought it was a little strange.
vPanel reverted to:
You do not currently have any devices registered to our servers!
Sorry I missed this thread last night, otherwise I would have gladly helped with the testing. FWIW, I'm running ok as of a few minutes ago, after having to reboot a couple of times yesterday...
This is good. I bet enabling Unregister on boot would take care of this. When it shows 3 lines, that's typically what it needed.Quote:
Originally Posted by KenH
I've had the same IP/port showing as a registered device on more than one occasion, although it is now only one, and I've never noticed anything acting wrong or strange when it was more than one.
Tim:Quote:
Originally Posted by VOIPoTim
Didn't make any changes to configuration, rebooted, and vPanel only showing one device now. Should I change the Unregister on Reboot setting?
Ken
Tim..
Should we consider going back to the sip server, even though all seems to be ok?
I was out for a while and tried to call home..Wife said that although both phones rang, line one got an immediate busy when answered, but if line 2 answered, it worked fine.
I got back and rebooted and seems to work now.
Burris, did you happen to have unregister on reboot enabled for both FXS1 and FXS2?Quote:
Originally Posted by burris
Morning update. I still have my device configured as it was last night. Both incoming and outgoing calls are working fine. Vpanel shows only one device listed but someone just mentioned that at this time that is normal. I also noticed Vpanel is not logging calls but that does not surprise me.
Looks good.
Are you sure you do not have voice mail? That would make both lights blink.Quote:
Originally Posted by Vumes
Brandon....Quote:
Originally Posted by VOIPoBrandon
If you remember, when we turned up the clone feature, you specifically mentioned to have one of the 2 lines set to yes and the other to no.
I've had it this way all along, and until the problem a few days ago, everything worked perfectly.
As I mentioned, I'm still on Central02 and when I called home before, one of the 2 lines was set yes and one to no. I set both to yes and seems to be working ok.
One we enable the call logs for central02, it'll be fine. Just a display/permissions change.Quote:
Originally Posted by Xponder1
Right now my ATA information page says "NOT REGISTERED" and I go directly to voicemail. I am running the test config.
1:18 PM EST
HT502: Neither port registered and vPanel: No devices registered
Still in test configuration.
My status shows registered again now. Maybe an intermittent problem or something on the new server? At least the ATA re-registered itself but my inbound calls were still down 15-30 minutes or so.
You learn something new everyday. I do indeed have voicemail. I deleted them and the lights went off. Sheesh. Thanks.Quote:
Originally Posted by Xponder1
I think Ken and Scott just helped us discover something very key here that's been completely overlooked.
More testing to confirm then we'll post. Thank You! :)
Sweet! Glad to hear!
2:56 PM EST
HT502: FXS1 Registered, FXS2: Not Registered
vPanel: No devices registered
Should I reboot?
Edit:
3:26 PM - Rebooted. HT502: Both ports registered. VPanel: one registered device.
Yes. I believe this will be the last time.Quote:
Originally Posted by KenH
Has anyone else notice a drop this afternoon since I posted that it's fixed?
Tim,
At this time, should we retain the test settings or revert to normal configuration?
Ken
Ken,Quote:
Originally Posted by KenH
Right now to be honest it shouldn't matter. It appears the issue was completely unrelated.
Returned HT502 to normal configuration. vPanel and HT502 CPL show both ports registered. I notice that now, NAT is shown as Symmetric, rather than Full Cone.
Incoming & outgoing calls are OK.
Update from me - I have not made any changes since the initial changes last night which did not involve making it unregistered and I am still up and working. No issues so I have not touched any settings today.
Forgot to add - vPanel has only shown one device registered the whole time. I do not have a 2nd phone hooked into FX2 so have not tested or anything there.
Can you start a brand new thread tonight with something to the tune of "Network Problems Fixed" so everyone can find it right away and maybe make it a sticky? Hope the problem is fixed for good and hope there was a good explanation for it too. Thanks!Quote:
Originally Posted by VOIPoTim
Although all seems to be working well and I am still on Central02, the VPanel devices still show only one instance. Call records are up to date.
Since it is working, it really doesn't matter except to make you aware of it.
Maybe because line 2 still has a B after the number?
I did not partake in any of this testing, but I do have the 502 registered 3 times in the CP !!!
502 is currently outside the router but I would like to move it back in sometime.
Update 9:02 PM CST. Still setup with test configuration. Outbound calls using 7 digits on port 2 go to a busy signal again. Inbound calls work on both ports. Add the area code and the call goes threw. Have not tested a 800 number. Brandon had this fixed last night did something change?
I will reboot my ATA and try again in a little while.
Everyone should be able to revert to the normal configuration without issues now as well.Quote:
Originally Posted by Xponder1
Ok I will say that when I rebooted it had the same issue. I will go ahead and revert as requested.Quote:
Originally Posted by VOIPoTim
I reverted back and logged in and took a look at the settings and it shows a outbound proxy (sip.voipwelcome.com) on port #2 and not on port #1 and port number 2 unregister on reboot is set to no. Port 1 is set to yes.
Phone is working fine on both ports.
I see the same configuration on my HT502.Quote:
Originally Posted by Xponder1
Everything is working for you though right?Quote:
Originally Posted by KenH
Yes, everything seems to be OK this morning.Quote:
Originally Posted by VOIPoTim
I would like to know what the proper settings for those items is, though.
Ken
Mine is working fine on both ports. I only pointed it out because they are settings you or Brandon asked us to change. I dunno what mine is doing this morning but its sure hammering away at the internet. The wan light is flashing none stop and my router is showing its hammering away. It is using somewhere between 250 and 500kbps none stop with the phone not in use. Are you all doing something? It seems to be all outbound traffic from the device.Quote:
Originally Posted by VOIPoTim
I didn't have any issues throughout the weekend, while there were others troubleshooting. I just came home for lunch. Incoming calls are not coming into our phone and of course, no MWI.
I checked vPanel and no devices are registered.
I just rebooted my ATA and all appears to be well again.
My ATA is behind my router with all the appropriate ports forwarded.
Dan
This did make me think of a feature request...
I don't need an SMS for every call/voicemail, but it would be great to have an option to send an SMS if Failover (either to voicemail or another number) is "triggered".
Dan
I'm still having issues. Almost once a day; maybe every other day; I lose incoming calls and have to reboot the adapter. Then it's fine for a while again. My settings are the same that others are mentioning. I notice by telnetting in that my port 1 will become UNREGISTERED (Yet I can call out); and Port 2 will still show REGISTERED. Luckily, between failover and simultaneous ring, I'm not missing calls.
It's possible that every time VoipO makes a change, that it's requiring the adapter to be rebooted. If true; this wouldn't be a problem if VoipO was only making changes every so often. But this is becoming a regular thing. I personally am not upset, because I'm a techno-geek and don't mind troubleshooting it. And as long as outgoing is still working, my wife will never know. (Most calls are outgoing; very few incoming). I believe the same thing is happening to my beta line which is on a Linksys RT31P2. I've had to reboot that one a couple of times. Same issue; outgoing fine, incoming not. This is only something that's been happening for the last few weeks. I've move the 502 into the DMZ of my router just in case. "Even though I don't have any router settings that should be affecting the voipo lines".
Any thoughts??? If not, I might take it off of auto-provisioning so I can experiment with certain settings. But the fact that similar things is happening with the Beta line on the linksys, makes me believe that it's something at the SIP server level. But to be honest, I haven't monitored the Beta line as extensive because I normally don't have a lot of incoming calls on that one. I will check it when I go home tonight to see if I have to reboot it. later... mike....
Has anyone had a drop today (and you know it was fine this morning) or could these have been from yesterday/overnight?Quote:
Originally Posted by christcorp