[cisco-voip] Local Route Groups without DID

[Damien Ball]

So I'm trying to use calling party transformation patterns to do the masking I need. I can't get the mask to apply though. I made sure Device Calling Party Transforms are allowed, and I've setup a calling party transform for 102X (my phone is 1023). The CSS I chose was System_LD (which is assigned to the phone and the Device Pool's Calling Party Transform CSS). Is there any step that i'm missing? 


----- Original Message ----- 
From: "Damien Ball" <balld at gcs.k12.nc.us> 
To: "Chris Ward" <chrward at cisco.com> 
Cc: cisco-voip at puck.nether.net 
Sent: Friday, May 1, 2009 11:39:41 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Local Route Groups without DID 


I didn't really want to manage them by this means. If i'm going to do that, I could just leave it setup the way it is. That would be easier. 

----- Original Message ----- 
From: "Chris Ward" <chrward at cisco.com> 
To: "Damien Ball" <balld at gcs.k12.nc.us> 
Cc: cisco-voip at puck.nether.net 
Sent: Friday, May 1, 2009 11:00:25 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Local Route Groups without DID 

Re: [cisco-voip] Local Route Groups without DID How about setting the external phone number mask on all the phones to the external number you want people to call back in on? Then on the single route pattern or local route group you can specify to use the external phone number mask? 

Chris Ward 


From: Damien Ball < balld at gcs.k12.nc.us > 
Date: Fri, 1 May 2009 10:52:26 -0400 (EDT) 
To: Chris Ward < chrward at cisco.com > 
Cc: < cisco-voip at puck.nether.net > 
Subject: Re: [cisco-voip] Local Route Groups without DID 

Yeah, I don't think that will work. From what I understand of local route groups, you can take advantage of having a single route list and a single set of route patterns. You define which route group to use in the device pool (this is specific to call manager 7). So, if i set the masking on the pattern, I still have the same problem of not being able to set multiple masks for different groups of phones easily. The only way I can see to do it is to set a mask on each individual phone. I don't want to do that. If this doesn't pan out, I'll have to go back to the traditional way of doing route groups. Any other suggestions? 


----- Original Message ----- 
From: "Chris Ward" < chrward at cisco.com > 
To: "Damien Ball" < balld at gcs.k12.nc.us >, cisco-voip at puck.nether.net 
Sent: Friday, May 1, 2009 10:44:48 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] Local Route Groups without DID 

Re: [cisco-voip] Local Route Groups without DID Hi Damien, 

It sounds like you want to be masking the calling party at the route pattern level with no modification at the route list level. I think I might not be understanding you exact scenario and goal, but that’s what it sounds like. 

Chris Ward 


From: Damien Ball < balld at gcs.k12.nc.us > 
Date: Fri, 1 May 2009 10:15:10 -0400 (EDT) 
To: < cisco-voip at puck.nether.net > 
Subject: [cisco-voip] Local Route Groups without DID 

I'm looking at using local route groups with my call system. I am currently masking the calling party information at the Route List. The reason for this is that I'm not mapping DIDs to individual phones, but I have all calls from a specific site masked as one telephone number (which dials back into the receptionist or UC call handler). If i'm using one global route list, is there a way to preserve this configuration or is it a lost cause? I'm using Call manager 7.0.2 and Unity Connection 7.0.2. I am routing these calls through 2 PRIs (each in different calling areas with different providers). 




_______________________________________________ 
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/20090504/f9a3d4ed/attachment.html>