[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » amd64,precise,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » amd64,wheezy,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » amd64,squeeze,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » i386,wheezy,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » i386,squeeze,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] Jenkins build is back to normal : kamailiodev-nightly-binaries » i386,precise,slave #514

See ___ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

[sr-dev] [kamailio/kamailio] unable to listen using eth interface (#602)

[According to the latest docs](http://www.kamailio.org/wiki/cookbooks/4.4.x/core#listen) kamailio should be able to listen on an address using the interface name of a local device. However, each time I try anything like: listen=eth1:5062 I get: 0(1) ERROR: [socket_info.c:1328]:

Re: [sr-dev] [kamailio/kamailio] dispatcher: use avl-tree for ds_set indexing (#578)

@miconda any updates on this PR? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/578#issuecomment-217457326___ sr-dev mailing list

Re: [sr-dev] [kamailio/kamailio] presence: introduce new module parameter `force_delete` (#601)

Good timing. Literally just came out of a meeting where the undesirable behavior of repeated `terminated` NOTIFY messages was discussed. This is a useful addition. You've changed a lot of whitespace that is not related to this PR. Makes it very difficult to digest :/ Appreciate this isn't

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

Hi, I've just updated the PR: - In multicast function I fix the issues with the parameters, was only 1. - Added evapi_unicast and evapi_async_unicast functions. - (evapi_dispatch.c) Rename evapi_relay_multicast, to _evapi_relay and provide 3 different functions to relay. Should be ok

[sr-dev] [kamailio/kamailio] presence: introduce new module parameter `force_delete` (#601)

- deletes expired presentity records without sending a NOTIFY - `force_delete` disabled by default You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/601 -- Commit Summary -- * presence: introduce new module parameter `force_delete`

Re: [sr-dev] [kamailio/kamailio] presence: introduce new module parameter `force_delete` (#601)

@miconda here is PR for new presence parameter --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/601#issuecomment-217447374___ sr-dev

Re: [sr-dev] [kamailio/kamailio] Kamailio 4.4) sipcapture_module: ERROR: parse_msg: message=<HEP3#003�> (#599)

The nonsip msg hook works for all transports, you can change to it if it helps. There is also SREV_NET_DATA_IN, but that probably needs some extra handling for its response code not to continue processing inside receive_msg(). --- You are receiving this because you are subscribed to this

Re: [sr-dev] [kamailio/kamailio] Kamailio 4.4) sipcapture_module: ERROR: parse_msg: message=<HEP3#003�> (#599)

@miconda can we replace sr_event_enable to register_nonsip_msg_hook and use it in both transports UDP/TCP ? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] sipcapture: table name corrupted (#566)

sorry guys, a lot stuff... yes, I will close it on this WE... --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] Kamailio 4.4) sipcapture_module: ERROR: parse_msg: message=<HEP3#003�> (#599)

kamailio's sipcapture module curently do now only SREV_NET_DGRAM_IN hook. ``` /* register DGRAM event */ if(sr_event_register_cb(SREV_NET_DGRAM_IN, hep_msg_received) < 0) { LM_ERR("failed to register SREV_NET_DGRAM_IN event\n"); return -1; } ``` and currently

Re: [sr-dev] [kamailio/kamailio] sipcapture: table name corrupted (#566)

Hoping @adubovikov will get back to this soon to close this issue. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] siptrace: HEPv2 destination port is sent as the wrong port (#581)

Added @adubovikov here just for adding his comments if it is the case to clarify something from sipcapture point of view. My guess is that the port is not taken from source address, because for TCP is hard (sometimes impossible) to guess the local port allocated by the kernel. That could make

Re: [sr-dev] [kamailio/kamailio] presence module triggering postgres constraint when marking records for deletion (#600)

@eschmidbauer: make a pull request, to be easier to review over all. You can make pull requests from branches of kamailio, no need to clone repo. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] kazoo: missing documentation (#530)

I pushed a patch to master branch with some docs about pua_mode as understood from mailing lists. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[sr-dev] git:master:f1e22c24: kazoo: regenerated the readme

Module: kamailio Branch: master Commit: f1e22c24b8d7a28c89f30d2fee8fa05eaa2ec7ed URL: https://github.com/kamailio/kamailio/commit/f1e22c24b8d7a28c89f30d2fee8fa05eaa2ec7ed Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:master:df30b8c7: kazoo: added some docs for pua_mode param based on lists discussions

Module: kamailio Branch: master Commit: df30b8c7c6021d84f560a6fb7d82a11cd0e1b3d5 URL: https://github.com/kamailio/kamailio/commit/df30b8c7c6021d84f560a6fb7d82a11cd0e1b3d5 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

Right now there is one tag per connection support -- you can extend it if you need more, as well as rpc commands to control connections. You can add timestamp per connection and have further rules to select it for a unicast. I pushed cfg multicast functions. I let testing (and unicast

[sr-dev] git:master:4fa443a3: evapi: documentation for evapi broadcast functions

Module: kamailio Branch: master Commit: 4fa443a3b6f3cfe3f3efc3bd028ad9eded1f6bf4 URL: https://github.com/kamailio/kamailio/commit/4fa443a3b6f3cfe3f3efc3bd028ad9eded1f6bf4 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:master:2236da9f: evapi: cfg multicast functions based on connection tag

Module: kamailio Branch: master Commit: 2236da9f5c75ebb844cd1ac57adf9c6e09d7fb25 URL: https://github.com/kamailio/kamailio/commit/2236da9f5c75ebb844cd1ac57adf9c6e09d7fb25 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:master:ab2958ae: evapi: documentation for evapi_set_tag(...)

Module: kamailio Branch: master Commit: ab2958ae0ecbffa8962a6e926236f70ca5504ddd URL: https://github.com/kamailio/kamailio/commit/ab2958ae0ecbffa8962a6e926236f70ca5504ddd Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

[sr-dev] git:master:28b809e4: evapi: added support for tagging connections and select for sending based on tag

Module: kamailio Branch: master Commit: 28b809e41be8e7bfc1ed5e564dbf2a0833a8de51 URL: https://github.com/kamailio/kamailio/commit/28b809e41be8e7bfc1ed5e564dbf2a0833a8de51 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

Hey Daniel, Tags make sense for me, and I love the concept TBH. Related with multicast functions I'm totally agree and I think that is too useful. About the unicast, It's ok for me and should work with Cgrates too, the only thing that maybe I'm worried about that is that unicast is going to

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/deb: use libradcli-dev for radius (#595)

A define is better because the radiusclient-ng is the only one available in some (old) OSes. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

Hi Eloy, I added the framework for tagging connections to simplify the development of further extensions via sending a structure packaged at once. I haven't extended the config functions for evapi relay, because I thought we may need to decide on naming. We can add a second parameter for the

Re: [sr-dev] [kamailio/kamailio] pkg/kamailio/deb: use libradcli-dev for radius (#595)

> So no changes required to radius modules -- only to pkg specs, right? Sadly, no. The Debian package doesn't provide the compatible include files freeradius-client.h nor radiusclient-ng.h, so we have to options: 1. remove radiusclient-ng support and use radcli instead 2. use another define to

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

Hey Daniel, Agree with the label, make sense so I can add. If you want I can do, I need this for us in the following days, so If you want I'll do at the beginning of the next week. Regards --- You are receiving this because you are subscribed to this thread. Reply to this email directly or

Re: [sr-dev] [kamailio/kamailio] Add missing modules to the spec file for CentOS 6 (#597)

Thanks, I will merge the patches manually to format the commit messages according to: * http://www.kamailio.org/wiki/devel/github-contributions#commit_message_format In the future, prefix the first line of the commit message with component name, in this case can be "pkg/rpm". --- You are

Re: [sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

If you get the IP:PORT in event route, then you can also set the tag there and can be inside the evapi connection structure, no need for htable anymore. You need to keep the relation of the IP:PORT and service somewhere, same can be done also with the tag name and service. The benefit is that

Re: [sr-dev] [kamailio/kamailio] presence module triggering postgres constraint when marking records for deletion (#600)

@juha-h: this is not changing anything in terms of the SIP specs. The behaviour is there, but now it is only a matter of the notifier_processes parameter. Given that this parameter is also useful for other tasks, I think it is fine to have a condition on another parameter for more fine tunings

[sr-dev] git:master:ab0a437d: cdp: keep the ser_clock_gettime() inside the module

Module: kamailio Branch: master Commit: ab0a437db098b014ed158434bd98db5ff3b76dd7 URL: https://github.com/kamailio/kamailio/commit/ab0a437db098b014ed158434bd98db5ff3b76dd7 Author: Daniel-Constantin Mierla Committer: Daniel-Constantin Mierla Date:

Re: [sr-dev] [kamailio/kamailio] Using registered() in event_route[usrloc:contact-expired] causes Kamailio to hang (#577)

No DB at all --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/577#issuecomment-217357140___ sr-dev mailing list