Hello,
I am considering to release kamailio v4.0.2 next week on Wednesday, June
12. Developers that committed fixes on master branch and should be
backported, have to do it before. Overall, everyone should keep an eye
and be sure their demanded fixes are backported.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
Module: sip-router
Branch: 4.0
Commit: 81b61679cabd2470becf86700b777cc496f1d330
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=81b6167…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Wed Jun 12 09:11:56 2013 +0200
mtree: use debug level for log message when invalid character in value to be matched
- more verbose message when an invalid database record is found
---
modules/mtree/mtree.c | 284 ++++++++++++++++++++++----------------------
modules/mtree/mtree_mod.c | 166 +++++++++++++-------------
2 files changed, 226 insertions(+), 224 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=81b…
Hi,
I've read this discussion from the link
http://lists.sip-router.org/pipermail/sr-dev/2012-August/016161.html.
I got a similar problem.
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.
I read from the kamailio log file and found the error like this:
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?
In sipML5, I put ws://public_IP_kamailio:8080.
If I remove this ws setting and use kamailio as outbound proxy only, 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.
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?
Could you please give any advices?
I'm new to this field. Sorry for my ignorance!
Best,
Billy
--
View this message in context: http://sip-router.1086192.n5.nabble.com/websocket-testing-in-kamailio-tp119…
Sent from the Development mailing list archive at Nabble.com.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#313 - DNS failover bugs
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hi Daniel,
no, I do not have a multi-homed environment. In case the script writer does not force a send socket, the following happens in src
- for original request, the receiving socket is being used as send socket
- for failover request, no specific send socket stated (just 0) => kamailio uses the first listen socket => a different one than before, if the request was not received on the first listening socket. I fixed dns failover to use the received socket.
I attached patches for 4.0 and master.
Jasmin
----------
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=313#comment947
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.