Recent content by jneiberger

Not only is it perfectly acceptable, it's how it's done on Juniper routers, just to give a little different perspective. If you entered "200.200.200.150 255.255.255.128" on a Juniper, it would have no idea what the heck you were doing. Cisco's way isn't the only way to do things.

Nevermind. We were able to get it working.

We are playing a prank on a new employee and have put really old equipment in her cubicle including an ancient rotary phone. It can dial out, but it doesn't ring when I call it. I've tried a newer rotary phone and it doesn't ring, either. I'm guessing I screwed something up somewhere, but I...

I was just talking to our other phone guys. One of them said that this was one of the first quirks of our Avaya system that he learned when he started many years ago, long before CallXpress. The head network/phone supervisor at the time just told him that it happens and no one has been able to...

Thanks, I'll check into that, too!

That's an interesting idea and worth checking into, but the weird part about this is that it's never the same extension that it happens to. It's always different. And we know that our phone system admin (who is also one of the senior data network admins) did not hit *3 and it happened to him...

I think they took our existing configuration and converted it. We had a two-week period where our configuration was frozen so that the new config would match the old one after the conversion. I think I see where you're going with that. If it's a configuration issue, that would explain why it...

We don't have SAC buttons on any phones, and the phone system admin definitely did not hit *3 on his phone. We're stumped.

We use CallXpress for voicemail, which uses 4 to delete mail. I'm not aware of any reason why users would ever hit *3 in our environment. It certainly seems odd that it keeps coming up, but we've never been able to figure out why. This has been going on since long before I got here three years ago.

SAC activation is #3, deactivation is #3. We don't have codes assigned to Remote SAC. A few of us have always just assumed that users were accidentally typing *3, but a couple other older admins didn't agree. They said the system just seemed to do it randomly. Whenever I ask a user if they...

I've been working at this company for three years and we have been having a weird problem for even longer than that. Intermittently, it is as if the PBX randomly selects an extension and turns on SAC. We always thought the users were accidentally doing it somehow, but they would swear they...

Our main phone guy returned to the office and figured it out. He actually had to go into "change locations" and set the rule back to 0. They had been previously set to rule 1, which was causing them to move forward an hour. But the system had already been updated, so that made the effective...

The info about the date-time button is not helpful for us since we do not have that button on any of our phones.

Mitch, I do trust you. I don't understand you. lol The system has the correct time. It jumped ahead one hour just as it was supposed to. The phones jumped ahead two hours instead of one. What would cause the phones to jump ahead two hours?

Okay, but why would the phones be an additional hour ahead? They jumped ahead two hours. That just seems weird that the system time jumped one hour as it was supposed to, but the phones jumped ahead two hours.