<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.4.3">
</HEAD>
<BODY>
The Path module should now support the WebSocket transport.<BR>
<BR>
Regards,<BR>
<BR>
Peter<BR>
<BR>
On Wed, 2012-08-08 at 09:47 +0100, Peter Dunkley wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
Hi,<BR>
<BR>
I've added comments below...<BR>
<BR>
On Wed, 2012-08-08 at 10:16 +0200, Muhammad Shahzad wrote: <BR>
<BLOCKQUOTE TYPE=CITE>
1. try to forward registration requests to another registrar.<BR>
</BLOCKQUOTE>
There is no reason this won't work as long as you take the NAT-like issues into account. If it didn't work, then it won't have worked for the same reason that forwarding registers from a TCP client behind a NAT wouldn't work.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
2. try to make calls between a webrtc and non-webrtc client.<BR>
</BLOCKQUOTE>
This does work, but you have to make sure the client media stack supports the right set of options. If there is a problem here it is probably to do with RTCweb interworking - not WebSockets. I did a lot of testing with Boghe (<A HREF="http://code.google.com/p/boghe/">http://code.google.com/p/boghe/</A> ) which does support the right media options.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
3. try to send call from webrtc client to asterisk / freeswitch server to play e.g. some IVR, voice mail etc.<BR>
<BR>
</BLOCKQUOTE>
This will be a problem for the same reason as above.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
and many other scenarios, which all have one thing common, that is one or more sip servers behind kamailio, webrtc clients do not work at all. They work only and only if kamailio is the only SIP server on the server side, mostly because kamailio currently do not have neither PATH nor outbound support.<BR>
<BR>
</BLOCKQUOTE>
Kamailio does have Path support (<A HREF="http://kamailio.org/docs/modules/stable/modules_k/path.html">http://kamailio.org/docs/modules/stable/modules_k/path.html</A> ), but it may require a small update to work with WebSockets. Kamailio doesn't have Outbound support (yet), but there is a simple mechanism that means you can work without it (the example configuration for the WebSockets module contains this).<BR>
<BR>
When I tested I used the following scenarios:<BR>
* WebSocket client -> Kamailio -> WebSocket client<BR>
* WebSocket client -> Kamailio -> TCP client<BR>
* WebSocket client -> Kamailio -> TLS client<BR>
* WebSocket client -> Kamailio -> UDP client<BR>
* WebSocket client -> Kamailio -> SCTP trunk -> Kamailio -> WebSocket client<BR>
* WebSocket client -> Kamailio -> TCP trunk -> Kamailio -> WebSocket client<BR>
* WebSocket client -> Kamailio -> TLS trunk -> Kamailio -> WebSocket client<BR>
* WebSocket client -> Kamailio -> UDP trunk -> Kamailio -> WebSocket client<BR>
* WebSocket client -> Kamailio -> SCTP trunk -> Kamailio -> TCP client<BR>
* WebSocket client -> Kamailio -> TCP trunk -> Kamailio -> TCP client<BR>
* ... and so on<BR>
<BR>
I also did some testing with secure WebSocket connections. All worked for me.<BR>
<BR>
Regards,<BR>
<BR>
Peter <BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
_______________________________________________
sr-dev mailing list
<A HREF="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</A>
<A HREF="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</A>
</PRE>
</TD>
</TR>
</TABLE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>