Jingle Transport-Info Bad Request

I’m receiving a bad request when I attempt to send a transport-info Jingle request

This is the xml:

<iq to='fdsafdsafsdafsafccccc@conference.dev.jitsi.com/focus' id='bMv8a-129' 
    xmlns='jabber:client' type='set'>
    <jingle xmlns='urn:xmpp:jingle:1' action='transport-info' initiator='fdsafdsafsdafsafccccc@conference.dev.jitsi.com/focus' sid='2435304365836776448'>
        <content name='video' creator='responder'>
            <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1' ufrag='93460c25' pwd='01fc3387691741829ef662be278462e6'>
                <fingerprint xmlns='urn:xmpp:jingle:apps:dtls:0' hash='sha-1' required='true'>43:3C:A5:10:9B:51:AA:81:C8:10:0C:DD:56:09:59:78:17:68:0A:E3</fingerprint>
                <candidate foundation='387492857' component='1' protocol='udp' priority='1686085631' ip='205.250.3.35' port='59658' type='srflx' rel-addr='192.168.1.91' rel-port='59658' generation='0' network='1' id='Beey9bLUa3'/>
            </transport>
        </content>
    </jingle>
</iq>

This is the response:

<iq to='eda6c788-b21a-4dfc-afa9-18b3eda173fd@dev.jitsi.com/aa8e0eba-8b6d-413a-95cb-126bfbc36144' from='fdsafdsafsdafsafccccc@conference.dev.jitsi.com/focus' id='bMv8a-129' type='error'>
    <error type='modify'>
        <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    </error>
</iq>

I’ve compared this with what the browser sends when joining a Jitsi Meet conference and it appears to have all the same information.

I see nothing in the Jicofo logs with the stanza id.

I’m sending this after sending the session-accept

The SID matches the SID in the session-accept xml.

I’ve noticed that when I search for the ID of the transport-info message from the browser joining a jitsi meet conference, I don’t see that ID in Jicofo either.

In Jicofo logging properties I have:

.level=FINEST
net.java.sip.communicator.service.protocol.level=ALL
org.jitsi.impl.protocol.xmpp.level=FINEST
org.jitsi.impl.protocol.xmpp.colibri.level=ALL

What else can I enable to try and debug this further?

Disregard, was a mismatched SID