09-27-2015 11:52 PM - edited 03-18-2019 05:02 AM
Hi,
We have tried to integrate the Cisco CUCM 10.5 with the Avaya Session Manager via SIP Trunk.
We see that Cisco IP Phones are able to make voice calls fine to the Avaya phones but Cisco 8945 IP Phone registered as SIP device is not able to make Video calls to Avaya phones.
We see that the Avaya phone receives the video for 12secs and then it goes blank. The Cisco phone also shows the 'self view' as blank.
We did few troubleshooting and we see that Cisco 8945 is able to make Video calls to Avaya soft phones
The difference we see in Wireshark is that for Calls to soft phones, CUCM is sending SDP video payload type as 97 and for calls to hard phones payload type sent is 126 (Not working) in SDP.
Is there any way where we can customize this Payload type in SDP to force it to send 97 for calls to Avaya Hard phones ?
Any ideas would be highly appricated
Thanks !
09-28-2015 04:56 PM
On the Cisco end this is done by means of regions, with video, the region setting defines the bandwidth that will be used for a particular call between regions.
so on your CUCM system, the SIP trunk that points to your avaya system will be in a region (say region A). your originating phone is in yet another region (say region B).
the video bandwidth settings between region A and region B, dictate what codec/bandwidth will be used towards your Avaya system. This bandwidth can be seen in your SDP as TIAS=xxxxxxxx.
You will need to tweak the region bandwidth settings.
10-27-2015 12:19 AM
Hi Dennis,
Looks like it was a bug on the 8945 IP Phone and TAC has released a custom firmware for the IP Phone after which it is working fine.
Below is the summary I received from TAC.
Problem Description:
=================
Video fails from 8945 across to Avaya system.
CUCM 10.5.2
Analysis:
======
DE has confirmed this to be a new defect on the 8945 Phones:
CSCuw26305 8945 does not send video to Avaya phone until hold/resume
https://tools.cisco.com/bugsearch/bug/CSCuw26305/?reffering_site=dumpcr
A new defect has been raised for the same and a private load has been built which we have confirmed has fixed the issue.
Thanks !
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: