[cisco-voip] MWI and Multi -Tenanting

Tue Apr 18 11:25:56 EDT 2006

I have to agree with Tim.  I've been in a multi-tenant CCM setup and 10
digits is the only way to go.  Otherwise you'll end up pulling your hair
out.

-The phone DN's should be 10 digits.
-Each customer should have their own Partition and CSS.
-Each customer can have their own translation pattern (in their own
Partition) that can translate four digits to 10 to effectively provide 4 (or
3 or 5) digit dialing to the customer.

All telco's should be capable of sending 10 digits.  It might take some
digging.  If the sales or customer service give you problems tell them you
want to speak with Translations.

Of course, it can get a little more complicated and SRND might suggest other
methods but this has worked very well in my opinion.

The only problem with this is that Unity doesn't have partitions so Unity
voicemail is not multi-tenant friendly.  Unless something has changed in the
newer Unity versions.

Justin

On 4/18/06, Tim Medley <medley at mac.com> wrote:
>
> In large/complex and/or multi-tenant deployments I typically ask the telco
> to send me all 10 digits. This makes it very easy for me to control what
> digits get sent to CCM.
>
> It's not always possible, since some telco's get pissy/confused/arrogant
> when you ask for something slightly outside of normal, but usually with a
> few escalated calls you can get what you want. I'm not a control freak, but
> I find it is vastly easier for me to control the digits I pass from the
> gateway to the CCM or other service instead of having the telco just send me
> what they want.
>
>
> tm
>
>
>
>  Tim Medley
> medley at mac.com
>
>
>
>
>  On Apr 18, 2006, at 12:49 AM, Wydra, Jason wrote:
>
>  Good point, but if telco only sends the last 4 digits then you're hands
> are tied. EXAMPLE:
>
>
>
> 357-4600
>
> 542-4600
>
>
>
> Telco only sends four digits……. Nothing you can do on the gateway or CCM
> as far as I know.
>
>
>
> *Jason Wydra*
>
> *Consultant*
>
> *burwood* *group, inc.*
>
> *Phone: (312) 327-4677*
>
> *Cell: (312) 493-2834*
>
> jwydra at burwood.com
>
>
>
>
>  ------------------------------
>
> *From:* Craig M Staffin [mailto:CMStaffin at ra.rockwell.com<CMStaffin at ra.rockwell.com>]
>
> *Sent:* Monday, April 17, 2006 11:46 PM
> *To:* Wydra, Jason
> *Cc:* cisco-voip at puck.nether.net; cisco-voip-bounces at puck.nether.net;
> Darren Smith; Tim Medley
> *Subject:* Re: [cisco-voip] MWI and Multi -Tenanting
>
>
>
>
> or better yet change it at the gateway and CCM is none the wiser.
>
> We do all of our digit manipulation at the gateway level.
>
> I agree with you a solid dial plan solves so many problems
>
>
>
>
>
>
> *"Wydra, Jason" <jwydra at Burwood.com>*
> Sent by: cisco-voip-bounces at puck.nether.net
>
> 04/17/2006 11:38 PM
>
>
>         To:        "Tim Medley" <medley at mac.com>, "Darren Smith" <
> darren at silvercommunities.com.au>
>         cc:        cisco-voip at puck.nether.net
>         Subject:        Re: [cisco-voip] MWI and Multi -Tenanting
>
>
>
>
> Forgive my idiotic question and somewhat asinine comment but…… Why do so
> many providers of IPT CCM service feel like they need to overlap
> multi-tenant extensions? Are there not enough numbers??? Do we have an issue
> like we sort-of have between IPV4 and IPV6. I doubt it…. Easy solution is
> don't overlap dialplans by having a solid design from the get go. If you
> have the same last four digits in the DID range then just call telco and
> have them send 7 digits instead of four.
>
> *Jason Wydra*
> *Consultant*
> *burwood* *group, inc.*
> *Phone: (312) 327-4677*
> *Cell: (312) 493-2834*
> jwydra at burwood.com
>
>
>
>
>  ------------------------------
>
>
> *From:* cisco-voip-bounces at puck.nether.net [
> mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Tim Medley*
> Sent:* Monday, April 17, 2006 11:16 PM*
> To:* Darren Smith*
> Cc:* cisco-voip at puck.nether.net*
> Subject:* Re: [cisco-voip] MWI and Multi -Tenanting
>
> Darren,
>
> I've setup multi-tenant CCM systems several times.  A couple of questions.
>
>
> How do you have the MWI on/off DN's configured in CCM? Are they in the
> same generic partition that your phone DN's are in? You will need to set the
> MWI on/off numbers to a partition that all tenants have access to AND the
> CSS that the Unity port(s) that are set for MWI will need access to the
> Tenant Partitions.
>
> tm
>
> Tim Medley
> medley at mac.com
>
>
>
>
> On Apr 18, 2006, at 12:05 AM, Darren Smith wrote:
>
> Hi,
>
> Has anybody succesfully implemented MWI with multi tenanting on CCM 4.1.3and Unity
> 4.0.5??
>
> We have multiple customers on our callmanager and unity platform, some of
> these are smaller business, ad each of these has their own Partitions, and
> each of these partitions use the same DN range (eg 200x).
>
> Other customers are in a generic partition, and their DN is their full DDI
> number.
>
> We have set the MWI numbers (Full 10 digit numbers), but cannot get MWI to
> work.
> The option for multi tenanting is set to turue within Callmanager
> Messaging Interfaces services, but I'm sure I need some transaltion patterns
> set, but can't work out what to do.
>
> Thanks in advance
>
> Regards
>
> *Darren Smith*
> Chief Operations Officer*
> Silver Communities*
>
> P 1300786755
> D 0756575299
> M 0405 847791
> E darren at silvercommunities.com.au
>
>
>
>
>
>
>
>
>
>
>  ------------------------------
>
>
> DISCLAIMER: This email, together with any attachments, is intended for the
> named recipient(s) only; and may contain privileged and confidential
> information. If received in error, you are asked to inform the sender as
> quickly as possible and delete this email and any copies of this from your
> computer system network.
> If not an intended recipient of this email, you must not copy, distribute
> or take any action(s) that relies on it; any form of disclosure,
> modification, distribution and /or publication of this email is also
> prohibited.
> Unless stated otherwise, this email represents only the views of the
> sender and not the views of Silver Communities Pty Ltd.
>
> _______________________________________________
> 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
>
>
>
>
> _______________________________________________
> 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/20060418/2228ddac/attachment-0001.html 