[sr-dev] Websocket module

[Muhammad Shahzad]

Yes, i do understand that there are still problems with media when bridging
calls between webrtc and non-webrtc clients, that's the bit i am still
working on. What i meant with not work with kamailio in all cases i have
previously mentioned is the signalling.

Anyways, its good to have PATH support finally added in web sockets
modules, good job, i appreciate it.

I am now looking forward to outbound support, i hope to see in Kamailio
soon.

Thank you.


On Wed, Aug 8, 2012 at 10:50 AM, Peter Dunkley <
peter.dunkley at crocodile-rcs.com> wrote:

> **
> The Path module should now support the WebSocket transport.
>
> Regards,
>
> Peter
>
>
> On Wed, 2012-08-08 at 09:47 +0100, Peter Dunkley wrote:
>
> Hi,
>
> I've added comments below...
>
> On Wed, 2012-08-08 at 10:16 +0200, Muhammad Shahzad wrote:
>
> 1. try to forward registration requests to another registrar.
>
> 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.
>
>  2. try to make calls between a webrtc and non-webrtc client.
>
> 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 (http://code.google.com/p/boghe/ ) which does support the right
> media options.
>
>  3. try to send call from webrtc client to asterisk / freeswitch server to
> play e.g. some IVR, voice mail etc.
>
>  This will be a problem for the same reason as above.
>
>
> 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.
>
>  Kamailio does have Path support (
> http://kamailio.org/docs/modules/stable/modules_k/path.html ), 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).
>
> When I tested I used the following scenarios:
> * WebSocket client -> Kamailio -> WebSocket client
> * WebSocket client -> Kamailio -> TCP client
> * WebSocket client -> Kamailio -> TLS client
> * WebSocket client -> Kamailio -> UDP client
> * WebSocket client -> Kamailio -> SCTP trunk -> Kamailio -> WebSocket
> client
> * WebSocket client -> Kamailio -> TCP trunk -> Kamailio -> WebSocket client
> * WebSocket client -> Kamailio -> TLS trunk -> Kamailio -> WebSocket client
> * WebSocket client -> Kamailio -> UDP trunk -> Kamailio -> WebSocket client
> * WebSocket client -> Kamailio -> SCTP trunk -> Kamailio -> TCP client
> * WebSocket client -> Kamailio -> TCP trunk -> Kamailio -> TCP client
> * ... and so on
>
> I also did some testing with secure WebSocket connections.  All worked for
> me.
>
> Regards,
>
> Peter
>
> _______________________________________________
> sr-dev mailing listsr-dev at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>     --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>


-- 
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +92 334 422 40 88
MSN: shari_786pk at hotmail.com
Email: shaheryarkh at googlemail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20120808/333ea595/attachment.htm>