We’ve all done this. You are sitting in front of your PC working on a project and realize that you need some important information from a coworker. Let’s call that coworker Deborah Olson. You click over to Microsoft Lync, find Deborah in your contacts list, and see that her presence jellybean shows her to be available.
What do you do next? Do you pick up the phone and call Deborah? No, you send her an instant message that looks similar to the following:
“Hi, Deborah. Are you busy? May I call you?”
So, what exactly did Deborah’s jellybean tell you? Clearly, not enough. Even though it indicated that she was available, her presence icon isn’t the green light (pardon the pun) that it should be. It didn’t say, “I am here and waiting to take your call.” Alas, available is nearly always second guessed as “I need to ask just to make sure available really means available.”
In my latest article for No Jitter, I ask the question, “Is presence stupid.” I also challenge my readers to come up with ideas on how to make it smarter and more relevant to the way we actually do business.
Tao, Zen, and Tomorrow 
I like the idea of varying degrees of the “Available” status itself. For an example; solid green could obviously mean you are free and available to talk. Then green with a yellow band through it, maybe indicating you are free to chat but you are also working on something. And then maybe a green status with a red band meaning you will be available momentarily.
Thanks, Jim. I know that some people do something similar with manual settings and status messages (e.g. “On the phone, but open to IM”). However, that doesn’t change the presence icon coloring. I like your idea!
HI Andrew,
First of all, i am really sorry for write this in reply…. But i dont have a choice bcz for me all mails are blocked.. but i could not resolve this issue.
the issue is , we are using Minisip server for testing purpose… our set up is
MSS (Stun)==> Vuatta Router(NAT)==> MSS
we need to make a call from one SIP ac from MSS to another SIP account in the same MSS via Vyatta Router… we have tried the same got succeed little bit, like calls are connecting internally (MSS to MSS), when we are making calls from MSS to MSS via Vyatta router calls are not connecting.
Vyatta Router configuration:-
configure
set interfaces ethernet eth0 address 192.168.5.21/26
set service ssh
set nat source rule 10 source address ‘192.168.5.0/26’
set nat source rule 10 outbound-interface ‘eth0’
set nat source rule 10 protocol ‘all’
set nat source rule 10 translation address ‘masquerade’
set protocols static route 0.0.0.0/0 next-hop 192.168.5.24 distance ‘1’
commit
save
pls help me out…
PS I dont know who else to ask this …
Thanks in advance.
I wish I could help, but nothing in what you said jumps out at me as your problem. This is the kind of problem that needs to be debugged in person. Sorry. 😦
ok… No problem…. 🙂