[cisco-voip] passing calling search space through intercluster trunks

[Lelio Fulgenzi]

Thanks Mark. Someone mentioned this a while back with router based gateways and I didn't put the two together. It's not exactly what I want, but it might be able to do the job. Thanks, Lelio

Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo."      WJR

  ----- Original Message ----- 
  From: Mark Noble 
  To: Wes Sisk ; Lelio Fulgenzi 
  Cc: cisco-voip at puck.nether.net 
  Sent: Monday, February 11, 2008 2:21 PM
  Subject: RE: [cisco-voip] passing calling search space through intercluster trunks


  you will need more that a simple 9.@ patterns, but  you could create 'tags' similar to MPLS, where when you pass a number across a trunk that has a particular CSS you assign a prefix on the route-pattern or group that it went out on, and on the inbound CCM you pass all inbound calls through a set of translation pattern that based on the prefix will allow the called number pass through a certain CSS

   

  e.g.

   

  outbound CCM

  user dials             prefix                    result    

   

  1234                       88                           881234

  5678                       89                           895678

   

   

   

  on 

   

  the inbound CCM you have a set of translation patterns, the inbound trunk has a CSS that contains all the translation patterns you wish 

   

  translation patterns                        ptn                         css                          

  88XXXX                                                 CCM1-in               88number

  89XXXX                                                 CCM1-in               89numbers

   

  then use one of the called party transformation settings to strip the number back to what you want it to be and remove the prefix

   

  I have used this method on very large deployments where there are multiple clusters, lots of gatekeepers and PGW's etc, and it works well, you just need to plan it and test it. 

   

   

   

  -mark

   

  From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
  Sent: 11 February 2008 18:15
  To: Lelio Fulgenzi
  Cc: cisco-voip at puck.nether.net
  Subject: Re: [cisco-voip] passing calling search space through intercluster trunks

   

  Nothing similar released so far.  There *may* be some similarities forthcoming but you'd need to check with your favorite PM's or account team.

  /Wes

  Lelio Fulgenzi wrote: 

  Something we were able to do on our old pbx is to match class of service across trunks, so basically we were able to map one class of service to another and have some flexibility in passing permissions across from one system to another. 

   

  Is there any way to do this with two callmanager clusters? I'd like to be able to add a simple 9.@ route pattern on one cluster and have that users class of service cross the trunk and have the final cluster deny/allow the call.

  --------------------------------------------------------------------------------
  Lelio Fulgenzi, B.A.
  Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
  (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
  "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo."      WJR

 
------------------------------------------------------------------------------

 _______________________________________________cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip  Notice: The information transmitted in this e-mail message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080211/b067bafd/attachment-0001.html