The progress will continue on hiops module #2209
--
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/1856#issuecomment-579459228___
Kamailio
Closed #1856.
--
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/1856#event-2987272298___
Kamailio (SER) - Development Mailing List
Reopened #1856.
--
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/1856#event-2985330181___
Kamailio (SER) - Development Mailing List
Please looks at top of this page. You will find
```
kamailio:master from mojtabaesfandiari:master
```
This PR created using `master` branch in your fork repo.
When you pushed a3dca98 commit as latest then GitHub can see that commit
already exist in upstream repo and make decision no need PR
why the hiops module pull request is closed after i update the base branch
to master for new pull request?
On Mon, Oct 28, 2019 at 10:19 AM Mojtaba wrote:
> Hello,
> Yes, The delay is because of developing another module for Kamailio.called
> LREProxy.
> The process of developing LREProxy is
Closed #1856.
--
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/1856#event-2985075779___
Kamailio (SER) - Development Mailing List
@mojtabaesfandiari pushed 0 commits.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/kamailio/kamailio/pull/1856/files/d3a762f56d2710c1e39c331f4ee8879921231264..a3dca980d945c3aab4dba8226b91dc92edea2321
Hello,
Yes, The delay is because of developing another module for Kamailio.called
LREProxy.
The process of developing LREProxy is done and the module is under stress
test for checking it's performance. I am planning to update all codes of
hoops module.
Then upload them. May be i could upload
Hello,
Yes, The delay is because of developing another module for Kamailio.called
LREProxy.
The process of developing LREProxy is done and the module is under stress
test for checking it's performance. I am planning to update all codes of
hoops module.
Then uploa
On Fri, Oct 25, 2019 at 3:06 PM
No activity since beginning of March 2019, more than half a year. Is this still
planned to be updated and merged?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hello,
Of course,
Thank you
On Sun, Mar 3, 2019 at 2:26 PM Henning Westerholt
wrote:
> Hello, thank you. About the remaining two topics:
>
>- regarding the ETSI standards, maybe you can add some comments later
>on how this module was tested against (like some hardware, vendor etc..)
>
@mojtabaesfandiari pushed 1 commit.
d3a762f56d2710c1e39c331f4ee8879921231264 hiops: remove cmake file from module
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
Hello, thank you. About the remaining two topics:
- regarding the ETSI standards, maybe you can add some comments later on how
this module was tested against (like some hardware, vendor etc..) when you
finished development
- about the cmake file - if its only related to your local development
Hello Henning,
In regards of first comment, This module is developed to provide handover
interface for lawful Interception in IMS-Network(VoIP-Services) for
Kamailio. Actually I am developing,yet, just as like some optimization
code, add extra features and more. My implementation is based on
Thank you for the your interest in Kamailio and the module in development. I
did a quick high level look today and have a few comments:
- can you give a small description what your module actually does? :-)
- a huge part of your code is related to the asn1 functionality. Some of this
is library
@mojtabaesfandiari pushed 1 commit.
c6e4844d3bf945ffd5f69c01a1b3dd12a161928e htable: add new function in htabe_api
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@mojtabaesfandiari pushed 3 commits.
098e307e018e8866e3c7e09fb65c98850e82f3cf core: move the received_in_via
function to hiops module
bf31c7db4bfef15d89a24b663f9c05d68fe4a3e5 hiops: change function name
56ab9820cd957bb9af3aa7ebb7b79fdecc80a548 hiops: Add two function to these files
--
You
I updated and now the codes is available for hiops module.
In Regards of new function in core, I will do that.
On Wed, Feb 20, 2019 at 2:15 PM Daniel-Constantin Mierla <
notificati...@github.com> wrote:
> There is no code for your module, it seems you try to add it as a git
> submodule. It has
Hello,
Yes, Tell me about it.
I will do it as soon as.
I am far away right now. Actually i am going to Germany embassy.
On Wed, 20 Feb 2019, 14:15 Daniel-Constantin Mierla, <
notificati...@github.com> wrote:
> There is no code for your module, it seems you try to add it as a git
> submodule. It
There is no code for your module, it seems you try to add it as a git
submodule. It has to be pushed with full code, if you want it to merge it
inside kamailio repository.
Then your commit messages do not follow the contributing guidelines:
*
@mojtabaesfandiari pushed 1 commit.
065a102c1f53c5a43a77173a8688b6a13dcd44ab hiops module
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
This is new module in Kamailio, named hiops module. I am developing and it take
few time to done.
In all over the module i used LM_INFO instead of LM_DBG, just for much easy
troubleshooting. And also I would use lock for share memory in all project.
These are some 'todo' project that i have to
This is new module in Kamailio, named hiops module. I am developing and it take
few time to done.
In all over the module i used LM_INFO instead of LM_DBG, just for much easy
troubleshooting. And also I would use lock for share memory in all project.
These are some 'todo' project that i have to
23 matches
Mail list logo
