[cisco-voip] Attendant Console, SRST, hunt pilots

[Matt Slaga (US)]

You've got your tasks pretty much right.

For SRST, use the "Alias" command to send the calls to the receptionists
number.



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert
Kulagowski
Sent: Tuesday, October 03, 2006 2:01 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Attendant Console, SRST, hunt pilots

We have a six digit dial plan, where the first two digits are the site 
ID, and the last four are the DID.

On the voice gateway at a remote site, we use translation profiles to 
take the incoming DID (our providers send 4 digits) and prefix the site 
code.

The receptionist has the main number for the site (6 digit DN) as the 
first line appearance.

I currently have a TAC case open because AC users aren't seeing call 
park details in AC when they park a call - they get a screen pop telling

them the park number, and it says it on their phone, but the AC 
application never shows it in the Parked Calls window.  The TAC engineer

says that it's because we're not using pilot points and hunt groups, and

that's the first thing to fix.  Assuming that I have to implement pilot 
points and hunt groups for all of this to work, would it be something
like:

1)  Remove existing main number DN from receptionist phone.
2)  Create a pilot point with the six digit main number for the site.
3)  Create a line appearance on the reception phone (doesn't have to be 
a DID)
4)  Create a hunt group for the pilot point DN whose members are the AC 
user for the site + pilot number for our VM.

What do I do for SRST mode though?  Some other set of translation 
patterns that only apply in fallback mode to take the main number and 
have it ring on the newly-created non-DID?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.