<p>Because in this case we are talking to a SIP Video Conferencing Services, it creates two sets of Custom Params, the first is a confid= which is a refence for the MCU for the current conference session, as stated above confid=3FD99511F9EB238C3FE825FF752847D1, the second part which is standard for all SIP conferencing services is they pass a isfocus as part of the Header that allows conference-aware user agent that supports the conferencing call control conventions</p>
<p>But as you see with this MCU it passes a couple of params in the contact header ;+com.avistar.confapi.v1;isfocus which are outside the <> and the config= that is inside the <> for the UAC to function it needs to receive all this information, from what i can see this is a typical method of operation for conference-aware UAC and SIP Conferencing services.</p>
<p>Thanks Craig (irc:dexteruk)</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/issues/301#issuecomment-53397784">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyNDY2NTcwNSwiZGF0YSI6eyJpZCI6Mzk1NTkwODN9fQ==--7abbfd49e62c07a4da20d9d23416896707ba1ab5.gif" width="1" /></p>