Correct, Even though the IM-Conf creation is basically SIP Routing, this is a special (OMA std. defined IM Conf extension on server ) extension just like Presence Module. it is not the work of a SIP Routing Core of a generic sip router or proxy. Is there any road map for this. I see a email string last year Aug 2008, about the IM Conf Module and Bogdan replied to it. Wondering if that went any furthur ?<br>
<br>Thank you<br><br><div class="gmail_quote">On Mon, Nov 2, 2009 at 2:54 PM, Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
El Lunes, 2 de Noviembre de 2009, Manivasagam Sivaraman escribió:<br>
<div class="im">> It is not exactly a SIP Proxy's job, but rather a IM Server's (Messaging<br>
> Server) Job. The Proxy Server should help in establishing the IM<br>
> Conference. It is a procedure defined in OMA IM Conference package. The<br>
> initiating UA will send an INVITE with a special xml payload Content Type<br>
> "application/resource-lists+xml" in addition to the SDP. The<br>
> Proxy/IM-Server up on receiving this INVITE will proxy the INVITE to all<br>
> registered UA found in the resource-lists xml that was received in INVITE.<br>
> All the UAs who are referred will then send INVITE and join in the IM<br>
> Conference that was created by the originating IM UA. The media is done<br>
> using MSRP and MSRP relay independent of the Proxy Server. The<br>
> Proxy/IM-Server only help in establishing the SIP IM-Conference. No media<br>
> will be handled by the proxy as in case of any other conf/session. ALl the<br>
> IM/Proxy server that supports IM -COnf will have a predefined Ad-Hock IM<br>
> COnf URI like "<a href="mailto:IMConf@opensips.com">IMConf@opensips.com</a>". All IM COnf will gets established by<br>
> sending INV to this special URI.<br>
<br>
</div>Interesting. However I really think that inspecting the request body is always<br>
a task of a server rather than a proxy. I'd really would prefer having a<br>
specific server for that. But perhaps it could be a opensips module to<br>
implement it (as there are presence server modules).<br>
<font color="#888888"><br>
<br>
<br>
--<br>
</font><div><div></div><div class="h5">Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>