Bartosz,
Try using 2 sets of dialpeers on IPIPGW: one set hardcoded to G711 with
"max-conn 1" and second set hardcoded to G729 with "max-conn 1"+"priority
1". Please report your results if/when you have a chance of labbing this
up:-)
Cheers
Alex
----- Original Message -----
From: "Bartosz Sokołowski" <[EMAIL PROTECTED]>
To: <ccie_voice@onlinestudylist.com>
Sent: Monday, November 10, 2008 6:37 PM
Subject: Re: [OSL | CCIE_Voice] Section 28 Tasks 23 and 28,LAB Prep Workbook
v4.0, call via GateKeeper and IPIPGW problem
Hello Alex,
IPIPGW won't negotiate the codec with HQR, it has to be statically
nailed down for all 4 legs. If you wish to have G729 call from CCM to
CME via IPIPGW, then it should be 4 dialpeers with default G729 codecs
(2 with "incoming called-number", 2 with "destination-pattern"):
That was it! Thanks! Now G729 works.
As I understand - without a transcoder on HQ-RTR there is no codec
flexibility - I mean a scenario when 1st call from CCM uses G711 and the
second uses G729 (due to bandwidth limit on GK) is impossible?
Now I have RG with both trunks (711/729) and I also added another four
dial-peers hardcoded for G711 but it doesn't work.
You can also change codec to 'codec transparent' on every dial-peer and then
you have a choice on CCM - if you put 729-trunk 1st on RG list then it will
use 729. If you put 711-trunk 1st on the list then it will use 711.
The question is how to achieve a flexibility - 1st call 711 and 2nd 729 due
to lack of bandwidth.
--
Best regards,
Bartosz
dial-peer voice 100 voip
incoming called-number [12]... # Inbound DP for CCM->IPIPGW call leg
dtmf-relay h245-alpha
!
dial-peer voice 101 voip
incoming called-number 3313213... # Inbound DP for BR2->IPIPGW call leg
dtmf-relay h245-alpha
!
dial-peer voice 102 voip
destination-pattern 011T # Outbound DP for IPIPGW->BR2 call leg
session target ras
dtmf-relay h245-alpha
!
dial-peer voice 103 voip
destination-pattern [12]... # Outbound DP for BR2->IPIPGW call leg
session target ras
dtmf-relay h245-alpha
!
It always worked for me this way.
If you want to transcode G711->G729 on IPIPGW, configure SRST/CCME
instance, SDSP farm and register SDSP farm to SRST/CCME instance.
Rgds
Alex
----- Original Message ----- From: "Bartosz Sokołowski"
<[EMAIL PROTECTED]>
To: <ccie_voice@onlinestudylist.com>
Sent: Monday, November 10, 2008 4:54 PM
Subject: [OSL | CCIE_Voice] Section 28 Tasks 23 and 28,LAB Prep Workbook
v4.0, call via GateKeeper and IPIPGW problem
Hello,
I have problem with calls from CCM to BR2 via GK and IPIPGW.
If I configure HQ-RTR GK without IPIPGW (no invia/outvia) like this:
!
!
gatekeeper
zone local HQ-RTR sldx.lab 172.1.100.1
zone local VGK sldx.lab
zone remote PSTN-WAN sldx.lab 10.1.200.2
zone prefix PSTN-WAN 011*
bandwidth remote 144
no shutdown
!
Everything works fine, I mean 1st call (from 1001 to 3001) uses G711 and
establishes without any problems, second call (from 1002 to 3002) uses
G729
and establishes without any problems. Third call (1003 to 3003) fails as
there is no more bandwidth available. Great.
For me this behavior means that all CCM stuff is configured correctly
(trunks, patterns, , PTs/CSS, RGs, RLs, etc.).
The problem is that if I want to use IPIPGW and change GK config to:
!
!
gatekeeper
zone local HQ-RTR sldx.lab 172.1.100.1
zone local VGK sldx.lab
zone remote PSTN-WAN sldx.lab 10.1.200.2 1719 invia VGK outvia VGK
zone prefix PSTN-WAN 011*
bandwidth remote 144
no shutdown
!
only G711 calls works.
On CCM I removed from RG trunk with G711 DP/Region and tried G729
call. The
setup works, BR2 phone rings but if I pickup the BR2 phone no RTP is
exchanged between the phones and after a while there is a fast busy
signal.
I can see that CCM phone tries to use G711 instead of G729.
Any one has any idea what is going on?
I tried some debugs (see below) and I see that I'm hitting dial-peer 0
for
incoming call but I have no idea why.
I'll be glad for any suggestion what to change in config in order to
make it
work as expected. Solution described in Proctor Guide book doesn't
work form
me :(
My config and debugs:
----------------- HQ RTR -----------------------------
!
voice service voip
allow-connections h323 to h323
!
!
interface Loopback0
ip address 172.1.100.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip id VGK ipaddr 172.1.100.1 1719
h323-gateway voip h323-id dupa
h323-gateway voip bind srcaddr 172.1.100.1
!
!
dial-peer voice 2 voip
destination-pattern 011T
session target ras
codec g711ulaw
!
dial-peer voice 3 voip
session target ras
incoming called-number [12]...
!
dial-peer voice 1 voip
session target ras
incoming called-number [12]...
codec g711ulaw
!
gateway
!
!
gatekeeper
zone local HQ-RTR sldx.lab 172.1.100.1
zone local VGK sldx.lab
zone remote PSTN-WAN sldx.lab 10.1.200.2 1719 invia VGK outvia VGK
zone prefix PSTN-WAN 011*
bandwidth remote 144
no shutdown
!
--
SOLIDEX S.A.
Tel: +48 12 638 04 80
Fax: +48 12 638 04 70
http://www.SOLIDEX.com.pl
http://www.SOLIDnySerwis.pl
Niniejsza wiadomość zawiera informacje zastrzeżone i stanowiące tajemnicę
przedsiębiorstwa firm grupy SOLIDEX. Ujawnianie tych informacji osobom
trzecim lub nieuprawnione wykorzystanie ich do wlasnych celów jest
zabronione. Jeżeli otrzymaliście Państwo niniejszą wiadomość omyłkowo,
prosimy o niezwłoczne skontaktowanie się z nadawcą oraz usunięcie wszelkich
kopii niniejszej wiadomości.
This message contains proprietary information and trade secrets of SOLIDEX
group companies. Unauthorized use or disclosure of this information to any
third party is prohibited. If you received this message by mistake, please
contact the sender immediately and delete all copies of this message.
