Sure there is. In the inbound CSS used on the gateway or trunk put a specific partition in it and in that partition create a translation pattern that matches the entire DID or whatever short digit range that you have and translate the called number to the predefined number. The important thing is to not give visibility to that partition to internal callers, it should only be visible in the CSS used inbound from the trunk or gateway.
The key thing to have in mind here is that this works because CM does a best match and that means that any call coming in to a used directory number will be a better match than the translation pattern that matches the entire DID range.
Why would you put the translation pattern in the same partition as the directory numbers?
Absolutely the outbound CSS of the translation would have visibility of the partition where the directory numbers are, but that said if the DNs are in a short format I would assume that the match of the translation would be in the same format and also the translated output called number, ie short on both. That’s why I don’t think it would make sense to have the translation in the same partition as the DNs. That is if you’re not suggesting to use dual layer of translations? That would however IMHO be an unnecessary step.
I’ve read your response again and now I see what you meant. You’re not doing the translation of called numbers to the short number format on the gateway, but with a translation in CM. With that what you wrote makes sense. Personally I’m a big believer in transforming the called and for the matter calling numbers at the closest possible place to the source, ie in the gateway. Mostly because this can then be used by many different use cases, such as SRST or for normal call routing in CM. Just my 2 cents on this. Preferences differ and there’s no one right way to do things.
