cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
915
Views
0
Helpful
4
Replies

DN to DN Call Blocking

angel-moon
Level 3
Level 3

Hello everyone,

 

 

I know the obvious answer involves CSS and partitions BUT on a VG if I have several lines that have to stay in the same CSS and partition is there a way to block calls between these extensions but still allowing  inbound/outbound calls as well as internal calls to all other DNs.  CM 10.5

 

 

Thanks in advance!

1 Accepted Solution

Accepted Solutions

What protocol is used to control these analog ports in CUCM? If it's SCCP or MGCP you control each port individually, thus can change the CSS per device/line, if these are controlled by SIP or H323 then you only have a trunk/GW pointing to/from the analog GW and thus single CSS is used for all ports on the GW.  

In any case you can control the partition separately for each port as for H323/SIP you can create separate route patterns in different partition and thus allow/disallow dialing that number, SCCP/MGCP DNs are just like any other phone DNs and partitions are assigned to the DN at the phone level.

View solution in original post

4 Replies 4

Chris Deren
Hall of Fame
Hall of Fame

All of it is possible with proper configuration of CSS/Partition as you point out.  When you stay that partitions and CSSes need to stay as they are then your hands are tied and the only option would be to potentially introduce other overlapping patterns with the exact same number in higher priority partition, and then ensure that PT is listed before the existing PT in every device/GW/etc CSS.  Just re-design your CSSes/PTs to your requirements and apply to your ports.

As Chris wrote you can setup matching patterns with the exact same match part as the DNs that the VG has on the ports in a PT that is ordered higher in the CSS. On these set them to block the call.

 

For example if you have DNs 2001 and 2002 create two TPs with match 2001 and 2002 and set the action on them to block the call. Put the TPs in a PT specifically created to hold the block patterns and add this PT into the CSS above the PT that holds the directory numbers. Worth to mention is that you would need to create a separate CSS for use on your VG ports, if other DNs should be able to call to the VG DNs. If that's not the case then you can use the same CSS as for other devices.

 



Response Signature


TONY SMITH
Spotlight
Spotlight

@angel-moon wrote:

on a VG if I have several lines that have to stay in the same CSS and partition is there a way to block calls between these extensions but still allowing  inbound/outbound calls as well as internal calls to all other DNs.  CM 10.5


Could you clarify why these lines have to be in the same partition, and have the same CSS?   There may be another solution if we understand where that requirement comes from.   I assume you could change the CSS, so long as the changed CSS applies to all these lines, again maybe you could confirm.

To give different DNs different calling permissions, while sharing the same CSS you might be able to lash something up using "Route Next Hop By Calling Party" option, but I think it would be quite fiddly to set up and administer.  Or understand.
Route Next Hop By Calling Party Number

What protocol is used to control these analog ports in CUCM? If it's SCCP or MGCP you control each port individually, thus can change the CSS per device/line, if these are controlled by SIP or H323 then you only have a trunk/GW pointing to/from the analog GW and thus single CSS is used for all ports on the GW.  

In any case you can control the partition separately for each port as for H323/SIP you can create separate route patterns in different partition and thus allow/disallow dialing that number, SCCP/MGCP DNs are just like any other phone DNs and partitions are assigned to the DN at the phone level.