We are integrating WhatsApp Business Calling with ElevenLabs using SIP.

Our SIP configuration in WhatsApp Manager is:

SIP host: sip.rtc.elevenlabs.io SIP port: 5061 Request URI user parameters: empty

Meta is generating the SIP destination incorrectly.

The SIP INVITE received by ElevenLabs contains:

sip:+55XXXXXXXXXXX;[...]:5061;transport=tls

The expected Request-URI should be:

sip:[...]:5061;transport=tls

The issue is that ;transport=tls is being inserted into the user portion of the SIP URI:

+55XXXXXXXXXXX;transport=tls

instead of:

+55XXXXXXXXXXX

Because of this, ElevenLabs returns:

404 Does not match any SIP Trunks

ElevenLabs support confirmed that the SIP trunk is correctly provisioned on their side and that they cannot normalize the malformed URI.

Our request_uri_user_params field is completely empty.

Could someone from the WhatsApp Calling / SIP team clarify why Meta is appending ;transport=tls to the user portion of the Request-URI and how to configure the destination URI correctly?