Something stuck? No Vpanel or inbound calls

I guess I can just roll it back to how it was, I'm just really curious to what is going on. :cool:

Quote:

---

Originally Posted by Vumes

Yes, mine looks the same. Different router, but I had no problems with this ATA prior to this registration issue.

---

I am convinced your problem is on their side. Has Brandon messaged you?

No, maybe he's sleeping like a normal human being. :p

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 :p

"Please stand by till morning. Thank you" LOL he he he.

Quote:

---

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

Maybe his forehead is hitting the "Do not Register Second Line for Vumes" button.

Quote:

---

Originally Posted by Vumes

I guess I can just roll it back to how it was, I'm just really curious to what is going on. :cool:

---

Yeah go ahead and switch back for now.

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.

Quote:

---

Originally Posted by VOIPoTim

Yeah go ahead and switch back for now.

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

---

Anytime. I love to mess with things. Thanks for the hard work!