CUCM conference

[mkouame17]

Hello Guys,

I hope everyone is doing good.

I would like to know how CUCM conference works.

When the conference is configured to use CUCM ressource and voice gateway ressource, which one it will use first?

How to make to conference use only voice gateway ressources when both is configure ?

Thanks

[Roger Kallberg]

What will be used first is set by the order of the MRG, media resource group, in the assigned MRGL, media resource group list. If you want to use the gateway CFB resources first you’d need to put them into a MRG and order that group higher in the list of MRGs in the MRGL that is assigned to the devices. This can be directly assigned to the device, but is more oftenly assigned to device pool that the device is associated with.

[mkouame17]

Thanks @Roger Kallberg for the answers, I will test it and let you know for the result.

Thanks

[mkouame17]

Hello @Roger Kallberg 

I try to modify the MRGL component but I still face the same issue.

I notice when I try to put or enable a conference calls, the calls drop 4 out 5 times.

Are there some tshoot commands which can help to detect the root cause ?

Based on capture , I got this message but it not really help to move forward:

Conference cannot be established between DN and CTI Route Point CAUSE_NETWORK_NOT_OBTAINABLE

 In case someone has already face this issue.

Thanks

[Roger Kallberg]

I’m not even sure if conference between a device and a CTI RP is even possible. Try out a simpler scenario first, ie a conference between two regular devices.

[mkouame17]

Hello @Roger Kallberg we are able to have a conference between 3 devises at least.

[Elliot Dierksen]

Do you get that error if you conference between several basic phone DN's? Leave PSTN and CTI route points out of the picture for now.

[mkouame17]

Hello @Elliot Dierksen I did not get this error between several basic phone DN's.

[Elliot Dierksen]

That is good news. I don't know why you would be conferencing with a CTI route point, that sounds like it isn't supported. Is there anything that isn't working now? If so, what is it and what are you trying to accomplish?

[mkouame17]

For compliant issue, we record each voice call session. And we should inform both called and calling peer that the call will be recorded.

The third party APP should put the called, calling and the media notification server in conference via CTI route point.

This is what I try to archieve.

Each time an outgoing call is place, the call is dropped when the calling pick up the call. As the notification server try to establish the conference.

[Elliot Dierksen]

I have no idea about why you can't conference to the CTI route point, but that appears to be a problem. What is that server? If you are trying to record, that would be a recording profile on the DN. That is how I would try to resolve that issue.

[mkouame17]

Yes, this is the issue I try to solve.

The server are Telisca recorder and Telisca notification recorder.

Is there a command on CUCM or voice gateway which can display the ressource attribution during conference establishment?

The record is only fine for internal call only, for external call when we associate notification recorder. It doesn't record the call 

[Elliot Dierksen]

I am still unsure what you mean by this statement: "The third party APP should put the called, calling and the media notification server in conference via CTI route point." Can you explain that further? I have seen several different recording platforms on CM, but none of the used CTI route points. Then you have the issue where CM states that you can't conference with a CTI route points.

Media and calls NEVER land on a CTI route point. A route point is just used for call control. As an example using CCX, the callers dial a CTI route point, but the call actually lands on a CTI port. Using CCE as an example, the callers dial a CTI route point (internal callers, external caller would go direct through CVP), and get a redirect to a pattern pointing to a SIP trunk. Maye that is why you can't conference with a route point because it never has the or media landing on it.