Brandon, figure anything out about mine at all?
Printable View
Brandon, figure anything out about mine at all?
Just curious what happens with yours?Quote:
Originally Posted by Vumes
FXS2 won't register no matter what I do. Also, on inbound calls, even though FXS1 is registered, I get a fast busy when I answer the Voipo phone, and the calling party goes to Voicemail.Quote:
Originally Posted by Xponder1
Ok and you have it set like this? ( XXXXXXXXXX = your number)Quote:
Originally Posted by Vumes
Port 1
SIP User ID: XXXXXXXXXX
Authenticate ID: XXXXXXXXXX
Port 2
SIP User ID: XXXXXXXXXXB
Authenticate ID: XXXXXXXXXXB
On both
Outbound proxy on both ports blank.
Unregister on reboot : Yes
Primary SIP server: central02.voipwelcome.com
And under advanced page
Config Server Path : blank
?
When I did it I went a page at a time and it would say the changes will take affect after reboot but then I just went to the next page. When I changed it all I then hit the reboot button.
They also had me check and make sure my dial plan matched on both. My dial plan shows the following.
{ *12 | *400 | [2-9]xxxxxxxxx | 1[2-9]xx[2-9]xxxxxx | 011[2-9]x. | [49]11 | [x*]+ }
All but the outbound proxy on port 2. It is also central02.voipwelcome.com
Is the STUN setting enabled on Line 1, but not Line 2? If so, try enabling it on both.Quote:
Originally Posted by Vumes
Make sure both ports have the "Unregister on Reboot" option set to yes.
proxy needs to be empty they sayQuote:
Originally Posted by Vumes
Tim,Quote:
Originally Posted by VOIPoTim
Stun is set to YES on both and so it Unregister on Reboot. I am removing the outbound proxy now to see if that makes a difference.
On the advanced page my stun server shows 74.52.58.50Quote:
Originally Posted by VOIPoTim
You could check that too.
Thanks Xponder, mine also shows the same. I removed the outbound proxy and that fixed the fast busy signal. So I can make and receive calls without a problem it seems, but Port 2 still will not register.Quote:
Originally Posted by Xponder1
Not trying to insult you just trying to help at the top does it say active = yes?Quote:
Originally Posted by Vumes
Ok, I spoke too soon. I can receive calls IF i don't let it ring more than one time. After that, I answer and get a fast busy still.
I just tested mine and let it ring a few times then answered and it was ok.Quote:
Originally Posted by Vumes
;) No problem, and yes both of them say YES to active.Quote:
Originally Posted by Xponder1
Tim is it possible that a Vpanel setting could have anything to do with the problems described?Quote:
Originally Posted by Vumes
Just throwing out random ideas. I find it weird mine works flawless and he is having a problem with it unless Brandon changed something on the VOIPo side that I do not know about that only affected me (or maybe did not affect him as intended).
Xponder, is your ATA in front or behind your router? Mine sits behind the router forcefully. So just throwing something out there to see if that could be a reason. Prior to this unregistering problem that started the other day, everything was going well.
User ID is phone number: NOQuote:
Originally Posted by Vumes
SIP Registration: Yes
on both?
Both look just like that.Quote:
Originally Posted by Xponder1
Behind my router. Linksys WRT54GS V6 running DD-WRT with the ports forwarded to the device as per the paper that came with it. 5060 5079 90 5004Quote:
Originally Posted by Vumes
Have you tried to DMZ your ATA?
Oh, and is yours set to a static ip address? I use my router to force mine to use the same ip when it gets its DHCP info.
Yes, mine looks the same. Different router, but I had no problems with this ATA prior to this registration issue.
I guess I can just roll it back to how it was, I'm just really curious to what is going on. :cool:
I am convinced your problem is on their side. Has Brandon messaged you?Quote:
Originally Posted by Vumes
No, maybe he's sleeping like a normal human being. :p
Dunno his last post was "please stand by" lol :pQuote:
Originally Posted by Vumes
"Please stand by till morning. Thank you" LOL he he he.
He is going to have a neck ache from falling asleep on his desk....Quote:
Originally Posted by Vumes
Maybe his forehead is hitting the "Do not Register Second Line for Vumes" button.
Yeah go ahead and switch back for now.Quote:
Originally Posted by Vumes
We're going to call it a night and resume this in the morning to give things time to sit overnight. For those of you testing, it would be great if you could leave it overnight, it should be fine.
This way we can see how it holds up overnight and we can push it out during the day when more staff is available for support issues that could come up.
Here is an update:
--
At this point we've pushed out one update network-wide that should resolve this for most users that were experiencing it.
We also have many of you testing on a switch with the final fix on it. We're going to make sure no issues come up with that overnight and then roll that out tomorrow. At that point we anticipate the users experiencing this will see it completely disappear.
Tomorrow we'll make an announcement about it and explain what caused it and what was happening. We'll also be issuing some service credits when the dust settles for affected users.
We apologize for an inconvenience and want to especially thank the huge number of you that volunteered to help test the fix implemented tonight.
to forum ·
--
Back to the matter at hand, my local sip port on FXS1 is 5079 and local RTP port is 5004. FXS2 local sip port is 5062 and local RTP port is 5012. Yours the same?
Sounds good. Thanks Tim for the update.
Anytime. I love to mess with things. Thanks for the hard work!Quote:
Originally Posted by VOIPoTim
Ya mine is the same on both.Quote:
Originally Posted by Vumes
Ah well, thanks for the tips. I will revert back for now and hopefully it stays registered for now. I'm patient, so no biggie.
I bet they fix it for you in the morning after a huge cup of coffee.Quote:
Originally Posted by Vumes
Buenas noches everyone.
Tim, I tried to revert back by adding provision.dev.voipo.com to the Config Server Path and I hit update, then reboot, and it did not revert. It did stay, but did not go back to sip so I am trying it manually. Just thought you should know. This can wait till morning, so no worries.
Update::: Don't know if this is normal, but I reverted back, and everything works as it should, but I just looked up and the lights on Line 1 and Line 2 are both blinking together. It's been going on now for about 10 minutes. I made a call and received a call and it works fine, but the lights are blinking.... Anything related to this ongoing problem?
Morning Update..
Good Morning, VOIPo....Bet you all had a rough night.
This is a summary of my experience..
I have the 502 and it sits behind a wireless router. Never a problem until the one time it unregistered. Upon reboot, it was ok. I did try my SPA-2102 to see what happens, but although it worked on all functions, it did drop registration from time to time. Haven't tried it on Central02.
Last night I went with the test bed settings. Turned right up and I left it overnight. Still fine this morning.
The only settings I changed were those specified..the rest were as they were after the clone provisioning update a few weeks ago.
What I have now is....
STUN=disabled
Central02 on Sip and OB Proxy
Phone no. in port 1 both in sip user and authenticate
Phone no. +B in port 2 both in sip user and authenticate
Port 1 DNS mode=SRV
Port 2 DNS mode=NAPTR/SRV
Port 1=unreg on reboot=yes
Port 2=unreg on reboot=no
These settings, with the exception of the server selection and +B on line 2 phone number were all the same as it had and was working since inception.
I will leave it on Central02 until you indicate I should switch back to sip.
Thanks to all of you for some really hard work troubleshooting and support all through the night..
Good morning,
Here's the situation at 7:45 AM EST:
HT502 CPL shows both ports registered.
vPanel: You do not currently have any devices registered to our servers!
FXS1:
Outbound: call completed OK
Inbound: Failover
FXS2:
Outbound: call completed OK
Inbound: Failover
Edit:
Power-cycled the HT502 and vPanel shows one registration. Incoming call on both ports working.
Edit:
Unregister on reboot:
FXS1: Yes
FXS2: No
Edit 09:43 EST:
vPanel now showing three devices, all with identical data (port numbers, expiration time, etc.)
Ken
The previous thread reminded me to take a look in the VPanel, even though everything is working well..
Tim mentioned that the +B line would not show up in the VPanel, however this is what I see at the moment...I'm still on Central02..
305xxxxxx sip:305xxxxxx@192.168.1.6:5079 2009-01-29 14:01:39 Grandstream HT-502 V1.1B 1.0.1.21
305xxxxxx sip:305xxxxxx@192.168.1.6:5079 2009-01-29 14:01:39 Grandstream HT-502 V1.1B 1.0.1.21
edit: I just did notice that the call history stopped recording at about 6:03 pm last night. I would guess that this was due to the server change.
Certainly not anything important for the moment.
Is that what the device does during a f/w update? (Even if so, not sure why it would have gone on for so long...)Quote:
Originally Posted by Vumes