06-25-2008 10:43 PM - edited 03-15-2019 11:32 AM
Hi all
I'm busy checking to see my config is correct for the above, I havent been able to test it yet, can anyone see this working?
interface BRI0/1/0
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
no isdn outgoing ie progress-indicator
no isdn outgoing display-ie
no isdn outgoing ie called-number
!
dial-peer cor custom
name local
name LN
name LNC
name LNCI
!
!
dial-peer cor list local
member local
!
dial-peer cor list LN
member local
member LN
!
dial-peer cor list LNC
member local
member LN
member LNC
!
dial-peer cor list LNCI
member local
member LN
member LNC
member LNCI
!
!
dial-peer voice 1 pots
corlist outgoing local
description local
destination-pattern 04.T
direct-inward-dial
port 0/1/0
!
dial-peer voice 2 pots
corlist outgoing LN
description LN
destination-pattern 0[1-5].T
direct-inward-dial
port 0/1/0
!
dial-peer voice 3 pots
corlist outgoing LNC
description LNC
destination-pattern 0[1-9].T
direct-inward-dial
port 0/1/0
!
dial-peer voice 4 pots
corlist outgoing LNCI
description LNCI
destination-pattern ...T
direct-inward-dial
port 0/1/0
!
dial-peer voice 6 voip
description WAN Calls
destination-pattern 7...
session protocol sipv2
session target ipv4:172.16.4.51
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 7 voip
description Voicemail
destination-pattern 5...
session protocol sipv2
session target ipv4:172.16.1.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
!
!
telephony-service
load 7910 P00403020214
load 7960-7940 P00307020200
max-ephones 35
max-dn 48
ip source-address 192.168.4.254 port 2000
auto assign 1 to 35
system message Trident Steel PE
url services http://172.16.1.2/voiceview/common/login.do
url authentication http://172.16.1.2/voiceview/authentication/authenticate.do
network-locale GB
date-format dd-mm-yy
create cnf-files version-stamp Jan 01 2002 00:00:00
dialplan-pattern 1 0414056... extension-length 4
voicemail 5000
max-conferences 8 gain -6
moh music-on-hold.au
web admin system name shauns password shauns
dn-webedit
time-webedit
transfer-system full-consult
This is the first CME system I am doing, so any crits / tips would be greatly appreciated
06-26-2008 01:59 AM
Hi, to begin with the two DPs are overlapping:
dial-peer voice 2 pots
corlist outgoing LN
description LN
destination-pattern 0[1-5].T
direct-inward-dial
port 0/1/0
!
dial-peer voice 3 pots
corlist outgoing LNC
description LNC
destination-pattern 0[1-9].T
direct-inward-dial
port 0/1/0
both will catch second digit from 1 to 5.
Do you really need so maby COR classes?
06-26-2008 02:06 AM
Oh, I see that now. the client is pretty hung up about employeed making unauthorised calls, so I need to make sure certain people can only make Local, local-national, local-national-mobile, local-national-mobile-international. To be honest the CoR on the CME is quite confusing for a first timer like myself. Is there away i could do this to achieve the CoR required?
Thanks for the help!
Shaun
06-26-2008 02:13 AM
Yes, the best way is that you try to simplify the client request as much as possible.
Example, if they can have just two categories, one that makes any type of call, another that is blocked for some types, that is a pretty simple config that I can give you an example.
Also, where are you located? In many countries it is possible to make the dialplan so you don;t need to dial any "0" or "9" to fial anj extenral lines. Usually customers like that very much because it's like calling from home.
Finally please mention if you have a single FXO line or more that one.
06-26-2008 02:25 AM
I am in South Africa, I think at most the most simple acceptable CoR would be:
Local only
Local, National only
Local,National,international,mobile
We are using a 2821 with 2 BRI's, but only using them as one so I suppose 1 FXO. However we also want to route calls (only destined for another branch within the voip network) over their Serial interface to their head office in Johannesburg. Johannesburg is running CCM 5.1 and is fully configured and working using a Non MGCP 2821 gateway and not using SRST.... yet!
06-26-2008 03:01 AM
Hi,
first of all your 2 x BRI has nothing to do with FXO. To use them "as one" you configure trung groups:
voice-port x/y/0
trunk-group bri
voice-port x/y/1
trunk-group bri
Now for the COR config, the minimal way is the following:
dial-peer cor custom
name call-nat
!
dial-peer cor list national
member call-nat
!
dial-peer cor list dummy
! note NO members here
!
dial-peer voice 1 pots
trunk-group bri
description local
! note NO corlist
dial-peer voice 2 pots
trunk-group bri
description National
corlist outgoing national
dial-peer voice 3 pots
trunk-group bri
description International
corlist outgoing dummy
dial-peer voice 4 pots
trunk-group bri
descrption Cellular
corlist outgoing dummy
ephone-dn-template 1
corlist incoming local
ephone-dn-template 2
corlist incoming national
The apply the ephone-dn-templates to the ephone-dn's you need to block. Do not do anything for the ones that you're NOT blocking.
This config takes advantage of the fact that if on either incoming or outgoign DP has no corlist, no blocking will occour.
Hope this helps, please rate post if it does!
06-27-2008 02:05 AM
Hi
Thanks for that, I will need to test that, however, I have connected the BRI to int bri0/1/0 and when trying to dial in, I see the call on the router using debug q931, but it doesnt ring on the called party phone, the calling party I hear the phone ringing, here is the debug:
*Jun 27 10:19:53.715: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Calling num 0113252322
*Jun 27 10:19:53.719: ISDN BR0/1/0 Q931: Applying typeplan for sw-type 0x1 is 0x0 0x0, Called num 0119129300
*Jun 27 10:19:53.747: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 73 changed to up
*Jun 27 10:19:53.747: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x13
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x81
Calling Party Number i = 0x0080, '0113252322'
Plan:Unknown, Type:Unknown
*Jun 27 10:19:53.851: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x93
Cause i = 0x82C1 - Bearer capability not implemented
Sorry I just want to tackle this, then the outgoing calls (cant make outgoing calls either) then will have a look at the CoR.
Thanks for all the help thus far
06-27-2008 02:56 AM
Hi, under voice-port for bri, configure "compand-type a-law."
06-26-2008 02:27 AM
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