08-23-2024 03:27 PM
Hello everyone!
I configured a 3rd-party SIP device on CUCM and was able to make audio calls to CSF devices, but video calls are not working. From SIP traces, I found the below scenario:
1 - Invite from 3rd party to CUCM contain video attributes.
2 - After sending a 180 Ringing, CSF accepts with 200 OK, and video attributes are also present.
3 - When CUCM sends the ACK to CSF, there's video information under media. There's one section indicating the port for video, and another showing port 0.
4 - CUCM sends 200 OK to 3rd party, with information for media. This is the last packet I see with video attributes, the subsequent ones contain only audio.
In this call, audio worked fine but video failed for both sides.
On CCM traces, looking at media information, there's a section that shows PartyA (3rd party) with the correct IP address and port for audio. But for video, IP and port are set as 0.0.0.0:0.
PartyB (CSF) contains correct IP/ports for both audio and video.
I still can't figure out the reason why this change happens to the address/port.
Also on CUCM traces, I saw that after 3rd party sends a REGISTER message, there's a check for video parameter, that contains value 0.
Compared to a CSF device, that has value 1. Does anyone know what this check means?
I'm leaving the SDL traces, if anyone could help in this case, if already faced a similar problem.
08-23-2024 11:24 PM
What type of 3:rd party SIP device did you create in CM? From what I’ve seen on past posts on similar topics you’ll need to use advanced 3:rd party SIP device for video to work.
08-24-2024 01:53 PM
Hello Roger,
I created as advanced third-party SIP device.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide