09-09-2015 08:47 PM - edited 03-17-2019 04:15 AM
Hi, All
Our company's communication router is CISCO 3800, I want to implement the following function on one certain phone number:
1. This phone number can dial and receive any internal extension No.
2. This phone number can receive any external phone No.
3. This phone number can't dial any external phone No.
How to implement it ? Thank You!
09-09-2015 09:37 PM
09-09-2015 10:10 PM
I‘m not very familar with that system, not understand all your means, but I could give the example,
Our client phone number is 6312, phone type CISCO 6921,now I should restrict the function on his phone, just receive and dial internal number, only receive external phone ,but not dial any external phone, how to do it ? Thank You!
09-10-2015 03:03 AM
Can you share your running config. We can then suggest you the desired modifications.
09-10-2015 07:01 AM
09-10-2015 11:47 AM
09-11-2015 02:08 AM
Why add name executive, what your means there have 2 groups, "cor list allowed" and "cor list restrict" , for ephone-dn 12, it should add "cor list restrict" group ? is it right ? for other ephone configuration, it should add "cor list allowed" group ?
09-11-2015 02:29 AM
Don't take the names seriously. These are just tags.
If the COR applied on an incoming dial-peer (for incoming calls) is a super set or equal to the COR applied to theoutgoing dial-peer (for outgoing calls), the call goes through. Incoming and outgoing are terms used with respect to the "voice ports". COR is often described as a lock and key mechanism. Locks are assigned to dial peers with an outgoing COR list. Keys are assigned to dial peers with an incoming COR list.
Simply when you want to restrict dial-peer access to certain DN, you need to apply corlist first to DN (towards incoming dial-peer) and then to outbound POTS dial-peers.
Now DN can access the outbound dial-peer only if corlist on DN is the superset of corlist under outbound dial-peer. Make sense?
Also note that if corlist is not applied to DN or dial-peers, they don't involve in corlist restrictions and selectable by anyone.
Coming back to your case, when we apply corlist incoming restrict to DN (inbound dial-peer) and 'corlist outgoing allowed' to all outbound dial-peers, that respective DN won't be able to make any external call since corlist incoming is not the superset of outbound cor list (incoming corlist restrict only includes security tag whereas outgoing corlist on outbound dial-peers include both security and executive tag).
Now you don't need to apply corlist to any other DN which you don't want to restrict for making PSTN calls. As I mentioned before, when corlist is not applied either to inbound or outbound dial-peer, that call doesn't qualify for corlist restriction.
At the end, apply 'corlist incoming restrict' to only those DN which you want to restrict from making PSTN calls. Don't apply corlist to DN which you don't want to restrict. Apply 'corlist outgoing allowed' to all outbound POTS dial-peers and 'corlist incoming allowed' to inbound POTS dial-peer.
I will suggest you to go through following document to get over the corlist concept;
http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/42720-configuring-cor.html
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide