Rick,Quote:
Originally Posted by ralfaro
I'll take a look at that ticket and we'll see what we can do for you to get you situated.
In terms of the auto login, I just made a post about it: http://forums.voipo.com/showthread.php?p=9114#post9114
Printable View
Rick,Quote:
Originally Posted by ralfaro
I'll take a look at that ticket and we'll see what we can do for you to get you situated.
In terms of the auto login, I just made a post about it: http://forums.voipo.com/showthread.php?p=9114#post9114
For what it's worth: Tim, I and Justin (VoipOJustin); worked back and forth on my Grandstream in the beginning in the week when it had all the same problems. No registration, dropping registration, etc... We changed the registration to 1 minute; changed to Central02 server; downgraded the firmware to .15. I have not had one problem sense then. There are 2 MINOR problems, but they are server related and not that important.
1) The grandstream shows BOTH PORTS registered. BOTH PORTS work. I can be on a call on PORT 1; and make another call on the clone in PORT 2. ALL IS GOOD. However; in the Vpanel; ONLY 1 device shows up as registered. Again, this is not really a problem. But I did know that prior; on the sip.voipwelcom.com server, I would see 2 registrations under device in the vpanel. Maybe it's a sip.voipwelcome.com thing; maybe the firmware; I don't know. It's not a big issue.
2) The VoipO servers are having a difficult time CALLING EACH OTHER. I.e. I have my beta line on Jupiter server and my Primary line on Central02 server. If I can FROM juptier to Central02, it rings my failover line. If I call FROM Central02 to the Jupiter, it goes to Voice Mail. This WAS an issue a time back. Maybe it is something that was never really addressed being it's not that common to talk to other voipo numbers; let alone one on a different server. I'm PRETTY SURE that if BOTH are on the same server; e.g. Beta and Primary both on Central02; then they can call each other. When I was using sip.voipwelcome.com on BOTH lines, it was fine. Again; not a problem.
Anyway; just wanted to say that things have been working fine on the grandstream and the current settings. Maybe it's the 1 minute registration. Maybe it's the downgraded firmware to .15. Maybe it's useing the central02 server. Maybe it's a combination. Tim and Justin know they can use my lines to experiment with if needed. Any time day time hours Mon-Fri. And we can work more together any night or on weekends. But current configuration is stable and a good bench mark for any one that needs the info. My BYOD (Beta line on Linksys) never had issues on any of the servers. Even when I moved my primary to it prior to fixing the grandstream issues. Great job Justin and Tim. You guys have a very high work ethic. As does all the voipo employees. Later... Mike.....
Well I sent you my info so please let me know which of the two are me lol :pQuote:
Originally Posted by VOIPoTim
Would of replied sooner but as I had to work today. I am off the next couple of days.
Update I just checked and the ATA shows both ports registered but Vpanel only shows one.
Both ports are working. (Reminds me of the "B" test we did). UPDATE logged in with the admin password and it is the B config we tested.
Product Model: HT-502 V1.1B
Software Version: Program-- 1.0.1.21 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76
System Up Time: 19:09:09 up 2:23
PPPoE Link Up: Disabled
NAT: Symmetric NAT
Quote:
Originally Posted by eagle 1
For what its worth, I moved my device back behind my firewall and its a little better. I also noticed that that Ip was getting hammered by three different Ip addresses (Thousands of times per hour).
I set the firewall to only allow the specific ports and Ipaddress specified by support and it seems better.
the offending ip's were:
Name: pbx-vancouver1.mdci.ca
Address: 204.209.14.50
Name: s0106001ee5355afc.ss.shawcable.net
Address: 70.64.23.199
Name: 209-20-73-234.slicehost.net
Address: 209.20.73.234
Yeah none of those IPs are related to us so definitely block them.Quote:
Originally Posted by eagle 1
Could always contact them and ask them nicely to leave your ip alone.Quote:
Originally Posted by eagle 1
Just checked at 6.30am and ATA shows I am registered. But vPanel does not show any devices. Incoming going to network down number.
NAT table shows no entries for the adapter. I have a feeling that the adapter is not sending the keep-alive or re-registration request.
Rebooted my adapter and everything is back to normal.
So far not very many reports of this and things look normal.Quote:
Originally Posted by sr98user
One thing we have seen before though is if the device is behind a router the internal DHCP IP changes and it doesn't like that.
Do you have it setup with a dynamic IP by chance?
Yes. And I was able to access the ATA configuration pages and it said it was registered. So it does have an IP.Quote:
Originally Posted by VOIPoTim
I can't receive inbound calls or make outbound calls. Opened a ticket.
Inbound calls ring, but can't be answered. When it goes to voicemail, it drops the call.
Outbound calls just fast busy.
Scott