Module: sip-router
Branch: master
Commit: b5132f217f521872fb0a6a4ab215443a700bab6f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b5132f2…
Author: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Committer: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Date: Mon Aug 13 15:45:20 2012 +0100
modules_k/usrloc: Downgraded a WARN to INFO
- When Kamailio loads a contact binding whose socket is not local a
warning is printed. Unfortunately, this happens a lot on multi-server
systems and it is not something to worry about.
- The end result is a huge number of warnings that swamps log messages
relating to real problems.
- So downgrading to INFO.
---
modules_k/usrloc/udomain.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/modules_k/usrloc/udomain.c b/modules_k/usrloc/udomain.c
index cf7807e..c676111 100644
--- a/modules_k/usrloc/udomain.c
+++ b/modules_k/usrloc/udomain.c
@@ -318,7 +318,7 @@ static inline ucontact_info_t* dbrow2info( db_val_t *vals, str *contact)
}
ci.sock = grep_sock_info( &host, (unsigned short)port, proto);
if (ci.sock==0) {
- LM_WARN("non-local socket <%s>...ignoring\n", p);
+ LM_INFO("non-local socket <%s>...ignoring\n", p);
}
}
Personally, I would say that it is not in the interest of the project to scatter focus away from itself, while further confusing newbies and in general making the "marketing message" less coherent.
That effort would be better spent on making Kamailio more user-friendly and/or easily deployable for trivial scenarios and small-scale, narrow purposes--if that's a priority for the project. Whether it even should be a priority deserves some rational discussion, since that may not be where Kamailio is strongest, just by design. The goal of a project should be to try to succeed in the game most appropriate for its character, and one which best aligns with the vision behind it.
-- Alex
--
Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:Personally I haven't used repro, so I cannot give relevant comments on it.
Cheers,
Daniel
On 8/5/12 11:25 PM, Daniel Pocock wrote:
>
>
> I've recently been doing some improvements to reSIProcate and it's SIP
> proxy, `repro'
>
> http://www.resiprocate.org/About_Repro
>
> It may appear to be a competitor for Kamailio - but a closer look at it
> reveals some interesting possibilities:
>
> a) the config file is less flexible than Kamailio - but this makes it
> extremely easy to set up. This makes it an ideal stepping stone for
> people who are not ready for Kamailio
>
> b) for Kamailio to really become widespread depends on a wide community
> of sites running SIP proxies - repro appears to be a solution that can
> be used to activate many public SIP servers very quickly, creating a
> world where everyone speaks Kamailio's language
>
> I'm curious to get some feedback about
>
> - have other people involved with Kamailio (and related proxies) had any
> exposure to reSIProcate already?
>
> - making repro and Kamailio work well together (ideally using DNS SRV
> and TLS with domain certificates/federated VoIP) - test cases? public
> test servers?
>
> - promoting the two proxies together, repro as the beginner solution,
> Kamailio as a strategic option for people who need more flexibility -
> does anyone feel comfortable with this concept?
>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hello,
I am looking to export $timef PV to the db_use_table acc / module
parameter.
I've been looking through source and it seems Line 390 under
modules_k/acc/acc.c is where this "fixup" is happening at a higher level.
It looks like fixup_var_pve_str_12 should be called for the 2nd parameter?
I'm having a difficult time tracking the flow between acc -> srdb1 and PV
for what I would imagine would be a rather simple modification.
Is there any online documentation for such cases to more familiarize myself
with the inner workings.
Thank you for all help / insight in advance!
Sincerely,
Brandon Armstead
Hello guys,
I wrote a module for credit control which aims to tear a call down when
client's credit is over. The problem is that I started writing it when Kam
3.3 was not out yet, and today, when I tried to use it with the latest
stable release, I found out that it wasn't working because, somehow, the
header fields are displaced.
Considering this code:
*LM_ALERT("Message CID: %.*s", msg->callid->body.len, msg->callid->body.s);*
when I try to read the Call ID hdr field in *3.2* I get the right reading:
ALERT: cnxcc [cnxcc_mod.c:807]: Message CID: *
vqsxmovczhwztpa(a)carlosrdcnx-laptop.site*
*
*
but if I do the same on *3.3*, with the same code (and recompiled for 3.3
of course) I get the Via hdr field.
ALERT: cnxcc [cnxcc_mod.c:807]: Message CID: *SIP/2.0/UDP 127.0.0.1:5062
;rport;branch=z9hG4bKnoyvhhjv*
It's the same for Kam 3.4-dev.
What am I doing wrong?
Regards.
Carlos.