[cisco-voip] CMM Config with ACT

[Voll, Scott]

Can anyone tell me what the differences are between the 12.3xy code,
12.3T code and 12.4mainline code?  If I understand 12.3t should be the
same as 12.4 mainline right?  So I guess the real question is what is
the difference between xy and the other to?

Thanks

Scott

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Thursday, June 09, 2005 9:02 AM
To: Voll, Scott
Cc: andy at dignans.com; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CMM Config with ACT

FYI 12.3(8)XY5 is out on CCO if you search for it.  It won't be easily 
found until tomorrow (actually eod SJ PST today) but if you use the 
software search tool you can find it now.  It has the fix for 
CSCsa72406 as well as a few others related to the CMM (I didn't get any 
specifics from DE on them).

-Ryan
On Jun 9, 2005, at 11:22 AM, Voll, Scott wrote:

Andy--

I know how you feel about TAC not knowing anything about the CMM Blade.
I went through the same thing myself.

Here is my working config:

6509 running 12.2.18SXE1 (was 12.2.18sxd4 also)

interface GigabitEthernet9/1
  switchport
  switchport access vlan 102
  no ip address
  mls qos trust dscp
!
interface FastEthernet9/2
  switchport
  switchport access vlan 102
  no ip address
!
interface FastEthernet9/3
  switchport
  switchport access vlan 102
  no ip address
!
interface FastEthernet9/4
  switchport
  switchport access vlan 102
  no ip address
!
interface FastEthernet9/5
  switchport
  switchport access vlan 102
  no ip address

******Vlan 102 is my Voice Vlan**********

CMM is running 12.3(8)XY.  I tried 12.4 but it had a Multicast MoH Bug.


!
interface FastEthernet0/0
  ip address y.y.102.6 255.255.255.255
  no ip proxy-arp
  full-duplex
!
interface GigabitEthernet1/0
  ip address y.y.102.5 255.255.255.0
  no ip proxy-arp
  ip pim sparse-dense-mode
  no negotiation auto
  no keepalive

!
mediacard 1
  resource-pool Ad-Hoc dsps 2
  resource-pool transcodeMcMinnville dsps 2
!
!
sccp local GigabitEthernet1/0
sccp ccm y.y.102.36 identifier 1
sccp ccm y.y.102.35 identifier 2
sccp
!
sccp ccm group 1
  associate ccm 1 priority 1
  associate ccm 2 priority 2
  associate profile 1 register CFB001192b75643
  associate profile 2 register MTP001192b75643
!
dspfarm
!
dspfarm profile 1 conference adhoc
  codec g711ulaw packetization-period 30
  codec g711alaw packetization-period 30
  codec g729r8 packetization-period 30
  codec g729ar8 packetization-period 30
  codec g723r63 packetization-period 30
  codec g723r53 packetization-period 30
  associate resource-pool Ad-Hoc
!
dspfarm profile 2 transcode
  codec g711ulaw packetization-period 30
  codec g711alaw packetization-period 30
  codec g729r8 packetization-period 30
  codec g729ar8 packetization-period 30
  codec g723r63 packetization-period 30
  codec g723r53 packetization-period 30
  associate resource-pool transcodeMcMinnville
!
Scott

PS.  Make sure the Meetme conference is in the "none" partition in CM.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Andrew Dignan
Sent: Wednesday, June 08, 2005 1:46 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CMM Config with ACT

Anyone out there have an actual working config on the 6500 side and the
CMM side?  The CMM configuration guide on CCO has many inacuracies and I
have had a TAC case open for 6 days now with no luck.  I am just getting
tired of working this case, it doesn't appear there are any experts on
the
CMM at TAC (I know there are but I just haven't gotten passed around to
one yet).  We have the CMM up and working properly, routing calls
through
the PRI's and T1 cas links.  However, the ACT card has not worked
properly
yet.  When trying to initiate a conference, the bridge is setup and you
can do a "show mediacard conference" to verify its the active conference
bridge, but no audio gets passed between the partys on the call.  The rx
and tx increments on the phones if you hit the ? button but no audio.
If
you hit a button on the phone, all partys on the conference can hear the
dtmf tone which is odd, but no actual voice.

The phone vlan can ping the Gig0/1 interface of the CMM, the phone vlan
can ping the ip addresses assigned to the FE interfaces for the ACT
card.
The conference bridge is registered in CM.  The switch side has the
Gig7/1
and FE 7/1-4 all in the same VLAN.

TIA,

Andy
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip