CMS Conference Problem (no Video)

[mohamedgiumazwali]

Hi All!

I 've been configuring CMS 2.8  for a customer everything registered , looks fine but the problem is when making a video call between 3 participant there is no  video just audio and sometimes the  conference disconnect.

In the CMS logs , I received the following messages :-

INFO : compensating for far end not matching payload types

INFO : sending prompt response (2) to BFCP message

INFO : call 59: receiver report 1 interval for r x video 0 = 6865ms (period 6859ms) 00000000
INFO : call 60: receiver report 1 interval for r x video 0 = 6884ms (period 6875ms) 00000000

INFO : call 58: ending; local teardown - connected for 1:00
INFO : call 58: destroying API call leg b3c04f1f-1087-4c00-91ae-00f54b6a1f94
INFO : conference 0922f3f6-149c-4526-b4a3-90b4a0779b37 destroyed
INFO : call 58: follow-up single codec offer received
INFO : call 58: non matching payload types mode 1/0
 INFO : call 58: answering offer in non matching payload types mode
: INFO : call 58: sending response to single-codec additional offer

End Points Used for test:- 

SX10

SX80

MX700

IP Phone 9971

Anybody could help!

And thanks.

[mohamedgiumazwali]

Any thing  guys , even hints could help or suggestions. 

[Sateesh Katukam]

Hello, 

You can check following

1. If you are making an adhoc conference (with 3 endpoint registered to CUCM), make sure that CMS is registered as conference bridge and appropriate MRGL and MRG's are configured and assigned to endpoints. 

2. Make sure that no transcoders are invoked in CUCM for this call,  this will make video call as audio. transcoders can invoke because of DTMF mismatch. set "no preference" for DTMF Signaling Method on CMS sip trunk. 

3. Video bandwidth is assigned between the locations. 

4. Appropriate SIP profiles are assigned to endpoints and CMS SIP trunk. (Standard SIP Profile For TelePresence Endpoint and Standard SIP Profile For TelePresence Conferencing )

hope this helps

[mohamedgiumazwali · Accepted solution]

Thanks for your reply , the problem was related to firewall blockig of call bridge ports and also port 4000 UDP , cisco TAC team solved this problem.