Question:
If it is possible, what would the config be if two ip phones needed to be restricted to use only two specific outgoing lines(POTS) when dialing an access code (9) and all other IP phones could dial the same access code(9) and be restricted to the other two available outgoing lines. Thank you in advance.
Anyways, setting this up via command line, or CUE via configure/extensions doesn't seem to work. I was simply trying to make a lobby phone internal only, I set From Phone to default, and To Phone user-internal and I could still call wherever I wanted?
Just taking a guess here... If you look at the "dial-peer voice XX pots" interface you would see a "corlist outgoing call-local" command attributed to all "destination-pattern 9[2-9]......." FXO ports.
I.E.
dial-peer voice 52 pots
corlist outgoing call-local
description ** FXO pots dial-peer **
preference 1
destination-pattern 9[2-9].........
port 0/1/0
forward-digits 10
no sip-register
The COR list is furthermore defined as...
dial-peer cor list call-local
member local
NOW... You can create your own COR list and call if LockedDownPhones...
I.E.
And finally, go to the ephone-dn XX configuration, where XX is the phone or phones that you wish to lock down to a specific FXO port, in this case 0/1/0, and apply the COR list...
In the end, maybe this would push out LockedDownPhones over FXO 0/1/0 for dial-patterns of 9[2-9]....... Conversly, if you are using the smal UC520 with only four stock FXO ports, and 4 IP phones, you could assign the other two phones to a COR list and attach them to FXO 0/1/2 and 0/1/3. This is just a guess though :P
Many times I see COR Described as a lock and keys.
You place and outgoing COR on your Dial Peers that you want to restrict access to ( This is the Lock)
You place an Incoming COR on the Ephone-DNs(extensions) That you want to Give access to the outgoing CORs (These are Keys)
If a ephone-DN has no Incoming COR applied it is like having a master key and has access to everything
If a Ephone-dn has a Incoming COR applied it can only access the ougoing CORs (on dial peers) that are defined for it.
COR
I would assume that everything I posted earlier is bunk, I can't seem to get a COR list to work properly on a simple ephone-dn for incoming calls similar to the examples in http://www.cisco.com/warp/public/788/AVVID/configuring-cor.html
?
Anyways, setting this up via command line, or CUE via configure/extensions doesn't seem to work. I was simply trying to make a lobby phone internal only, I set From Phone to default, and To Phone user-internal and I could still call wherever I wanted?
Just taking a guess here...
Just taking a guess here... If you look at the "dial-peer voice XX pots" interface you would see a "corlist outgoing call-local" command attributed to all "destination-pattern 9[2-9]......." FXO ports.
I.E.
dial-peer voice 52 pots
corlist outgoing call-local
description ** FXO pots dial-peer **
preference 1
destination-pattern 9[2-9].........
port 0/1/0
forward-digits 10
no sip-register
The COR list is furthermore defined as...
dial-peer cor list call-local
member local
NOW... You can create your own COR list and call if LockedDownPhones...
I.E.
dial-peer cor list LockedDownPhones
member local
Assign this to a dial-peer group
I.E.
dial-peer voice 52 pots
corlist outgoing LockedDownPhones
description ** FXO pots dial-peer **
preference 1
destination-pattern 9[2-9].........
port 0/1/0
forward-digits 10
no sip-register
And finally, go to the ephone-dn XX configuration, where XX is the phone or phones that you wish to lock down to a specific FXO port, in this case 0/1/0, and apply the COR list...
I.E.
ephone-dn 20 dual-line
corlist outgoing LockedDownPhones
In the end, maybe this would push out LockedDownPhones over FXO 0/1/0 for dial-patterns of 9[2-9]....... Conversly, if you are using the smal UC520 with only four stock FXO ports, and 4 IP phones, you could assign the other two phones to a COR list and attach them to FXO 0/1/2 and 0/1/3. This is just a guess though :P
A little analogy for COR
Many times I see COR Described as a lock and keys.
You place and outgoing COR on your Dial Peers that you want to restrict access to ( This is the Lock)
You place an Incoming COR on the Ephone-DNs(extensions) That you want to Give access to the outgoing CORs (These are Keys)
If a ephone-DN has no Incoming COR applied it is like having a master key and has access to everything
If a Ephone-dn has a Incoming COR applied it can only access the ougoing CORs (on dial peers) that are defined for it.
Hope i didn't confuse the subject.
Ted