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
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.
Thanks Craig (irc:dexteruk)
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/301#issuecomment-53397784
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
