[cisco-voip] Unity Connection 7 Call Handlers based on Called Number

[Pat Hayes]

The inherited search space that the call handler picks up from the
routing rules in the config that Lelio describes only governs what
extensions the user can enter directly, it doesn't impact the
caller-input config.

If you just need to do this for an operator, that will work, just
configure multiple users with the extension '0' and put them in
separate partitions. If there are multiple inputs that you need to go
to site specific locations, that doesn't really scale, you would be
much better off just making copies of the call handler with the
appropriate extensions and setting up the caller input. No need for
routing rules, search spaces, or partitions.

On Wed, Nov 4, 2009 at 2:33 PM, O'Brien, Neil <nobrien at datapac.com> wrote:
> Thanks for the info, I kinda figured I’d have to do some reading, now I know
> what I have to read!!
>
>
>
> Thanks again..........
>
>
>
> Regards,
>
>
>
> Neil O'Brien
>
> Network Engineer
>
>
>
> Datapac Ltd
>
> Phone: +353 1 426 3500
>
> Fax:    +353 1 426 3501
>
> Email:  nobrien at datapac.com
>
> Web:   www.datapac.com
>
>
>
>
>
>
>
> Datapac is the leading Irish business technologies provider
>
> IT Maintenance & Managed Services | Virtualisation & Storage Solutions |
> Microsoft Infrastructure Solutions
>
> Voice & Data Networks | Unified Communications | Microsoft Dynamics Nav ERP
> | EPOS Retail Solutions | IT Consumables
>
>
>
> From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
> Sent: 04 November 2009 19:30
> To: O'Brien, Neil
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Unity Connection 7 Call Handlers based on Called
> Number
>
>
>
> This is what routing rules and search spaces are used for. It's a bit
> complicated to answer in email, but basically, if you create a routing rule
> for each called number and assign it a particular search space then route it
> to a call handler, the call handler is set to "inherit" the search space.
> Then when it dials "0", it will dial the appropriate "0" based on the search
> space.
>
> It takes some time to get your head around it, but it should work.
>
> I would read up on the routing rules and search space documentation. I had
> to read it more than once. ;)
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "Bad grammar makes me [sic]" - Tshirt
>
>
> ----- Original Message -----
> From: "Neil O'Brien" <nobrien at datapac.com>
> To: cisco-voip at puck.nether.net
> Sent: Wednesday, November 4, 2009 2:22:41 PM GMT -05:00 US/Canada Eastern
> Subject: [cisco-voip] Unity Connection 7 Call Handlers based on Called
> Number
>
>
> Hi,
>
>
>
>
>
> We have Unity Connection 7 and have multiple geographically disparate
> sites.  We have a requirement for a single call handler with various options
> but the numbers these options ring will differ based on the called number.
>
>
>
> So for example, if Ben calls 555 1234 which is Remote Site A, it goes
> through to the central call handler in HQ.  Ben selects Option 1 is to speak
> to a reception.  It needs to go through to the reception of the office he
> dialled.  If Jerry calls 907 1234 for Remote Site B, it goes through to the
> same call hander and Jerry selects Option 1 to speak to reception, it needs
> to go through to the reception of the office he called.
>
>
>
> I am very unfamiliar with Unity Connection so I’d appreciate some guidance.
>
>
>
> Thanks in advance,
>
>
>
> Neil
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>