

Restricted Call List? n Can Change Coverage? nĪccess to MCT? y Fully Restricted Service? n Restriction Override: none Facility Access Trunk Test? n Priority Queuing? n Direct Agent Calling? n Time of Day Chart: 1 Forced Entry of Account Codes? n Multimedia Mode: basic Audible Message Waiting? nīridged Appearance Origination Restriction? nĪbbreviated Dialing List Number (From above 1, 2 or 3):īlock Alerting if IP principal logged off? nĬOR Description: Originate (Calling Party Restrict)Ĭan Be Service Observed? n Calling Party Restriction: originationĬan Be A Service Observer? n Called Party Restriction: termination XMOBILE Type: EC500 Message Lamp Ext: 12002192009ĭisplay Module? y Message Waiting Type: ICONĭisplay Language: english Length of Display: 12x3īridged Call Alerting? y Distinctive Audible Alert? y Name: Block Number 26 Coverage Path 2: COS: 1 This is sytem wide however you can do it by trunk.Įxtension: 12002192009 Lock Messages? n BCC: 0 Then, you need to assign to this dummy XMOBILE station a COR with Calling Party Restriction: origination. The cellphone number will be the number you want to block calls from (12622070094 in this case) which can be any type of number, not only cellphone and the mapping mode "origination". Originally posted 19:23:00.Solution is to utilize EC500 to restrict a specific number from calling anyone in your CM system, adding a dummy XMOBILE station (12002192009 in this case). Now the calls from 99999 will be blocked when the call hits Cisco Unified Communication Manager. Route Option > Block this Pattern > Call Rejected.Description > 99999 is Being Blocked to Call to the Directory Numbers.Ensure Route Next Hop by Calling Party is UncheckedĬreate Translation Pattern > This Translation Pattern will block calls to the Directory Numbers.

Calling Search Space > Internal_CSS (Calling Search Space of IP Phones/Directory Numbers).Description > Filtered Translation Pattern.Check Mark > Route Next Hop By Calling PartyĬreate Translation Pattern > This Translation Pattern will route non blocking calls to the Directory Numbers.Description > Calls from Gateways or Trunks.Note : Ensure that Gateway CSS should not have any other Partitions that is being used by Directory Numbers, else the calls will be routed to the Directory Numbers.Īssign Gateway_CSS in Trunks and Gateways for Inbound CallsĬreate Translation Pattern > This Translation Pattern will match all the incoming calls from Gateways or Trunks Create a Partition named “Filter_PRT” and Create a CSS name “Filter_CSS”.This cmdlet also returns whether blocking has been Enabled (True or False). Get-CsTenantBlockedCallingNumbers returns the inbound block number patterns and the inbound exempt number patterns parameters for the global blocked number list. Create a Partition named “Gateway_PRT” and Create a CSS name “Gateway_CSS”. Viewing and activating the entire call blocking feature is managed through the Get-and Set-CsTenantBlockingCallingNumbers cmdlets.Login to Cisco Unified Communication Manager.To achieve this functionality, you need to follow the below steps –Ĭonfiguration in Cisco Unified Communication Manager: In Figure 2 – When “Route Next Hop By Calling Party Number” is applied, the calls are not being sent to the extension 10000 by Cisco Unified Communication Manager. Dial the number of the person youre trying to reach. In Figure 1 – When “Route Next Hop By Calling Party Number” is not applied, the calls are getting routed to extension 10000. Block your name and number only for the next call Dial 67 and wait for the three beeps. This feature works for all the protocols like MGCP, H323 and SIP as well.Ĭalling Party Number – 99999 (External PSTN) Block Incoming calls based on calling party number CUCMĪre you annoyed of unwanted calls? Trying to block incoming calls based on the Calling Party Number? Time to play with “Route Next Hop By Calling Party Number” which block calls based on calling party number.
