[cisco-voip] Calling Party Transformation Mask based on Device Pool

[Dan Letkeman]

Ok, that works, but I have to assign the route list to the route
pattern.  So this means I have to create a new route pattern for every
site.  And we plan on adding 10-15 more sites in the next 12 months.
Seems like a lot of extra work.

Any other ideas?
Dan.

On Tue, Oct 19, 2010 at 12:51 PM, Mark Lee (US) <mark.lee at us.didata.com> wrote:
> Create route groups for each site and assign caller ID for each site within the route group once it is assigned to a route list.  This is done within the Route list, select the route group and then assign the caller ID.
>
> Mark Lee
> Dimension Data
> Managing Technical Consultant
> National L3 Team
> 972-322-7274 (c)
> 972-212-7293 (f)
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Dan Letkeman
> Sent: Tuesday, October 19, 2010 1:45 PM
> To: cisco-voip
> Subject: [cisco-voip] Calling Party Transformation Mask based on Device Pool
>
> Hello,
>
> Is there a way to assign a different caller id to each of my remote
> offices?  I have device pools for each of them already and I was
> wondering if I can somehow assign a calling party transformation
> pattern to the device pool using CSS and Partitions?
>
> Or is there better way to accomplish this?
>
> Thanks,
> Dan.
> _______________________________________________
> 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.
>