<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Verdana","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Verdana","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-IE link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>Thanks Pat,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I think this is what Lelio was explaining - Multiple
"operators" with a 0 extension just in separate partitions only
accessible from the partition the caller comes in on, I understand that from a
CallManager perspective.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>I think it's just for one particular extension (operator)
however I had thought about separate call handlers but 1 handler for each site
(9) seems a bit OTT, but thanks for the suggestion.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>On a separate note, if neither of you mind. If I'm
creating a complete AutoAttendant within Unity - "<i>Welcome to Acme &
Co, Please Press 1 for Sales, 2 for Tech Support.....etc”. </i>Then
if you press 2 for Tech Support, you get 2 further options like “<i>Press
1 for Cisco VoIP, Press 2 for Cisco Routing and Switching.....”. </i>You
get the idea. Do I need completely separate call handlers for each “announcement”
and link them together?? So I would have a “Welcome” call
handler which the caller hears first, then another call handler called “Tech
Support” which announces the tech support options. Forgive my lack
of understanding but am I on the right track??<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Just wondering from a best practices approach, if you had
multiple handlers for different auto attendants, is there a recommended naming
convention or format that would allow someone to look at the list of call
handlers and see what links to what?? Or is it just a matter of
drilling into each one to find out what it’s linked to. Obviously
proper documentation is what you’d firstly recommend but I thought there
might be a real-world way. I was thinking prefixing the name of each separate
AA with a 3 digit code say 101, the first 1 (on the left) identifying the AA,
the middle digit identifying the tier within the AA and the other 1
(right) identifying the message within that tier. So if I had 3 seperate
AA’s for 3 seperate busineses, the welcome message for each AA would have
codes 101 - Welcome, 201 - Welcome and 301 - Welcome. If we take the 101 –
Welcome, and it says “<i>Press 1 for Sales, 2 for Tech Support, 3 for
Stores”. </i>Then I have 3 further call handlers announcing the
different options for Sales, Tech Support and Stores. I would call these
111 – Sales, 112 – Tech Support, 113 Stores. <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Sorry for the rant, but it seems to me that unless you
have a proper structure to it, it could very easily and very quickly get out of
control.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks for taking the time to read!!<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Thanks again,<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Neil<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Regards,<o:p></o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText>Neil O'Brien<o:p></o:p></p>
<p class=MsoPlainText>Network Engineer<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Datapac Ltd<o:p></o:p></p>
<p class=MsoPlainText>Phone: +353 1 426 3500<o:p></o:p></p>
<p class=MsoPlainText>Fax: +353 1 426 3501<o:p></o:p></p>
<p class=MsoPlainText>Email: nobrien@datapac.com<o:p></o:p></p>
<p class=MsoPlainText>Web: www.datapac.com<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Datapac is the leading Irish business technologies
provider<o:p></o:p></p>
<p class=MsoPlainText>IT Maintenance & Managed Services | Virtualisation
& Storage Solutions | Microsoft Infrastructure Solutions <o:p></o:p></p>
<p class=MsoPlainText>Voice & Data Networks | Unified Communications |
Microsoft Dynamics Nav ERP | EPOS Retail Solutions | IT Consumables<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><span lang=EN-US>-----Original Message-----<br>
From: pat@wcyv.com [mailto:pat@wcyv.com] On Behalf Of Pat Hayes<br>
Sent: 04 November 2009 22:39<br>
To: O'Brien, Neil<br>
Cc: Lelio Fulgenzi; cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] Unity Connection 7 Call Handlers based on Called
Number</span></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The inherited search space that the call handler picks up
from the<o:p></o:p></p>
<p class=MsoPlainText>routing rules in the config that Lelio describes only
governs what<o:p></o:p></p>
<p class=MsoPlainText>extensions the user can enter directly, it doesn't impact
the<o:p></o:p></p>
<p class=MsoPlainText>caller-input config.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>If you just need to do this for an operator, that will
work, just<o:p></o:p></p>
<p class=MsoPlainText>configure multiple users with the extension '0' and put
them in<o:p></o:p></p>
<p class=MsoPlainText>separate partitions. If there are multiple inputs that
you need to go<o:p></o:p></p>
<p class=MsoPlainText>to site specific locations, that doesn't really scale,
you would be<o:p></o:p></p>
<p class=MsoPlainText>much better off just making copies of the call handler
with the<o:p></o:p></p>
<p class=MsoPlainText>appropriate extensions and setting up the caller input.
No need for<o:p></o:p></p>
<p class=MsoPlainText>routing rules, search spaces, or partitions.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>On Wed, Nov 4, 2009 at 2:33 PM, O'Brien, Neil
<nobrien@datapac.com> wrote:<o:p></o:p></p>
<p class=MsoPlainText>> Thanks for the info, I kinda figured I’d have
to do some reading, now I know<o:p></o:p></p>
<p class=MsoPlainText>> what I have to read!!<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Thanks again..........<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Regards,<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Neil O'Brien<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Network Engineer<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Datapac Ltd<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Phone: +353 1 426 3500<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Fax: +353 1 426 3501<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Email: nobrien@datapac.com<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Web: www.datapac.com<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Datapac is the leading Irish business technologies
provider<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> IT Maintenance & Managed Services |
Virtualisation & Storage Solutions |<o:p></o:p></p>
<p class=MsoPlainText>> Microsoft Infrastructure Solutions<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Voice & Data Networks | Unified Communications |
Microsoft Dynamics Nav ERP<o:p></o:p></p>
<p class=MsoPlainText>> | EPOS Retail Solutions | IT Consumables<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> From: Lelio Fulgenzi [mailto:lelio@uoguelph.ca]<o:p></o:p></p>
<p class=MsoPlainText>> Sent: 04 November 2009 19:30<o:p></o:p></p>
<p class=MsoPlainText>> To: O'Brien, Neil<o:p></o:p></p>
<p class=MsoPlainText>> Cc: cisco-voip@puck.nether.net<o:p></o:p></p>
<p class=MsoPlainText>> Subject: Re: [cisco-voip] Unity Connection 7 Call
Handlers based on Called<o:p></o:p></p>
<p class=MsoPlainText>> Number<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> This is what routing rules and search spaces are
used for. It's a bit<o:p></o:p></p>
<p class=MsoPlainText>> complicated to answer in email, but basically, if
you create a routing rule<o:p></o:p></p>
<p class=MsoPlainText>> for each called number and assign it a particular
search space then route it<o:p></o:p></p>
<p class=MsoPlainText>> to a call handler, the call handler is set to
"inherit" the search space.<o:p></o:p></p>
<p class=MsoPlainText>> Then when it dials "0", it will dial the
appropriate "0" based on the search<o:p></o:p></p>
<p class=MsoPlainText>> space.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> It takes some time to get your head around it, but
it should work.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> I would read up on the routing rules and search
space documentation. I had<o:p></o:p></p>
<p class=MsoPlainText>> to read it more than once. ;)<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> ---<o:p></o:p></p>
<p class=MsoPlainText>> Lelio Fulgenzi, B.A.<o:p></o:p></p>
<p class=MsoPlainText>> Senior Analyst (CCS) * University of Guelph *
Guelph, Ontario N1G 2W1<o:p></o:p></p>
<p class=MsoPlainText>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<o:p></o:p></p>
<p class=MsoPlainText>>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<o:p></o:p></p>
<p class=MsoPlainText>> "Bad grammar makes me [sic]" - Tshirt<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> ----- Original Message -----<o:p></o:p></p>
<p class=MsoPlainText>> From: "Neil O'Brien"
<nobrien@datapac.com><o:p></o:p></p>
<p class=MsoPlainText>> To: cisco-voip@puck.nether.net<o:p></o:p></p>
<p class=MsoPlainText>> Sent: Wednesday, November 4, 2009 2:22:41 PM GMT
-05:00 US/Canada Eastern<o:p></o:p></p>
<p class=MsoPlainText>> Subject: [cisco-voip] Unity Connection 7 Call
Handlers based on Called<o:p></o:p></p>
<p class=MsoPlainText>> Number<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Hi,<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> We have Unity Connection 7 and have multiple
geographically disparate<o:p></o:p></p>
<p class=MsoPlainText>> sites. We have a requirement for a single call
handler with various options<o:p></o:p></p>
<p class=MsoPlainText>> but the numbers these options ring will differ based
on the called number.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> So for example, if Ben calls 555 1234 which is
Remote Site A, it goes<o:p></o:p></p>
<p class=MsoPlainText>> through to the central call handler in HQ. Ben
selects Option 1 is to speak<o:p></o:p></p>
<p class=MsoPlainText>> to a reception. It needs to go through to the
reception of the office he<o:p></o:p></p>
<p class=MsoPlainText>> dialled. If Jerry calls 907 1234 for Remote
Site B, it goes through to the<o:p></o:p></p>
<p class=MsoPlainText>> same call hander and Jerry selects Option 1 to speak
to reception, it needs<o:p></o:p></p>
<p class=MsoPlainText>> to go through to the reception of the office he
called.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> I am very unfamiliar with Unity Connection so
I’d appreciate some guidance.<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Thanks in advance,<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> Neil<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> _______________________________________________
cisco-voip mailing list<o:p></o:p></p>
<p class=MsoPlainText>> cisco-voip@puck.nether.net<o:p></o:p></p>
<p class=MsoPlainText>> https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>> _______________________________________________<o:p></o:p></p>
<p class=MsoPlainText>> cisco-voip mailing list<o:p></o:p></p>
<p class=MsoPlainText>> cisco-voip@puck.nether.net<o:p></o:p></p>
<p class=MsoPlainText>> https://puck.nether.net/mailman/listinfo/cisco-voip<o:p></o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
<p class=MsoPlainText>><o:p> </o:p></p>
</div>
</body>
</html>