Closed #1150.
--
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/1150#event-1130489809___
Kamailio (SER) - Development Mailing List
sr-dev@lis
Thanks, closing it then!
--
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/1150#issuecomment-309676278___
Kamailio (SER) - Development Mailin
yep. It works now! :-) thank you
--
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/1150#issuecomment-309675518___
Kamailio (SER) - Developmen
So #1155 is fixing also the introduced bug with bad pointer?
--
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/1150#issuecomment-309674524___
https://github.com/kamailio/kamailio/pull/1155
looks like it has been fixed :-)
--
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/1150#issuecomment-309673679___
bingo! :-)
now another issue:
/usr/sbin/kamailio[1798]: ERROR: topoh [topoh_mod.c:560]:
th_execute_event_route(): exit due to 'drop' in event route
/usr/sbin/kamailio[1798]: : [core/mem/q_malloc.c:469]: qm_free(): BUG:
qm_free: bad pointer 0x7fa3461b9000 (out of memory block!) called from co
Might have been the execution of clear_branches() inside next faked msg
function, which was resetting some global variables. I just pushed a patch in
master, can you give it a try again?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
no, the fake msg is not null, but once you call the faked_msg_next(), after you
will always get "I'm terribly sorry, server error occurred (6/SL)", even if you
didn't execute "run_top_route".
I will check a bit more, but the issue it can be with pointer for
re-transmission.
--
You are recei
Indeed, that condition should be with &&.
Is the next fake msg null, or what is failing there? Can you see what is the
return code for t_relay? I guess the slow error is because of sl_send_error ()
in kamaulio.cfg. I am traveling, no much testing that I can do.
--
You are receiving this becaus
Thank you @miconda , unfortunately there is bug that I couldnt catch.
6 days ago I have implemented same way in my repository:
https://github.com/adubovikov/kamailio/commit/ae15a717e9a5849b4ac295c5864cd6e9b198b6d1
but your and my patches makes same results:
/usr/sbin/kamailio[1260]: ERROR: sl [
Can this be used for topos as well as topoh?
--
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/1150#issuecomment-309004565___
Kamailio (SER)
I did an implementation to execute an event_route before the topoh processing
for messages to be sent out. Documentation will follow soon, meanwhile you can
see the comments of the commit f7d1d23 . Basically, $sndto(ip) should point
to the ip address of the destination and calling `drop` sho
ok. agree.. this way will be more effective and flexible. Should I do or you
wanna ? ;-)
--
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/1150#issuecomment-307392619__
Giving a fake request is very fast, like done at:
*
https://github.com/kamailio/kamailio/blob/master/src/modules/htable/htable.c#L268
It is no parsing apart of the first time. This way is safe, because some
functions need the msg structure.
--
You are receiving this because you are subscrib
so, from topoh we can call topoh-route in kamailio.cfg , there we can use
allow_address from the permissions module and base on the result we can reject
and accept topoh request. Should we just send empty sip_msg structure there ?
Just to avoid sip message parsing in case the request will be rej
We have the source code, we can change if something helps substantially --
currently, I see two options that can be controlled via a mod param (or just
choose one that it is considered better):
* give a fake request, like it is done with other event_route blocks (e.g.,
htable:mod-init) -- thi
Yes, exactly this way, just to exclude or include destination IP for topology
hiding.
I am not sure that there is a way to do it via internal flags, because the
event socket for SREV_NET_DATA_OUT will be called from retransmission function
in the tm module and in this case you don't have sip_m
What is exactly the purpose of this new functionality? To allow/deny traffic
from those IP addresses or for doing/skipping topology hiding?
I am somehow not very pleased with importing a lot of code similar to what
permissions does in regards to address matching. I would rather do another
appro
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1150
-- Commit Summary --
* modules/topoh: added IP lookup functionality for trusted or untrusted
destination
* modules/topoh: changed README
* utils/kamctl: fixed sql schema for t
19 matches
Mail list logo