looks like 4.1 and master mtree README is missing these parameters:
{"pv_dstid", STR_PARAM, &dstid_param.s},
{"pv_weight", STR_PARAM, &weight_param.s},
{"pv_count", STR_PARAM, &count_param.s},
i didn'd find in the code any use for the last.
-- juha
defined($avp(foo)) can be used to test if avp $avp(foo) has been
defined. i looked through kamailio wiki, but didn't find defined
function documented anywhere.
-- juha
Hi,
I'm trying to fetch attribute list with kamailio ldap_search:
ldap_search("ldap://agents/ou=Xxxxx,dc=xxxx,dc=yyyyyy,dc=zz?memberOf?sub?(sAMAccountName=$fU)");
ldap_result("memberOf/$avp(s:ldapmemberof1)");
xlog("L_INFO", "LDAP $fU memberOf = $avp(s:ldapmemberof1)");
if (ldap_result_next())
{
xlog("L_INFO", "if loop ldap_result");
ldap_result("memberOf/$avp(s:ldapmemberof2)");
xlog("L_INFO", "LDAP $fU memberOf = $avp(s:ldapmemberof2)");
}
There's must be seven returning attributes list of memberOf, but I can only
retrieve only one of them (looks like last of seven). First xlog output log
into my log file, but if loop didn't start. What I'm doing wrong?
Hi,
I have a kamailio with the dispatcher module setup. I use:
ds_select_dst("1", "9");
to load balance between 3 gateways.
My database looks like this:
id setid destination flags priority attrs
5 1 sip:1.1.1.1 0 0 weight=10
8 1 sip:1.1.1.2 0 0 weight=45
9 1 sip:1.1.1.3 0 0 weight=45
As I understand it, most of the calls should be split evenly between
gateways 8 and 9, and some calls (around 10%) going to gateway 5.
Well, gateway 8 gets 99% of the calls. I am using kamailio 4.1 and I really
cannot understand why this is happening. Running ds_list shows me that all
gateays and weights are correctly parsed into kamailio.
This is the result of my ds_list:
SET:: 1
URI:: sip:1.1.1.1 flags=AP priority=0 attrs=weight=10
URI:: sip:1.1.1.2 flags=AP priority=0 attrs=weight=45
URI:: sip:1.1.1.3 flags=AP priority=0 attrs=weight=45
I have tried changing the priority to 100, or to 1 in every gateway, and
the result is still the same. I have tried adding ; after the weight
parameter, the colon is gone in the ds_list once kamailio parses it.
If, keeping the same database, I use ds_select_dst("1", "0") the calls are
split evenly across all 3 gateways. This is great, but not what I want, but
it at least proves that something is working.
Is there anything else I can try?
Thanks a lot for the help!
Alex
Slightly offtopic, but for QA reasons I'm interested in logging RTCP reports
from peers that send them. It looks like rtpproxy-ng might be used to do this
(I'm already using rtpproxy anyway). Is someone already doing this and willing
to share some pointers?
I am in need of a Kamailio expert that has some availability for
consulting services (remote is fine). Feel free to contact me for details.
Thanks,
Sharan Harkisoon
Hi Gents,
We have created a small redirect server using the Lua API to get the
destinations.
Lets say that it takes some time while the script generates the answer,
during this time we got a CANCEL.
How we can handle this properly ? As far as I could see the TM module
always sends back the answer (302) and after that I get the "CANCEL" in
my script.
Here is my config: http://pastebin.com/7PyKBJyD
Here is my test Lua script: http://pastebin.com/6VXn5y8m
Could you please help me what is the best way to handle the CANCEL ?
Is it possible to do it properly ?
Thanks,
Misi
I am planing to implement mediaproxy so which NAT module will be good for
media proxy and why?
should i use nat_traversal ro nathelper ? I haven't see any example people
using nat_traversa. most of example i found on google are based on
nathelper so just want to make sure which one i should use and why?
