Re: Call Manager can't find 6509 CMM resources

gwhuang5398 · ‎12-29-2006

I configured 6509 CMM module media card for a conferencing resource and a transcoder, then I inserted them into Call Manager as media resource. But neither was able to register with a call manager. There's no issue with routing and reaching each other's IP addresses.

Any suggestions?

Thanks

Gary

gogasca · ‎12-29-2006

Please make sure you have followed this guide:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123limit/123x/123xy8/gtcmm.htm#wp1285052

IP connectivity between CMM and CCM is fine right?

If all is good please paste your config and an screenshot of CCM CFB config

gwhuang5398 · ‎12-29-2006

I followed all the procedures in that document. All the IP connectivities are good. I can ping the CMM intrefaces (G1/0, Fa1/0. Fa3/0) anywhere on the network. Can also ping CCMs from the CMM.

Here is the relevant CMM config:

mediacard 2

resource-pool nokct1vg01a-conf dsps 4

!

mediacard 4

resource-pool nokct1vg01a-trans dsps 4

!

sccp local GigabitEthernet1/0

sccp ccm 172.28.4.5 identifier 1

sccp ccm 172.28.105.5 identifier 2

sccp ccm 10.132.189.5 identifier 3

sccp

!

sccp ccm group 801

associate ccm 3 priority 3

associate ccm 2 priority 2

associate ccm 1 priority 1

associate profile 2 register MTP0018b983f9aa

associate profile 1 register CFB0018b983f9a8

!

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 nokct1vg01a-conf

!

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 nokct1vg01a-trans

!

On CCM:

Service > Media Resource > Conference Bridge.

Then "Add New Conference Bridge":

Conference Bridge Type = Conference Bridge (WS-SVC-CMM).

MAC Address = MAC of CMM Int G1/0

Subunit = 2 (for media card 2)

Device Pool = an existing device pool

Maximum Capacity = 128

-------------------------

But CCM can't find the resource.

On CMM, also showing "not registered with CCM":

NOKCT1VG01A#sh sccp

SCCP Admin State: UP

Gateway IP Address: 10.132.26.67, Port Number: 2000

IP Precedence: 5

User Masked Codec list: None

Call Manager: 172.28.4.5, Port Number: 2000

Priority: N/A, Version: 3.1, Identifier: 1

Call Manager: 172.28.105.5, Port Number: 2000

Priority: N/A, Version: 3.1, Identifier: 2

Call Manager: 10.132.189.5, Port Number: 2000

Priority: N/A, Version: 3.1, Identifier: 3

Conferencing Oper State: ACTIVE_IN_PROGRESS - Cause Code: NOT_REGIS_WITH_CCM

Active Call Manager: NONE

TCP Link Status: NOT_CONNECTED, Profile Identifier: 1

Reported Max Streams: 128, Reported Max OOS Streams: 0

Supported Codec: g711ulaw, Maximum Packetization Period: 30

Supported Codec: g711alaw, Maximum Packetization Period: 30

Supported Codec: g729r8, Maximum Packetization Period: 30

Supported Codec: g729br8, Maximum Packetization Period: 30

Supported Codec: g729ar8, Maximum Packetization Period: 30

Supported Codec: g729abr8, Maximum Packetization Period: 30

Supported Codec: g723_6.3, Maximum Packetization Period: 30

Supported Codec: g723_5.3, Maximum Packetization Period: 30

Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30

Transcoding Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED

Active Call Manager: 172.28.4.5, Port Number: 2000

TCP Link Status: NOT_CONNECTED, Profile Identifier: 2

Reported Max Streams: 128, Reported Max OOS Streams: 0

Supported Codec: g711ulaw, Maximum Packetization Period: 30

Supported Codec: g711alaw, Maximum Packetization Period: 30

Supported Codec: g729r8, Maximum Packetization Period: 30

Supported Codec: g729br8, Maximum Packetization Period: 30

Supported Codec: g729ar8, Maximum Packetization Period: 30

Supported Codec: g729abr8, Maximum Packetization Period: 30

Supported Codec: g723_6.3, Maximum Packetization Period: 30

Supported Codec: g723_5.3, Maximum Packetization Period: 30

Supported Codec: t.38 fax, Maximum Packetization Period: 20

Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30

gogasca · ‎12-29-2006

When you configure the CFB in CCM.

CCMAdmin will automatically generate a name for CMM conference bridge.

You are using another name:

associate profile 2 register MTP0018b983f9aa

associate profile 1 register CFB0018b983f9a8

So please go to CCM Admin and check which is the device name for the CFB and fro the MTP

will be sth like this (MAC will change of course):

M020003feac9852 for MTP

C010003FEAC9853 for CFB

gwhuang5398 · ‎01-02-2007

I still couldn't get the CMM registered with CMM Admin. Here is what I have done. Can you tell me if I had something incorrect?

1. This is a new CMM in a new 6509. I configured both of them and all interfaces are up.

2. CMM has a media card in its slot 2. I configured it as conference bridge and media card 4 as transcoder.

3. The CMM also has a T1 PRI card but right now there are no live T1 circuits into it.

4. The CMM has a CCM group with 3 CCM hosts in it, one primary and 2 redundant. SCCP is shown as ACTIVE now.

5. I didn't configure CCM Admin to add the conference bridge and transcoder. I thought the CCM should be able to find the resources once they are registered. But CMM was not able to get registered. Here is CMM "sh sccp".

Conferencing Oper State: ACTIVE_IN_PROGRESS - Cause Code: NOT_REGIS_WITH_CCM

Active Call Manager: NONE

TCP Link Status: NOT_CONNECTED, Profile Identifier: 1

Transcoding Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED

Active Call Manager: 172.28.4.5, Port Number: 2000

TCP Link Status: NOT_CONNECTED, Profile Identifier: 2

6. Then I tried to insert the resources into CCM Admin, but the CMM still couldn't be found by the CCM Admin.

My question is: is it sufficient to just configure the CMM and let it to register with CCM on its own or do I need to configure bot CMM and CCM Admin at the same time? Is "no live T1 circuit" possibly a factor to cause the registration problem?

Thanks a lot

Gary

gogasca · ‎01-02-2007

You need to configure both CMM and CCM Admin at the same time. So CCM recognizes it as a valid device in its DB.

There's an option for auto-reg but discard it.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123limit/123x/123xy8/gtcmm.htm#wp1245747

gwhuang5398 · ‎01-03-2007

Thanks. I added CMM to the CCM Admin and they got registered with CCM.