[Spce-user] sipwise 3.1 (CE) and websocket support

[Ashutosh Apte]

Update on the websocket support issue:

I changed the following files (names and diff shown below), applied the
changes (ngcpcfg apply) and now I see that kamailio lb instance is
listening on the port specified in the config.yml file. It continues to
fail the same way though.

It looks like that the kamailio config teamplate now needs to be modified
to handle websocket related processing. Based on 3.0 release announcement (
http://www.sipwise.com/news/announcements/spce-v3_0-release/ ), I assumed
that sip:Provider CE would automatically configure the Kamailio LB for
websocket support. Is that not the case?


Can anyone please share a version of kamailio config and / or template that
not only works as websocket - SIP gw but also uses mediaproxy for media
transcoding?


sipwise at spce:/etc/ngcp-config$ sudo diff config.yml config.yml.orig
92,97d91
<     ws:
<       enable: 'yes'
<       port: 10080
<     wss:
<       enable: 'no'
<       port: 10081


root at spce:/etc/ngcp-config/templates/etc/kamailio/lb# diff kamailio.cfg.tt2
kamailio.cfg.tt2.orig
20,23d19
< [% IF kamailio.lb.ws.enable == "yes" -%]
< #!define ENABLE_WEBSOCKETS
< [% END -%]
<
52,54d47
< #!ifdef ENABLE_WEBSOCKETS
< listen=tcp:[% ip %]:[% kamailio.lb.ws.port %]
< #!endif
68,70d60
< #!ifdef ENABLE_WEBSOCKETS
< listen=tcp:[% ip %]:[% kamailio.lb.ws.port %]
< #!endif
248,255d237
< #!endif
<
< #!ifdef WITH_WEBSOCKETS
< # ----- nathelper params -----
< modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)")
< # Note: leaving NAT pings turned off here as nathelper is _only_ being
used for
< #       WebSocket connections.  NAT pings are not needed as WebSockets
have
< #       their own keep-alives.





On Tue, Feb 11, 2014 at 4:44 PM, Ashutosh Apte <apteashutosh at gmail.com>wrote:

> I've downloaded the sip:provider v3.1 (Virtualbox image) and have gone
> through the handbook to configure the system. But it seems that I've missed
> enabling websocket support.
>
> I can successfully register an endpoint using direct SIP but when I try to
> use jssip or sipml5, the connection establishment fails and the endpoint is
> never registered.
>
> I tried to compare a kamailio configuration file at
> https://gist.github.com/jesusprubio/4066845 with the one located
> at  /etc/kamailio/lb/kamailio.cfg but I cannot see a "listen" entry
> specifically for websockets. (I do see that it does load websocket.so)
>
> What is the default port on which sip:provider listens for websocket
> requests?
> (I tried pointing the javascript to port 80, 443, 1443, 5081 etc but they
> all fail with different response codes - XMLRPC Not allowed, 301 Moved
> Permanently etc)
>
> What change should I make to get the registrations working?
>
> Please help.
>
> Thanks,
> Ashutosh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140212/48db45d2/attachment-0001.html>