On 03/08/2012 04:50 AM, Aleksandar Ivanisevic wrote: > On 02.03.2012 22:17, [email protected] wrote: >> One thing we did for a while was that we had a phone in the office that >> forwarded to the on-call person. It was the responsibility of the >> outgoing on-call person to change the forwarding (so that if you forgot, >> you suffered for it :-) > > We still have this, as we are required to actually answer the call to the > 24/7 oncall phone number, not take a message. It has been working fairly > well for years now, except for the cases where on call had to be switched > (i.e. person on call suddenly can't perform the duty any more for whatever > reason) in the odd hours when there was no one in the office. > Yeah, we're supposed to also actually answer the call and take ownership of the issue, until we determine that it needs to go somewhere else (like to the DBA group or the ASA group).... The phone (and then phones) were set up with no voicemail. So, they could ring indefinitely if the caller waited.... My phone once rang for like 30 minutes, I on vacation and had forgotten to dial out.... After months of one person missing oncalls, and making excuses....like forgot to charge it, in a dead spot, etc. It came out that he didn't know how to dial into the oncall system.
There's a number we call, where you punch in a code and either # or * to be in or out. Well, it has to come from our desk phone (or a number that the system maps to our desk phone) Every so often the cell company turns voicemail service back on...and it messes up the HOT phone....because we don't know how to get into the voicemail service we're not supposed to have. Or it goes into the wrong person's voicemail. I think we gave up on having the cell company keep voicemail off, and each do something different to deal with it. Also, unless its me or my manager.... the person taking the call will probably not know how to handle the issue...and if it isn't the other senior admin....might not know how to figure out who should handle the issue.... He could probably benefit from some mentoring, as soon as he figures out he needs it. He lacks so much the basic foundation stuff.... IE: he can setup the ntp client, but if somebody tells him its not working right, he doesn't know how it works....to know what might be wrong. He closed out the ticket saying he set it up the say way as he's always done it....so it must be right. The generic ntp.conf only uses one NTP server. (and one of the pool members likes to become desynchronized regularly....working on me running the NTP servers...) etc. >> it worked, but not nearly as well as handing around a physical phone/pager. > > That means that person on call needs to carry two phones. Yuck. For several years I carried two phones. It was manageable at first....because my personal phone was a iphone, and work phone was small (krzr). Later work switched to a Droid 2 (so I tried making do with a small 'feature' phone).... Now I have my own Android phone (people were giving me a hardtime for buying my own Android apps, like Touchdown, for work phone)...and two smartphones in my pocket just doesn't work. Well, back when we had a shared phone....some of the people would forward it to their personal cell phone during the time. So, that's what I've done now..... We could certain go with no work cell phone....but the others are trying to get cell phone pay before they get a personal cell phone for work....and I don't want to rock that boat. Especially since they seem to think it could amount up to $100/month (taxable) added to their pay. One of the ASA's says he got a cheap unlocked phone off of ebay, and it only costs him $100/year for prepaid service....and its plenty of minutes. Which is about right...since I average in the single digits for my monthly work call usage. _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
