Thanks Frog for the update.
your name convention is a bit strange though:)
1st example
block2003 is actually to block 2002 from translation profile reject /^2002/
in your 2nd example.
you are blocking 3001 by placing 3001 in a partition let-it-go
block css does not have partition let-it-go, so the call to 3001 will fail.
in this config let-it-go actually meant for block
and block css actually meant for allow
did i get it right?
i also noticed that your css and partition have the same name, it is
recommended approach?
Sara
FrogOnDSCP46EF <[EMAIL PROTECTED]> wrote: sara,
Please note, I was testing it yesterday and had many issue.
The only working solution I had are:
This one is simple and easy....
1. config t
dial-peer voice 1
desc ##
incoming called-number .T
port 2/0:23
call-block translation-profile incoming block2003
voice translation-rule 1
rule 1 reject /^2002/
!
!
voice translation-profile block2003
translate called 1
!
OR
in this example, we are trying to block incoming call to 3002 from PSTN.
Our global incoming called number .T dialpeer is "1" in below example. We put
.T example in let-it-go partion (seprate) and then put 3002 in different CSS
(block)
dial-peer cor custom
name let-it-go
name block
!
!
dial-peer cor list block
member block
!
dial-peer cor list let-it-go
member let-it-go
!
dial-peer voice 1 pots
corlist incoming block
incoming called-number .T
direct-inward-dial
port 0/2/0:23
call-manager-fallback
cor outgoing let-it-go 1 3001
Note: U see in above example "dial-peer voice 1 pots" configuration has
CSS=block which can't access "lte-it-go" partion configured in
call-manager-fallback. Therfore calls coming in will be not pass thorugh to
router to fallback.
Frog
On Sat, Apr 19, 2008 at 10:10 PM, <[EMAIL PROTECTED]> wrote:
Frog,
Thanks for the explanation, i think using translation pattern is easier to
follow :)
also good stuff from JD, cor-list in outgoing direction is partition and
incoming direction is css.
thanks
Sara
FrogOnDSCP46EF <[EMAIL PROTECTED]> wrote: Hi Sara,
The example config you've pasted on the forum shows:
condition1: DN:2002 should be able to dial Internal.
condition2: DN:2002 should receive all incoming call too. (assuming CSS_ALL
have everything, as u didn't paste full config).
------------------------
In a nutshell, here is what my understanding is about the COR.
Lets say DN2002 should able to dial everyone in SRST but no PSTN caller should
be able to dial 2002.
step1: create partiotions
dial-peer voice cor custom
name 911
name local
name ld
name intl
Step2: create cor list:
dial-peer voice cor list 911 <----css same as in CCM
member 911 <--------------partition created in step1
dial-peer voice cor list local
member local
dial-peer voice cor list ld
member ld
dial-peer voice cor list intl
member intl
note: above 4 we will apply to the POTS dialpeer
dial-peer voice 3 pots
corlist outgoing 911 <--------noticed the list above we created?
destination-pattern 911
port 0/2/0:23
forward-digits 3
!
dial-peer voice 4 pots
destination-pattern 9[2-9]......
corlist outgoing local
port 0/2/0:23
forward-digits 7
!
dial-peer voice 5 pots
destination-pattern 91[2-9]..[2-9]......
corlist outgoing ld
port 0/2/0:23
forward-digits 11
!
dial-peer voice 10 pots
destination-pattern 9011T
corlist outgoing outgoing ld
port 0/2/0:23
prefix 011
!
Now we've made a pitch for our COR so far... now time to look at the question
and prepare for it
step3: Create custom CORLIST now for restricting phone dn 2002 (incoming
restricted but outgoing it shud be able to dial everone.
--------
Outgoing calls from 2002:
dial-peer voice corlist DN2002
member 911 <---will be able to access the dial-peer POTS 911, local, ld ,
intl (call to everyone from 2002 dn)
member local
member ld
member intl
Apply above corlist in SRST configuration:
config t
call-manager-fallback
corlist outgoing DN2002 1 2002 <---------- CORLIST DN2002 is applied to
phone DN 2002.
thats all, 2002 will be able to call everyone...
now work on PSTN callier calling DN 2002 in SRST.. (INCOMING to 2002)
We can achieve this task in 2 way...
My prefereed way just create a translation profile and apply that to
srst-fallback:
voice translation-rule 1
rule 1 reject /^2002/
voice translation-profile BLOCK2002incoming
translate called 1
config t
call-manager-fallback
translation-profile incoming BLOCK2002incoming
or
voice-port 0/2/0:23
voice translation-profile incoming block2002incoming
thats all..
in the lab book 8.9 there is a requirement to configure cor so that no pstn
caller to call 2002 in srst mode.
the config given is:
cor incoming css-911 1 2002-2003
cor incoming css-all 2 2002
cor outgoing css-intl 3 2002
dial-peer voice 2 pots
corlist incoming css-911
incoming called number .
direct-inward-dial
dial-peer css-intl
member pt-internal
dial-peer css-911
member pt-911
--
Smile, you'll save someone else's day!
Frog
---------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
--
Smile, you'll save someone else's day!
Frog
---------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
