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

[Andrew Pogrebennyk]

Hi,
thanks, sufficient info collected. The issue is triggered by the Route
inserted by sipml5: Route:
<sip:172.18.101.48:5060;lr;sipml5-outbound;transport=udp>
I'll check what kamailio-lb should do in this case. But as a workaround
you can try disabling route or "outbound proxy" in sipml5 client.

> Feb 14 23:26:54 spce lb[3773]: DEBUG: websocket [ws_frame.c:589]: ws_frame_receive(): Rx SIP message:
> ACK sip:ngcp-lb at 172.18.101.48:5060;ngcpct=7369703a3132372e302e302e313a35303830 SIP/2.0
> Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bKPLN9elJsPlfeyLsMqN2J;rport
> From: "4252143385"<sip:4252143385 at 172.18.101.48>;tag=RtycJXR6JIUFzAezAbRX
> To: <sip:2067077495 at 172.18.101.48>;tag=1F9894DE-52FE982E000437E0-321A4700
> Contact: "4252143385"<sip:4252143385 at df7jal23ls0d.invalid;rtcweb-breaker=yes;click2call=no;transport=ws>;+g.oma.sip-im;+sip.ice;language="en,fr"
> Call-ID: 1bff80ac-1e47-ab0f-3ea4-6a7b8637030b
> CSeq: 43084 ACK
> Content-Length: 0
> Route: <sip:172.18.101.48:5060;lr;sipml5-outbound;transport=udp>
> Max-Forwards: 70
> Proxy-Authorization: Digest username="4252143385",realm="172.18.101.48",nonce="Uv6ZWVL+mC3kkbBLeaVF0E1fvkGRSU0m",uri="sip:ngcp-lb at 172.18.101.48:5060;ngcpct=7369703a3132372e302e302e313a35303830",response="c145f2a14437257dc33fca9c83e230b6",algorithm=MD5
> Route: <sip:172.18.101.48;transport=ws;r2=on;lr=on;ftag=RtycJXR6JIUFzAezAbRX;nat=yes;ngcplb=yes;socket=ws:172.18.101.48:5060>
> Route: <sip:127.0.0.1;r2=on;lr=on;ftag=RtycJXR6JIUFzAezAbRX;nat=yes;ngcplb=yes;socket=ws:172.18.101.48:5060>
> Route: <sip:127.0.0.1:5062;lr=on;ftag=RtycJXR6JIUFzAezAbRX;did=117.fcb;mpd=ii;ice_caller=replace;savp_caller=force_srtp;avpf_caller=force_avpf;ice_callee=strip;savp_callee=force_rtp;avpf_callee=force_avp;rtpprx=yes;vsf=ampNeU9nS3R6XXJyQ2QgJVJTaiZjfFJ4S35Wf0E->
> User-Agent: IM-client/OMA1.0 sipML5-v1.2014.01.27
> Organization: Doubango Telecom
> 
> Feb 14 23:26:54 spce lb[3773]: DEBUG: rr [loose.c:778]: after_loose(): Topmost route URI: 'sip:172.18.101.48:5060;lr;sipml5-outbound;transport=udp' is me
> Feb 14 23:26:54 spce lb[3773]: DEBUG: rr [loose.c:862]: after_loose(): URI to be processed: 'sip:172.18.101.48;transport=ws;r2=on;lr=on;ftag=RtycJXR6JIUFzAezAbRX;nat=yes;ngcplb=yes;socket=ws:172.18.101.48:5060'
> Feb 14 23:26:54 spce lb[3773]: DEBUG: rr [loose.c:871]: after_loose(): Next URI is a loose router
> Feb 14 23:26:54 spce lb[3773]: DEBUG: rr [rr_cb.c:97]: run_rr_callbacks(): callback id 0 entered with <lr;sipml5-outbound;transport=udp>
> Feb 14 23:26:54 spce lb[3773]: DEBUG: siputils [checks.c:106]: has_totag(): totag found
> Feb 14 23:26:54 spce lb[3773]: DEBUG: rr [loose.c:974]: check_route_param(): params are <;lr;sipml5-outbound;transport=udp>
> Feb 14 23:26:54 spce lb[3773]: INFO: <script>: Reset loose-routing, du='sip:172.18.101.48;transport=ws;r2=on;lr=on;ftag=RtycJXR6JIUFzAezAbRX;nat=yes;ngcplb=yes;socket=ws:172.18.101.48:5060' - R=sip:127.0.0.1:5080 ID=1bff80ac-1e47-ab0f-3ea4-6a7b8637030b



On 14/02/14 23:33, Ashutosh Apte wrote:
> Hi Andrew,
>     Thank you for the quick turn-around. I followed your instructions
> and collected logs. The attached .zip file also contains javascript
> console logs for sipML5 in case they are of any use.
> 
> Let me know if you need anything else. I'll be happy to test.
> 
> Thanks again,
> Ashu
>