Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

Intercluster Trunk Between Call Manager 6.1.3 and Call manager 4.1.3

We have a non-gatekeeper controlled intercluster trunk setup between a 6.1.3 cluster (clusterA) and a 4.1.3 cluster (clusterB). The phones and the Intercluster trunks in each cluster are in separate regions and the codec between these regions are set to G729. When I place a call from clusterA to device in clusterB the phone in clusterA is communicating using a G711 codec and the phone in clusterB is communicating using a G729 codec. If we use wireshark to look at this call we see a transcoding resource in clusterA involved in this call. When I place a call from clusterB to device in clusterA the phone in clusterB is communicating using a G711 codec and the phone in clusterA is communicating using a G711 codec. If we use wireshark to look at this call we see a transcoding resource in clusterA involved in this call.

When we setup a non-gatekeeper controlled intercluster trunk between two 6.1.3 clusters using the same configurations parameters, the calls no matter who initiates the call uses a G729 codec on both side with no transcoding resource involved.  Any ideas as to what could be causing this? 

1 REPLY
Silver

Re: Intercluster Trunk Between Call Manager 6.1.3 and Call manag

Hi,

This is just a guess, but the Intercluster trunks have proprietary Cisco "additions" for functionality.  Perhaps Cisco made changes between the versions and so they are not working predictably.  Just for fun have you tried checking the Require MTP on both ends?

Art

576
Views
0
Helpful
1
Replies
CreatePlease to create content