Cisco Meeting Server configured as Conference Bridge on CUCM but unable to have 3 way video Adhoc conference

[Harikrishna Ojha]

Hi all,

I have setup a UAT setup for CUCM 11.5 and CMS 2.1.3. 

I have configured conference bridge as Cisco meeting server. I have also updated Call Bridge and CUCM internal CA signed cert on the call manager and CMS as instructed on the white paper. 

The SIP trunk is configured with encryption and SRTP. Conference Bridge registered with CUCM. 

However , when I try to establish the ad hoc conference between 3 party , only two side gets the video conference and one only connects using audio in the conference.

Kindly advice what could be the issue.

Regards,

Hari

[Jaime Valencia]

What does the calls look like in CMS?

What does the logs say?

[Harikrishna Ojha]

Hi Jamie 

The error is related to some miss match of the payload. There is no request for screensharing however it is still shows error related to BFCP.

The call does get establish as per the CMS logs however gets below error. 

Regards,

Hari 

2017-06-21 01:50:43.239 Info call 28: ending; local teardown, timed out - connected for 1:00
2017-06-21 01:50:48.057 Info call 29: incoming encrypted SIP call from "sip:5002@xxx.xxx" to local URI "sip:2110@cms01.xxx.xxx:5061"
2017-06-21 01:50:48.060 Info call 29: setting up UDT RTP session for DTLS (combined media and control)
2017-06-21 01:50:48.078 Info call 29: compensating for far end not matching payload types
2017-06-21 01:50:49.112 Info call 29: BFCP (client role) now active
2017-06-21 01:50:49.119 Info call 29: BFCP (client role) now active
2017-06-21 01:50:52.071 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:52.071 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:50:52.078 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:52.078 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:50:53.037 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:53.037 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:50:53.046 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:53.046 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:50:59.112 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:59.112 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:50:59.124 Info call 29: non matching payload types mode 1/0
2017-06-21 01:50:59.124 Info call 29: answering offer in non matching payload types mode
2017-06-21 01:51:00.131 Info call 29: non matching payload types mode 1/0
2017-06-21 01:51:00.131 Info call 29: answering offer in non matching payload types mode

[Jaime Valencia]

What endpoints are you using?

[Harikrishna Ojha]

Its all Jabber client , they are registered internally no remote access involved. No other device other than Jabber Andriod for the below scenario.

Jabber android client 1

User  UC Officer 1

Extension 5001

Jabber android client 2

User UC Officer 2

Extension 5002

Jabber android client 3

User UC Officer 3

Extension 5003

Call Scenario (all using jabber android client)

User 1 calls users 2 and establishes the call then press conference button on the phone to dial 5003.

User 2 and User 3 has two way video established and User 1 gets only audio from all the party (no video for user 1 ).

It’s Ad hoc conference , CMS is registered as conference bridge.  CUCM also has a secured SIP trunk to CMS , there is no issue in reachability.

CMS 2.1.3  is a single combined server where call bridge , xmpp , web bridge all are in the same node.

[Jaime Valencia]

No idea about that, I just released a video with this integration and I used an Android device for the tests and had no issues, I'd probably try with some other endpoints and try to find out if this is specific to android or not.

[Harikrishna Ojha]

Hi Jamie ,

Thanks , I have seen your video. Quite useful. 

I have tried with Andriod and Windows. Only Andriod jabber client has this issue. there is no issue with windows jabber endpoint. 

Every time cucm tries to send sip invite for a video conference initiated by Androd endpoint  , it sends m=video 0 , there is no RTP port. So still working to find the solution. 

Has anyone tested only with Jabber Andriod endpoints ? 

Regards,

Hari 

[Jaime Valencia]

Does calls from Android work fine to any other video endpoint?

Direct calls?

[Harikrishna Ojha]

I found out the cause of the issue , there is it was DTMF reception required option checked due to which MTP was invoked for Video. After removing it for Andriod BOT devices , 3 party video conferencing worked successfully.

Thanks Jamie , appreciate your help.