Conferenced calls failing

[bkhanal1971]

I have a quick question regarding ad-hoc conference call issues in UCM 8.6.2 environment. Recently I have noticed a few instances of ad-conference calls failing while trying to add 3rd party in the call. I want to know where I should check to find out the root causes of such problems. If it is in RTMT, can someone tell me where exactly in RTMT I should be looking at and what I should be looking for?

Thanks

[yahsiel2004]

Have you verified that your conference bridges are registered? Have you tried resetting the IPVMS services?

Regards,

Yosh

[yahsiel2004]

In regards to searching through logs you would go under "Syslog Viewer" in RTMT and select a CUCM server and select application logs.

Regards,

Yosh

[bkhanal1971]

I am getting file does not exist error while trying to view application log through syslog viewer. Do I need to enable somethning somewhere?

[yahsiel2004]

You have to open the RTMT application with admin rights. Once you do that you will be able to view the Syslogs and be able to pull SDI traces.

In regards to the CODEC mismatch you will need to first verify that you can create a conference internally with 3 participants. If you can and your issue is with adding external participants and or adding users coming across a different "Region" then you will need to verify that you have transcoding and or MTP resources available to be able to setup calls between 2 different codecs.

Regards,

Yosh

[Jaime Valencia]

Id also check for codec mismatch

Sent from Cisco Technical Support iPad App

[bkhanal1971]

Where do i check for codec mismatch?

[Ayodeji Okanlawon]

Your best bet might be to gather cucm logs. Thats where you will knwo whats going on. If you collct CUCM SDI traces, I can help have a look

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[bkhanal1971]

Would you mind telling me what specif file/log I should be collecting  in order to get the SDI straces in RTMT? Also, I have 4 server UCM  cluster so do I need to select all 4 servers or the the one the phone in  question is having trouble doing the conference call?

Thank you,

[Ayodeji Okanlawon]

You should collect CUCM SDI logs from the servers the Phones affected are registered to. Make sure you have set your trace settings to detailed before collecting the logs.

When sending the logs include the calling number, called number, conferenced number and time of call

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[bkhanal1971]

Hi Aokanlawon:

A brief background of the issue. Here, a person with ext. 11179 attempted to intiate the 3 way conference calls around 9 am, all within same ucm cluster (one cluster, two locations and 2 ucm servers in each side connected with mpls link). The initiator of the call uses the voice dialing to dial the dn 18847. He answers the calls. After that the user dials the DN 121175.The person with DN 12175 picks up the phone and as soon as the confrn key is pressed, the call got disconnected.

I think i cannot attached the log files here which are in winrar archived format so i will try to email them directly to you.

Thank you for your help

BK

[Ayodeji Okanlawon]

You can use the advanced editor on the right hand side of each thread to attach files.


Sent from Cisco Technical Support Android App

[Ayodeji Okanlawon]

Do you have a conference bridge in the MRG of the phones. What type of CFB is it. Is it CUCM soft ware CFB? Nb: this can only support g711 conferences. Check the region setting between the phones and the one u are trying to conference in. If its g729, then you need a hardware CFB


Sent from Cisco Technical Support Android App

[bkhanal1971]

We have only software CFB in MRG. Other resources defined in MRG are software MTP and hardware xcoder. We use g.729 for intersite calls (defined in Region). If hardware CFB is required for g.729 conference calls, I don't know why it works most of the time without hardware cfb and fails only occassionally. But your point makes good sense that software CFB supports only g.711.

[Ayodeji Okanlawon]

It is possible that the ones working are phones in the same regions and are using G711. The call in the trace use G729, so Soft ware CFB wont work..You need IOS based hardware CFB.

The number that I saw called in the trace is not 121175 but 12175...

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"