Conferencing error

Unanswered Question
May 29th, 2008

Hi,

i am still having conferncing problem on cme. I donno if it is a miss configuration or something is missing.

attached is the config as well as error of show sccp

Good day

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
irisrios Wed, 06/04/2008 - 06:24

Please follow the instructions here to configure the conference.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a0080334294.shtml

Please make sure you have the voice card available/DSDP farm running on the CCM that the device name is matching since it is case sensitive. Do not use different cases for the same name when assigning pools to profiles.

Sushil Kumar Katre Wed, 06/04/2008 - 09:49

Hi,

I dont see "max-conferences max-conference-number" command under telephony-service.

Please add this command and then check..

Refer to the following URL for the complete configuration -

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeconf.html

If you have 4.1 or above running and want to configure multiparty ad-hoc conference follow the steps -

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeconf.html#wp1011144

-> Sushil

ashok_boin Wed, 06/04/2008 - 09:39

The CFB is failing to register with your CME as per the error. And on the other hand, transcoding service registered successfully with the same CME, so it's not network connectivity issue.

What's the config on your CME related with CFB and transcoding? Did you debug on your CME why it is declining the registration from this but allowing transcoding to get registered?

Regards...

-Ashok.

twissam Wed, 06/04/2008 - 09:46

all the config related to conf and transcoding is in the attached file nothing else is configured in this relation.

i am doughting the config under the telephony-service, i tried couple of scenario but i did not manage to make it work.

also i could not find any doc for such setup

Good day

twissam Wed, 06/04/2008 - 11:19

nothing is help.

I guess it must be an IOS issue, but unfortunalty i do not have another ios for this time.

c2800nm-ipvoicek9-mz.124-11.XW5.bin

i haven't configured conferening before i am not sure if it works on PVDM2

max-conference is already there by the way...

what i have tried even only conferencing with same results:

no sccp

sccp

with some debugs give me this results

*Jun 4 09:23:24.083: sym_xapp_xlate_rpm_codec: payload 5

*Jun 4 09:23:24.083: sym_xapp_xlate_rpm_codec: payload 16

*Jun 4 09:23:24.083: sym_xapp_transfer_supported_codec: supported codec cnt 5

*Jun 4 09:23:24.083: sccp_sym_set_secure_param:: appl profile 2 rpm device_mode 0appl device mode 0

*Jun 4 09:23:24.083: sym_xapp_new_rpm_profile_info: max_streams 8, prof_id 2, codec_cnt 2, iss 8, mspc 8, rsvp un-enabled

*Jun 4 09:23:24.083: sym_xapp_process_ccapi_events: minor is ZERO - should be non-zero for CCAPI event

*Jun 4 09:23:24.083: sccpapp_process_sys_events: sys_eve 3, xlated_eve 0

*Jun 4 09:23:24.083: sccp_get_ccm_group_using_assoc_prof: prof_id 2 found in the CCM group 1

*Jun 4 09:23:24.083: sccpapp_process_sys_events: prof_id 2, assoc to ccm_group 1,appl_type 3, sys_eve 3

*Jun 4 09:23:24.083: sccp_bring_up_appl_service: Trigger FSM for prof_id 2, appl_type 3

*Jun 4 09:23:24.083: sccp_connect_to_ccm_on_priority_basis: Trying connecting to CCM on priority basis prof_id 2, appl_type 3

*Jun 4 09:23:24.083: sccp_connect_to_ccm_on_priority_basis: Trying CCM with ipaddr 192.168.1.247, priority 1, port 2000

*Jun 4 09:23:24.087: sccp_appl_service_start_timer: Start timer type 1 with time_out 30000ms

*Jun 4 09:23:24.087: sccp_tcp_socket_connect: Trying tcp soc connect for appl_type 3, prof_id 2, to ipaddr 192.168.1.247

*Jun 4 09:23:24.087: sccp_tcp_open_and_set_option: Socket 0 opened and binded to ipaddr 192.168.1.247 - for appl_type 3, prof_id 2

*Jun 4 09:23:24.087: sccp_socket_connect_to_ccm :: connecting to port 2000 sccp_socket_connect_to_ccm: soc conn to 192.168.1.247 port 2000 in progressfor appl_type 3, state 1, soc_fd 0 appl 47108640

*Jun 4 09:23:24.087: sym_xapp_xlate_ccapi_eve: Unsupported ccapi eve 2

*Jun 4 09:23:24.087: sym_xapp_process_ccapi_events: Unsupported ccapi eve_id 2

*Jun 4 09:23:54.087: sccpapp_process_timer_events: appl_type 3, experied_timer 1, xlated_eve 2, state 1

*Jun 4 09:23:54.087: sccp_initiate_ccm_connect_interval_timer: Start CCM connect interval timer for prof_id 2, appl_type 3

*Jun 4 09:23:54.087: sccp_appl_service_start_timer: Start timer type 0 with time_out 10000ms

*Jun 4 09:24:04.087: sccpapp_process_timer_events: appl_type 3, experied_timer 0, xlated_eve 0, state 0

*Jun 4 09:24:04.087: sccp_connect_to_ccm_on_priority_basis: Trying connecting to CCM on priority basis prof_id 2, appl_type 3

*Jun 4 09:24:04.087: sccp_connect_to_ccm_on_priority_basis: Trying CCM with ipaddr 192.168.1.247, priority 1, port 2000

*Jun 4 09:24:04.087: sccp_appl_service_start_timer: Start timer type 1 with time_out 30000ms

*Jun 4 09:24:04.087: sccp_tcp_socket_connect: Trying tcp soc connect for appl_type 3, prof_id 2, to ipaddr 192.168.1.247

*Jun 4 09:24:04.087: sccp_tcp_open_and_set_option: Socket 0 opened and binded to ipaddr 192.168.1.247 - for appl_type 3, prof_id 2

*Jun 4 09:24:04.087: sccp_socket_connect_to_ccm :: connecting to port 2000 sccp_socket_connect_to_ccm: soc conn to 192.168.1.247 port 2000 in progressfor appl_type 3, state 1, soc_fd 0 appl 47108640

ashok_boin Wed, 06/04/2008 - 21:38

Yeah, I am not seeing any config mistake here.

From the debug provided, this is the error preventing the registration.

"Jun 4 09:23:24.087: sym_xapp_xlate_ccapi_eve: Unsupported ccapi eve 2

*Jun 4 09:23:24.087: sym_xapp_process_ccapi_events: Unsupported ccapi eve_id 2 "

So, it's giving "Unsupported ccapi" which may mean the IOS problem. Did you try same debug with Transcoding alone which should say "Supported ccapi" and get registered successfully.

Regards...

-Ashok.

twissam Fri, 06/06/2008 - 09:45

with the transcoding it is registering

*Jun 6 17:41:34.275: %SDSPFARM-6-REGISTER: mtp-1:MTP001319d27668 IP:10.10.1.254 Socket:1 DeviceType:MTP has registered.

i guess it must be that the confer is not supported on cme!!!

Good day

ashok_boin Mon, 06/09/2008 - 00:37

No, Conferencing is supported on CME.

The only thing to re-check about IOS.

Regards...

-Ashok.

Actions

This Discussion