CCA 2 and Conference problems

Unanswered Question
Jul 27th, 2009
User Badges:
  • Bronze, 100 points or more

Setting up conferencing with cca2.01 is not working. While the configuration appears correct, we cannot get the conference to ever associate and any phone trying to establish a conference is welcomed with a wonderful "busy" tone or "conference cannot be initiated" on the phone screen.


Here are some show commands: Anyone have a thought on why this would happen and how to correct?


UC500 only - CCA issue


LA_UC500#sho dspfarm all
Dspfarm Profile Configuration

Profile ID = 1, Service = CONFERENCING, Resource ID = 1
Profile Description : DO NOT MODIFY, active CCA conference profile - CCA2.0 codec711
Profile Service Mode : Non Secure
Profile Admin State : UP
Profile Operation State : ACTIVE IN PROGRESS
Application : SCCP   Status : ASSOCIATION IN PROGRESS
Resource Provider : FLEX_DSPRM   Status : UP
Number of Resource Configured : 4
Number of Resource Available : 4
Codec Configuration
Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required


SLOT DSP VERSION  STATUS CHNL USE   TYPE    RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED

0    2   23.8.0   UP     N/A  FREE  conf   1      -         -         -
0    2   23.8.0   UP     N/A  FREE  conf   1      -         -         -
0    2   23.8.0   UP     N/A  FREE  conf   1      -         -         -
0    2   23.8.0   UP     N/A  FREE  conf   1      -         -         -

Total number of DSPFARM DSP channel(s) 4


LA_UC500#sho sccp all
SCCP Admin State: UP
Gateway IP Address: 10.10.2.254, Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.10.2.1, Port Number: 2000
                Priority: N/A, Version: 3.1, Identifier: 1
                Trustpoint: N/A

Conferencing Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED
Active Call Manager: 10.10.2.1, Port Number: 2000
TCP Link Status: NOT_CONNECTED, Profile Identifier: 1
Reported Max Streams: 32, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
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


SCCP Application Service(s) Statistics:

Profile Identifier: 1, Service Type: Conferencing
TCP packets rx 9, tx 18
Unsupported pkts rx 0, Unrecognized pkts rx 0
Register tx 9, successful 0, rejected 9, failed 0
KeepAlive tx 0, successful 0, failed 0
OpenReceiveChannel rx 0, successful 0, failed 0
CloseReceiveChannel rx 0, successful 0, failed 0
StartMediaTransmission rx 0, successful 0, failed 0
StopMediaTransmission rx 0, successful 0, failed 0
PortReq rx 0
PortRes tx 0, successful 0, failed 0
PortClose rx 0
QosListen rx 0
QosPath rx 0
QosTeardown rx 0, send 0, recv 0, sendrecv 0
QosResvNotify tx 0, send 0, recv 0, sendrecv 0
QosErrorNotify tx 0, send 0, recv 0, sendrecv 0
   err0 0, err1 0, err2 0, err3 0, err4 0, err5 0,
   err6 0, err7 0, err8 0, err9 0, err10 0, err11 0,
   err12 0
QosModify rx 0, send 0, recv 0, sendrecv 0
UpdateDscp rx 0
Reset rx 0, successful 0, failed 0
MediaStreamingFailure rx 0
MediaStreamingFailure tx 0
Switchover 0, Switchback 0

CCM Group Identifier: 1
Description: None
Binded Interface: NONE, IP Address: NONE
Associated CCM Id: 1, Priority in this CCM Group: 1
Associated Profile: 1, Registration Name: confprof1
Registration Retries: 3, Registration Timeout: 10 sec
Keepalive Retries: 3, Keepalive Timeout: 30 sec
CCM Connect Retries: 3, CCM Connect Interval: 10 sec
Switchover Method: GRACEFUL, Switchback Method: GRACEFUL_GUARD
Switchback Interval: 10 sec, Switchback Timeout: 7200 sec
Signaling DSCP value: cs3, Audio DSCP value: ef


Total number of active session(s) 0, and connection(s) 0


Total number of active session(s) 0, and connection(s) 0


Total number of active session(s) 0, connection(s) 0, and callegs 0

SCCP Application Service(s) Statistics Summary:
Total Conferencing Sessions: 0, Connections: 0
Total Transcoding Sessions: 0, Connections: 0
Total MTP Sessions: 0, Connections: 0
Total ALG-Phone Sessions: 0, Connections: 0
Total BRI-Phone Sessions: 0, Connections: 0
Total SCCP Sessions: 0, Connections: 0


Total active sessions 0, connections 0, rsvp sessions 0
Statistic                  Count
-------------------------  -----------
Send queue enqueue error   0
Socket send error          0
Msgs discarded upon error  0



****************************************************************************************

sho run commands:


stcapp ccm-group 1
stcapp
!
stcapp feature access-code
!
voice-card 0
dspfarm
dsp services dspfarm
!
sccp local Loopback0
sccp ccm 10.10.2.1 identifier 1
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register confprof1
!
dspfarm profile 1 conference
description DO NOT MODIFY, active CCA conference profile - CCA2.0 codec711
codec g711ulaw
codec g711alaw
maximum sessions 4
conference-join custom-cptone CCAjointone
conference-leave custom-cptone CCAleavetone
associate application SCCP
!
telephony-service
sdspfarm conference mute-on 111 mute-off 222
sdspfarm units 5
sdspfarm tag 1 confprof1
conference hardware

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Marcos Hernandez Mon, 07/27/2009 - 15:18
User Badges:
  • Blue, 1500 points or more

Can you modify this line:


sccp ccm 10.10.2.1 identifier 1


to:


sccp ccm 10.10.2.1 identifier 1 version 4.0


and then do a "no sccp" followed by "sccp".


Let me know if that works.


Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

MICHAEL JOHNSON Mon, 07/27/2009 - 15:26
User Badges:
  • Bronze, 100 points or more

no sccp ccm group 1
no sccp ccm 10.10.2.1 identifier 1
sccp ccm 10.10.2.1 identifier 1 version 4.0
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register confprof1
exit
no sccp
sccp



Thanks for the tip. I did the following commands and that appeared to correct the issue. Is this a known bug with CCA 2.0.1?

Marcos Hernandez Mon, 07/27/2009 - 15:29
User Badges:
  • Blue, 1500 points or more

Yes, and you are the lucky first finder ;-)


By the way, we did not know about this bug, so thanks.


We'll get this fixed in 2.1.


Marcos

Marcos Hernandez Mon, 07/27/2009 - 20:44
User Badges:
  • Blue, 1500 points or more

finalconnect,


I checked with our developers and we SHOULD be putting this keyword in the command already. You said you used CCA to configure 100% of the application, right? Can you describe the sequence of events a little more? Was this system using default configs?


Thanks a lot,


Marcos

MICHAEL JOHNSON Tue, 07/28/2009 - 08:11
User Badges:
  • Bronze, 100 points or more

We had this happen twice on two different systems. These are out of the box UC500 immediately upgraded to 7.0.3 via CCA 2.0 (not 2.0.1). No CLI was applied to the conference configuration. The basic summary of steps:


1) Unbox and turn up.

2) Use CCA 2.0 to upgrade UC500 firmware to v7.0.3 without using quick start.

3) Use CCA to design base configuration and configure base feature set on phones/extension/users.

4) Tweak CCA configuration with CUE GUI.

5) Finalize configuration with CLI.

6) Never go back to CCA or customized CLI gets trashed.



If that command is applied, something else strips to off later, and the only thing that could do that would be CCA.


We noticed this same problem in our lab system. Luckily, we don't typically demo conferencing during onsite demos. Thanks to your quick pointer, we have corrected the lab system as well.

Eivind Jonassen Tue, 07/28/2009 - 10:03
User Badges:
  • Silver, 250 points or more

Marcos,


I´ve just configured a 8 user model right out of the box. When I added the ad-hoc config within CCA the "version 4.0" was added to my config, and I´m using CCA 2.0.1 version, so this is not a common bug.


Regards

Eivind

Marcos Hernandez Tue, 07/28/2009 - 10:06
User Badges:
  • Blue, 1500 points or more

Correct. I recreated yesterday on my system and could not get it to fail. I am guessing the CUE out of band component is messing something up.


finalconnect, what exactly did you change with the CUE GUI?


Thanks a lot guys,


Marcos

MICHAEL JOHNSON Tue, 07/28/2009 - 10:17
User Badges:
  • Bronze, 100 points or more

Who knows. It could have been a dozen things. I find it hard to believe CUE would cause the problem, but I'm open minded.


One last thing, both demo and production system were 16u models not 8u.


When we get our next production system in the pre-config lab, we will try to watch the conference conf closer to figure out when it fails/changes.

MICHAEL JOHNSON Tue, 07/28/2009 - 10:20
User Badges:
  • Bronze, 100 points or more

Eivind,


Thanks for checking. If you play with the config more via CCA and make significant changes to the dial-plan and extension numbering, can you let us know if anything happens to the conference config?


We commonly have to change the IP scheme of the device and service module as well as extension numbering plan. That is when we really start to see issues with CCA.


Thanks again.

Eivind Jonassen Tue, 07/28/2009 - 10:46
User Badges:
  • Silver, 250 points or more

Well, I would love to plau around with dial-plans and stuff, but as you noticed I´ve put up a post regarding TSW and CCA 2.0.1, and after this setup I´m not able to play with the dial-plan in CCA

This is the first time I´m having trouble with CCA and the dial-plan changes though..


Regards

Eivind

MICHAEL JOHNSON Tue, 07/28/2009 - 10:26
User Badges:
  • Bronze, 100 points or more

Did you add any meet-me conferences to your base configuration? Our standard is to split the available evenly between meet-me and adhoc. It appears you only did adhoc - is that correct?

Eivind Jonassen Tue, 07/28/2009 - 10:40
User Badges:
  • Silver, 250 points or more

Only ad-hoc for this setup.


Whenever I change the IP plan not to use the default, I only use CCA for the inital setup, after that I never launch CCA again, to much hassle I´m afraid..

Well, actually, after the 2.0 release it´s not that bad actually, I was thinking back to my earlier deployments where I really struggled with CCA 1.8 and 1.9 (not so bad after 1.9.1) release.



Regards

Eivind