testing Kamailio as WebSocket Server by sipML5

[Billy Yu]

Hi there,

I'm currently trying to test Kamailio as a websocket server.
In the expert view of sipML5 http://sipml5.org/expert.htm, I put the field of WebSocket Server URL=ws://<ip:port of kamailio> and SIP outbound proxy URL=udp://<ip:port of kamailio> and the port for UDP is not the same as for WebSocket.
I have a kamailio server with websocket support running.

However I got an error in sipML5.org/call.htm that failed to connect to the server.
From kamailio log file, I read that
DEBUG: <core> [forward.c:462]: check_self: host != me 
As my understanding, I did not set it correctly for messages received over websocket  to be forwarded to outbound proxy.
Without making DNS changes to support our realm, is there any way to set it through?
Or is it possible to use kamailio as a websocket server and a outbound proxy?

I'm new to this field. Sorry for my ignorance!
Best,
Billy

[BIlly Yu]

Hi Jack,

 

Thanks for reply!

I did set a different port for websockets.

 

The problem is that, even I set the ws port to 10060 and set it in the firewall, I still have the same problem, in kamailio log file:

 

DEBUG: <core> [forward.c:462]: check_self: host != me.

 

during the host checking in grep_sock_info, it showed that:

checking if host==us: 13==14 && [IP1] == [IP2]

where IP1 is the public IP address of my kamailio server and IP2 is the local IP address of my kamailio server. May I ask if I set it wrongly?

 

If I remove this ws setting, I can register to kamailio while grep_sock_info shows that

 - checking if host==us: 18==14 && [realm] == [IP2]

where realm is set in sipML5 and kamailio.cfg. IP2 is the local IP address of my kamailio server.

Could you please give any advices?

On Tue, Jun 11, 2013 at 11:59 PM, Jack Ring <jack...@gmail.com> wrote:

In your kamailio config, did you specify a different port for web sockets?

In my config I set the ws port to 10060 then had to open the port in the firewall. 

I am able to connect to kamailio with websocket server set to ws://<IP>:10060 no outbound proxy, ICE Server set to [{url:'stun:stun.ekiga.net'}] and  Enable RTCWeb Breaker checked. 

I can make calls between Chrome browsers. Now If I could just get it to call bria....

Jack

--
You received this message because you are subscribed to a topic in the Google Groups "discuss-doubango" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/doubango/ZPlhQvWx5w0/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to doubango+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mamadou DIOP]

This is more a question to ask on Kamailio dev-group. I have seen several projects based on SIPML5 working with Kamailio and I think it's just a configuration issue.

You received this message because you are subscribed to the Google Groups "discuss-doubango" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doubango+u...@googlegroups.com.

[Alexandre GOUAILLARD]

thanks,

we are positive this is a configuration problem, and we will ask about the kamailio config part on their mailing list. 

Now, that being said, what we would like to do is the following setting:

sipml5 <-> webrtc2sip <-> kamailio  with rtcbreaker on.

In such configuration, we are unclear about which address / port should go in the "web socket server URL" and "sip outbound proxy url" settings in the expert mode page.

To be honest, those settings, even with the footnotes, are very confusing and a little drawing or two to illustrate would be greatly welcome.

regards,

alex

[aub...@presenceco.com]

Hi there,

I'm testing with sipml5 and Kamailio with web sockets support enabled and I have a problem to receive calls from an Asterisk PBX. Browser shows a rejected call error.

Instead, calls made from the same browser work fine.

In the browser console I get the following error:

1. This/PeerConnection is null: unexpected SIPml-api.js?svn=179:1
1. tsk_utils_log_errorSIPml-api.js?svn=179:1
2. tmedia_session_jsep01.onIceCandidateSIPml-api.js?svn=179:3
2. o_pc.onicecandidate
   
   
   Best,
   Agustí
   

[Mamadou DIOP]

You should not cut your logs when reporting an issue.