How to configure endpoints in H323 Gateway

[sarwarm123]

Hello

I am new in IP Telephony so please ignore if I ask any silly question, basically our clients dont want to share each other channels. So I decided configure MGCP controlled gateway as it will give more control on the gateway but unfortunately I am unable to complete this job due lots of issue. So I decided configure H323 Gateway. My question is there any way I can have control on endpoints or BRI ports in H323 Gateway or if you can give me your expert opinion how I can achieve my task using H323 Gateway. As I said above our clients don’t want to share channels, so please suggest how I can split channels and allocate ports to end users

Thanks

Muhammad Atif Sarwar

[allan.thomas · Accepted solution]

Hi,

Please take time to review the following document regarding Trunk selection enhancement for routing, it has been around since 12.2T. In summary you can configure trunk groups on your voice gateway and assign them to different voice-ports, thus giving the physical separation. You will need to configure your outgoing call legs or pots dial-peers with specific destination patterns that are defined as route-patterns in Communications Manager and associated with the route-group or h323 endpoint. The Route-Patterns and Destination pattern in the dial-peer will have to have a prefix to ensure the correct trunk group is used for the outgoing call leg:

http://www.cisco.com/en/US/docs/ios/12_2t/12_2t11/feature/guide/ftgwrepg.html

Regards
Allan

Sent from Cisco Technical Support iPad App

[sarwarm123]

Allan you are star mate, I tried to configure trunk group and voice translation rules, somehow I managed but my voice translation outgoing is not working on outgoing dial peer. I just posted config, can you please give some idea why its not working. Basically what I want, when ip extension 47900 dial outside call it should go through trunk group  BRI0/1/1 voice port. If you tell me with example, will much appreciate.

hostname 2851-rtr1
!
boot-start-marker
warm-reboot
boot-end-marker
!
logging buffered 200000
enable secret 5 $1$j5sM$lKaaf2uWiCoFzDJEWccAG.
!
no aaa new-model
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 BRI0/0/0
network-clock-select 2 BRI0/0/1
network-clock-select 3 BRI0/1/0
network-clock-select 4 BRI0/1/1
dot11 syslog
!
!
ip cef
!
!
no ip domain lookup
ip domain name cwss.nhs.uk
multilink bundle-name authenticated
!
isdn switch-type basic-net3
!
!
trunk group  BRI
!
!
trunk group  BRI0/1/1
translation-profile outgoing outgoing
!
voice-card 0
no dspfarm
dsp services dspfarm
!
!
voice call convert-discpi-to-prog
voice call carrier capacity active
voice rtp send-recv
!
voice service voip
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
!
!
voice class codec 99
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729br8
!
!
!
voice class h323 1
h225 timeout tcp establish 3
!
!
!
voice translation-rule 1
rule 1 /^638094/ /47900/
!
voice translation-rule 2
rule 1 /47900/ /47900/
!
voice translation-rule 10
!
voice translation-rule 20
rule 1 // /90/ type national national
rule 2 // /900/ type international international
!
!
voice translation-profile Add9
translate calling 20
translate called 1
!
voice translation-profile DD-IN
translate called 1
!
voice translation-profile SRST_Remove
translate calling 20
translate called 10
!
voice translation-profile outgoing
translate calling 2
!
!
!
!
!
!
username ansgroup privilege 15 secret 5 $1$xNdk$pgOhqGzMjBtd7KP/DzLBy/
username admin privilege 15 secret 5 $1$TncT$l2tqOp4GISTZpEtx2DjmE0
archive
log config
  logging enable
  hidekeys
!
!
!
!
!
!
interface Loopback0
description Local Multicast MoH
ip address 10.1.1.1 255.255.255.255
!
interface GigabitEthernet0/0
ip address 10.88.48.3 255.255.255.128
duplex auto
speed auto
h323-gateway voip interface
!
interface GigabitEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
isdn static-tei 0
trunk-group BRI
!
interface BRI0/0/1
description Faulty-CRCerrors
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
!
interface BRI0/1/0
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
isdn static-tei 0
trunk-group BRI
!
interface BRI0/1/1
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
trunk-group BRI0/1/1
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 10.88.48.1
!
!
ip http server
no ip http secure-server
!
no logging trap
!
!
!
control-plane
!
!
!
voice-port 0/0/0
translation-profile incoming Add9
input gain 3
output attenuation -3
echo-cancel coverage 32
compand-type a-law
cptone GB
!
voice-port 0/0/1
translation-profile incoming Add9
input gain 3
output attenuation -3
echo-cancel coverage 32
compand-type a-law
cptone GB
!
voice-port 0/1/0
translation-profile incoming Add9
input gain 3
output attenuation -3
echo-cancel coverage 32
compand-type a-law
cptone GB
!
voice-port 0/1/1
translation-profile incoming Add9
translation-profile outgoing outgoing
input gain 3
output attenuation -3
echo-cancel coverage 32
compand-type a-law
cptone GB
!
no ccm-manager fax protocol cisco
!
sccp local GigabitEthernet0/0
sccp ccm 10.102.243.12 identifier 1 version 5.0.1
sccp ip precedence 3
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register Willenhall_TR
keepalive retries 5
switchover method immediate
switchback method immediate
switchback interval 15
!
dspfarm profile 1 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
maximum sessions 1
associate application SCCP
shutdown
!
!
dial-peer voice 1 pots
trunkgroup BRI
description ** Default Dial-Peer **
incoming called-number .
direct-inward-dial

dial-peer voice 2 pots
trunkgroup BRI0/1/1
translation-profile outgoing outgoing
destination-pattern 11T
progress_ind setup enable 3
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
direct-inward-dial
!

!
dial-peer voice 9 pots
trunkgroup BRI
destination-pattern 9T
progress_ind setup enable 3
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
direct-inward-dial
prefix 141
!

dial-peer voice 10 voip
preference 1
destination-pattern .....
progress_ind setup enable 3
modem passthrough nse codec g711ulaw
voice-class codec 99
voice-class h323 1
session target ipv4:10.102.243.13
dtmf-relay h245-alphanumeric
no vad
!
dial-peer voice 479 voip
destination-pattern 47964
voice-class h323 1
session target ipv4:10.102.243.12
session transport udp
codec g711ulaw
!
dial-peer voice 2 pots
trunkgroup BRI0/1/1
translation-profile outgoing outgoing
destination-pattern 0..........
progress_ind setup enable 3
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
no digit-strip
direct-inward-dial
!
!
num-exp 663209 47901
num-exp 7079.. 479..
!

!
!
line con 0
logging synchronous
login local
line aux 0
line vty 0 4
privilege level 15
password 7 030752180500
logging synchronous
login local
transport input telnet ssh
line vty 5 15
privilege level 15
login local
transport input telnet ssh
!
scheduler allocate 20000 1000
ntp clock-period 17180289
ntp server 194.72.7.142 prefer
ntp server 194.72.7.137
!
end

2851-rtr1#

[allan.thomas]

Hi,

Glad that you've found the information helpful. The likely reason that you are not hitting the correct outgoing dial-peer is dependant on the destination-pattern or called party number. From within CUCM you need to ensure that there is differentiation between company A and B and how they make outbound calls.

As it stands you will have a route pattern which either point to a RL or the H323 gateway, the dialled digits will then be matched based on the destination-pattern on the pots dial-peer on the gateway, so you need different route-patterns and dial-peers each with unique destination patterns for each company.

For each company you can create unique route patterns in partitions which are only assigned to the Line CSS for that Company, this will allow you to prefix the dialled number making it transparent to the end-user, but unique so that it can be matched on the appropriate pots dial-peer. For example company A dials 9xxxxxxx, the RP for Company A should prefix 01, so the destination-pattern on the dial-peer will something like 019T and the digit strip will be carried out by default on the pot dial-peer. It will be this dial-peer which is associated with the respective trunk-group.

if you are unsure what is happening on the gateway, debug voice ccapi inout, this will indicate the dial-peer used for the outgoing call-leg.

Regards
Allan

Sent from Cisco Technical Support iPad App