Looks like you right - I've tried it with both, PVDM and PVDM2. In both cases transcoder registers instantly, but conferencing does not. I will try to upgrade IOS on one of the router to CME 4.0 and see if it will solve the problem with the same config.

----- Original Message ----- From: "Robert Schuknecht" <[EMAIL PROTECTED]>
To: <ccie_voice@onlinestudylist.com>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 22, 2008 2:26 PM
Subject: Antw: [OSL | CCIE_Voice] Problem with PVDM-2 Conferenceregistration


Hi Michael,

Hardware Conferencing is not supported with CCME 3.3. When you want to use a Hardware Conferencebridge with CCME you have to use CCME Version 4.0 or maybe higher, i donĀ“t remember it at the moment.

HTH

/Robert

Michael Shavrov<[EMAIL PROTECTED]> schrieb am Mittwoch, 22. Oktober 2008 um
18:57 in Nachricht 93f2ba42c46071d4f82376100596cbc2:
Hi All,

I have an ongoing problem with creating a media resources on CME router. I create 2 dspfarm profiles, configure SCCP, register with CME... Transcoding registeres fine, but Conferencing does not. Here is part of the config, and
the SCCP status:
----
voice-card 0
 dspfarm
 dsp services dspfarm
!
sccp local GigabitEthernet0/0.123
sccp ccm 10.10.66.254 identifier 1
sccp ip precedence 3
sccp
!
sccp ccm group 1
 bind interface GigabitEthernet0/0.123
 associate ccm 1 priority 1
 associate profile 1 register cfb001da10466d8
 associate profile 2 register mtp001da10466d8
!
dspfarm profile 2 transcode
 codec g711ulaw
 codec g711alaw
 codec g729ar8
 codec g729abr8
 codec g729r8
 maximum sessions 4
 associate application SCCP
!
dspfarm profile 1 conference
 codec g711ulaw
 codec g711alaw
 codec g729ar8
 codec g729abr8
 codec g729r8
 codec g729br8
 maximum sessions 2
 associate application SCCP
!
telephony-service
 sdspfarm units 2
 sdspfarm tag 1 cfb001da10466d8
 sdspfarm tag 2 mtp001da10466d8
 ip source-address 10.10.66.254 port 2000
 max-conferences 2 gain -6
!
-----------------------------
R7-BR2#sh sccp
SCCP Admin State: UP
Gateway IP Address: 142.103.66.254, Port Number: 2000
IP Precedence: 3
User Masked Codec list: None
Call Manager: 142.103.66.254, Port Number: 2000
                Priority: N/A, Version: 3.1, Identifier: 1

Transcoding Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 142.103.66.254, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 2
Reported Max Streams: 8, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization
Period: 30

Conferencing Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED
Active Call Manager: 142.103.66.254, Port Number: 2000
TCP Link Status: NOT_CONNECTED, Profile Identifier: 1
Reported Max Streams: 16, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization
Period: 30


Reply via email to