[cisco-voip] Dealing with Exec Admins w/o IPMA

[Lelio Fulgenzi]

you can simulate IPMA without using it in this way. of course, you lose all the neat features, but as scott mentioned, things like i-divert are standard features in 4.1 now.

anyway, here's what we did. create the executive's phone as you ordinarily would, with their main/published DN as their primary line. they forward this primary line to their assistant's phone (doesn't matter what line really, personal preference really). create a secondary 'bypass' DN that exists in a partition that only the assistant can dial. you can also create a private, unpublished number that people can call the executive directly with and remind the exec never to make outbound calls with this line - you can also modify the CSS so they can't make outbound calls (I don't think we did this, but come to think of it would should have, perhaps use a CSS with a blank translation to nowhere so you immediately get busy signal when you lift up the handset...but I digress).

create the assistant phone with appearances of all the lines on the executive phone. yes, you are correct, get ready to buy some 7914s if your assistants help more than one executive. 

when a call comes in to the exec's published line it rings on the asst phone. the asst can see if the exec is on one of their lines and if not, transfer them to their 'bypass' line. remember, that the end result is that the caller will see the 'bypass' DN on their screen so it has to be in a different partition. you could swing it so that the published DN and the bypass DN are the same, there's no reason for number to call itself, so it should work out OK.

when the exec makes calls out on their phone, they should always be made from the published number. 

to handle the 'ringing' of the monitored lines on the assistant phones you can modify the ring setting to be flash only, beep, or like us, create a 'blank' ring file and have them assign it to that line.

it's not perfect by any stretch of the imagination, but it seems to work out. one of the sore spots is that assistants have to log into CCMuser pages to forward their exec's lines to voicemail, etc. 

you can also work out what restrictions (calling and forwarding) you want to put on the lines to make the solution work better for you. and in some cases you'll realize that you want to forward the forwarded calls to another assistant so the executive must forward their line to the assistant's primary line.

you also have to keep in mind RNA targets and making sure the call goes to the appropriate voicemail box. 

did i mention it wasn't perfect? ;)


  ----- Original Message ----- 
  From: IT 
  To: cisco-voip at puck.nether.net 
  Sent: Thursday, January 05, 2006 9:19 PM
  Subject: [cisco-voip] Dealing with Exec Admins w/o IPMA


  I guess this is a follow-up to my previous questions regarding IPMA vs. Attendant Console.

  It looks like AC is for receptionist, and my current dilemma are for all the executive assistants we have. Currently, we put the executives line (extension/directdial) on the assistant's phone as a shared line. The problem is, how can the asst transfer the call in to the exec, since they are already occupying the same line. For example a call comes in on 4950, the execs line, the asst picks up,  wants to transfer to 4950, but it rings on their own phone (as well as all the other assts who monitor 4950). So we usually end up with another asst answering the transfer.

  When we set up IPMA with multiple assistants, the other assistants line rang as well.

  So, here is the question. How can an assistant monitor multiple executives lines, and successfully transfer the call directly to the executive, without it ringing on other assistants phones.

  In addition, is there any way for the assistant to only be notified when the incoming call is from an outside line, but when someone internally direct dials the execs extension, it goes straight through?

  Please help.

  Thanks,

  Avidan

   

  ******************************************************
  This email may contain trade secrets and/or other information that is 
  proprietary and/or confidential. Use of this by anyone other than the 
  intended recipient(s) is prohibited and may be unlawful. If you are not 
  the intended recipient, delete the e-mail and notify us immediately.
  ****************************************************** 



------------------------------------------------------------------------------


  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060105/b93abbe8/attachment.html