This article demonstrates how to use the COR feature to establish classes of service.
We have two phones at HQ site: x1000 and x1003. x1000 is a manager. x1003 is a security guard. Obviously, we will assign the national PSTN access to the manager and restrict the security guard access.
In the topology below, I left only what is relevent to the experiment.
The steps required are:
- check which dial peers will be concerned by the COR feature
- configure the COR names
- configure COR lists according to our class of services
- assign COR lists to dial peers
- incoming COR lists to inbound matched dial peers
- outgoing COR lists to outbound matched dial peers
We are going to apply one COR list for the inbound matched dial peer for calls from x1000; and we’re going to apply another COR list for the inbound matched dial peer for calls from x1003.
Given the current configuration of the HQ router, I’m using a dial-peer 9999 for inbound call leg matching. The dial peer 9999 uses “incoming called-number .” statement to match any inbound call leg. But you see, no matter what the source of the call leg is, dial peer 9999 is going to match. And that’s not a good thing because we want to apply different COR lists for different call sources.
So I modified the inbound matched dial peer. Instead of dial peer 9999, I created two dial peers 9998 and 9997 that respectively have “answer-address 1000” and “answer-address 1003”. Remember that, for an nibound dial peer matching, a dial peer with “answer-address” = ANI is a match.
A direct result of that is:
- when x1000 calls through the gateway, dial peer 9998 is the inbound matched dial peer,
- when x1003 calls through the gateway, dial peer 9997 is the inbound matched dial peer,
Let’s check this on the lab.
we make simple call from x1000 to a PSTN long-distance number, let’s say 14048847473:
And we make a call to the same destination, from x1003:
- for calling party number x1000, we will apply an incoming COR list to dial peer 9998 and an outgoing COR list to dial peer 1201
- for calling party number x1003, we will apply an incoming COR list to dial peer 9997 and apply the same outgoing COR list to dial peer 1201
Defining COR names
Defining COR lists
We apply the outgoing COR list national to the outbound matched dial peer 1201
We apply incoming COR lists to the inbound matched dial peers :
A call from x1000 succeeds
A call from x1003 to the same destination fails.