How to disable IX in Jabber ?

[almadacom]

Hello Community,

All Jabbers in our clusters are configured to allocate TRPs. We noticed that each time a jabber places an internal call we consume twice the amount of necessary TRP (8 connections instead of 4).

After some digging, we found that it is related to the Jabber initial Invite which comes with a second mline >>m=application 59838 UDP/UDT/IX *. The point is that we haven't found a way to disable this feature.

Since it sounds related to a cvideo conference feature, What we tried so far:

- disable jabber video

- disable enhanced ad hoc conference in service parametres

- Empty immersive and video Bandwith in Regions

FYI CUCM 15 and Jabber 14.

If anyone has an idea on how to diable IX, please answer.

Thanks

./WM

[almadacom]

Forgot to mention, IX is disabled in the SIP profile associated to jabber enpoints

[Jonathan Schulenberg]

Does that same SDP early offer from Jabber include video as well?

[almadacom]

Hello

Nope Video is disabled at Product specific level on all jabber device.

OPUS is clusterwide disabled in service parameters.

The Jabber EO SDP contains one mline for Audio and another mline for IX.

[almadacom]

[hafid salil · Accepted solution]

After openning a tac case >> It was an undocumented parameter

Steps to Disable iX Configuration for Jabber:

1. Access the Jabber Configuration Files

Locate the jabber-config.xml file used in your Jabber deployment.

This file contains the configuration settings for Jabber clients.
The file is typically hosted on your CUCM TFTP server or in a central location where Jabber retrieves its configuration.

1. Modify the EnableIX Parameter

Open the jabber-config.xml file using a text editor (e.g., Notepad++ or any XML editor).
Search for the <EnableIX> parameter. If it is not already present in the file, you can add it under the <Policies> section.
Set the value of <EnableIX> to false to disable the iX capability.

Example:

xml
Copy Code
<Policies>
<EnableIX>false</EnableIX>
</Policies>

1. Save and Upload the Updated Configuration

Save your changes to the jabber-config.xml file.
If the file is hosted on the CUCM TFTP server:
Upload the updated jabber-config.xml file to the CUCM TFTP server using the CUCM web interface.
Navigate to Cisco Unified OS Administration → TFTP File Management → Upload the updated XML file.
Restart the TFTP service on the CUCM server to ensure that clients download the updated configuration.

1. Verify the Configuration on the Client Side

After making the changes, restart the Jabber client to apply the new settings.
You can verify whether iX has been disabled by checking the behavior of the calls and ensuring there is no additional MTP allocation for iX media capabilities.

Why Disable EnableIX?

The <EnableIX> parameter is set to true by default in Jabber 14.3.0.58392.

When enabled, it allows Jabber to support iX media capabilities, which can trigger the allocation of Media Termination Points (MTPs) during calls.
Disabling this setting (false) prevents unnecessary consumption of MTP resources,

which is especially useful in environments where MTP resources are limited.

Additional Notes

CUCM Version Compatibility:

Ensure that your CUCM version is compatible with Jabber 14.3.0.58392. The process of modifying the jabber-config.xml file may vary slightly depending on your CUCM version.
Testing:

Test the updated configuration in a controlled environment to ensure no unintended side effects on call behavior or media handling.
Fallback:

If any issues arise, revert the <EnableIX> parameter to true or restore a backup of the original jabber-config.xml file.
Client Updates:

Ensure all Jabber clients are configured to download the updated configuration file from the server. You can force a client to reload settings by clearing its local configuration cache

[Roger Kallberg]

Great find and thank you for sharing the resolution. If not known in current versions of CM the Jabber configuration “file” can be managed directly in the CM admin webUI. This makes the process of this much more straightforward as you do not need to handle an actual file or restart any services when making changes and you’d also get a better overview as it’s all shown in the webUI.