The other thing about transformations is that they are intended to apply to what is presented TO the device that they are configured on. You wouldn't apply a transform at a phone for digits it sends, you'd apply a transform at the phone for digits it is receiving.
Instead of this: 7965 > Called Party Transformation > Route Pattern > Gateway You need: 7965->Route Pattern->Called/Calling Party Transformation->Gateway. Think of them as the last-resort method for changing the number format as it will appear on the device the transform is configured on (context-specific is the word the docs use). If you need to format called party information for all calls a given phone makes (regardless of where it goes), use a translation pattern. If you need to format a number for all calls going out a specific gateway, use a transform mask, likewise if you need to format connected numbers for all calls going to a phone. -Ryan On May 29, 2014, at 8:32 AM, Matthew Loraditch <[email protected]<mailto:[email protected]>> wrote: What are you trying to have happen digit wise? I just started having a use for these and found out some confusing things about where they apply and how they match. For example, for a called party transform on a trunk, the matching pattern needs to match the digit string that went to the route pattern that ends up at the trunk, not how the digit string is when it hits the trunk. In my situation we are transitioning from MGCP gateways to CUBEs. For MGCP we strip pre-dot at the Route List level. However, in the Cubes we need the pre-dot to stay as we strip on the router. My transform on the trunk is 7.@ and then discard digits to none… even though in theory the route list has already stripped the 7… I don’t get the programming logic at all, but after bashing my head against a wall I found documentation that indicated this and darn if it doesn’t work. Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA 1965 Greenspring Drive Timonium, MD 21093 direct voice. 443.541.1518 fax. 410.252.9284 Twitter<http://twitter.com/heliontech> | Facebook<http://www.facebook.com/#!/pages/Helion/252157915296> | Website<http://www.heliontechnologies.com/> | Email Support<mailto:[email protected]?subject=Technical%20Support%20Request> Support Phone. 410.252.8830 From: cisco-voip [mailto:[email protected]] On Behalf Of Jason Aarons (AM) Sent: Thursday, May 29, 2014 8:10 AM To: cisco-voip ([email protected]<mailto:[email protected]>) Subject: [cisco-voip] CUCM 9.1 Called Party Transformation I recall you only apply a Called Party Transformation outbound at the Device > Gateway in CallManager 7.x You can’t apply a Called Party Transformation directly on the phone (that setting is for inbound only at the phone level). Has this changed in 9.1 or higher? I’m also using Standard Local Route Groups with 9.1.1 This is my goal, but I don’t think it is possible; 7965 > Called Party Transformation > Route Pattern > Gateway _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
