CUCM 11.5 - Routing calls using source number or partition

[OakMan]

Hello,

I have a CUCM 11.5 and would like my internal source calls (extensions 85XX) ring directly to my extension (8510) and the other external type sources would ring directly to another extension (8500), how can I implement this in CUCM? is possible?

Regards,

OakMan.

[Maren Mahoney]

I can see a way to do this, but it will be complicated. There is a "Route Next Hop by Calling Party Number" field in translation patterns. It would be a variation on blocking/rerouting incoming calls based on caller-id. Here is a link to that:

https://supportforums.cisco.com/t5/collaboration-voice-and-video/blocking-calls-based-on-calling-party-id/ta-p/3113978

So you could create a translation pattern for your extension with RNHbCP checked. And have the CSS for that TP have access to a partition that has a pair of translation patterns - one for the direct-to-you extensions and another for the redirected extensions - and each of the two would have a different called-party-mask for which destination you want the call to take.

I don't even want to think about the affect this will have on CDRs, rolling to voicemail, etc. But it could be done.

Another way to do this would be to have all calls to your extension roll to Unity Connection. Then have Personal Call Routing Rules that path the calls back to CUCM with different dialed numbers based on caller-id. Again, unknown but probably problematic issues with call accounting and even caller ID.

Unless someone else can think of something brilliant, I see two ways to do what you are asking that are both icky.

[Jaime Valencia]

If you simply want people who dial internally 8510 to reach out to you directly, but people whose call comes from PSTN to dial 8510 and translate to 8500, simply configure a TP in a partition with a higher preference in the inbound CSS and that will do the trick.