Playing around with ndb_mongodb
getting this error:
ERROR: ndb_mongodb [mongodb_client.c:262]: mongodbc_exec_cmd(): Failed to
run command: lexical error: invalid char in json text
query is very simple:
db.cdrs.insert({time:new
Date(),src_user:"kelvin",term_ani:"14112",src_domain:"domain.com
",src_ip:"0",dst_ouser:"18188",dst_user:"18112",dst_domain:"domain.com"})
which is inside a pv
mongodb_cmd("mgs1", "datab", "cdrs", "$var(MNG_MISSED)", "mgr1");
tried this:
insert({time:new Date(),src_user:"kelvin",term_ani:"14112",src_domain:"
domain.com",src_ip:"0",dst_ouser:"18188",dst_user:"18112",dst_domain:"
domain.com"})
and other combinations, same error
any ideas? i guess we need some more examples on the documentation
Kelvin Chua
Hi!
In SIREMIS I am getting the info after trying to register, that "Public
registration is not enabled!"
but i have set siremis/modules/ser/config/common.Main.php to
$cfg_siremis_public_registrations = true;
What is the problem?
Thanks and Greetings,
Sven
Hi Gents,
We have a redirect server based on Kamailio (4.2.3).
The server has multiple IPs, but Kamailio is bound to only one address:
http://view.xscreenshot.com/9dfdf449a387bdc6f9a719eae3620416
*Sometimes* it answers back from a wrong IP address, here is the proof:
http://view.xscreenshot.com/ac661d6b303eda6653b37be7cf65aa65
The interesting thing is that if I do:
root@tralab-route-01:~# ip ro get 10.121.24.51
10.121.24.51 via 10.121.43.30 dev vlan486 src 10.121.43.17
cache ipid 0x05ad
root@tralab-route-01:~#
So the 10.121.43.17 IP is selected, but I *do* expect that Kamailio send
back the answer from the same socket where it got the request.
What could be the issue ?
Why does it do that *sometimes* ? In the majority of the time it works
well..
I am not sure why this happens...
Thanks,
Mitya
i was wondering why sometimes requests to rtpengine don't get through
and icmp unreachable destination error message is received. it turned
out that in these error cases ip packet containing the rtpengine request
has 0x02 (don't fragment) flag set even when the packet was bigger than
4 KB. in this case kamailio was running in an amazon container which
may be doing something weird.
is it somehow possible from the application (= kamailio) to control
setting of that flag?
-- juha
Hello,
I would like to inform that the deb nightly builds are going to be disabled.
I'm having problems with the actual configuration and until I found the
time to fix them the service
will be out of order.
No new debs will be produced until further notice.
Cheers,
Victor
Hi,
Is it possible for Kamailio to restrict certain users (like in a group) to
only receive calls but never dial out or send SIP Simple messages outbound,
while allowing all other "regular" users to make outgoing calls and text
messages as well as receive them?
If so, which module do you guys recommend I look into?
Cheers,
Peter
Hello,
We are trying to get Kamailio working as an SBC using rtpproxy();
The config seems to work except with some carriers, kamailio does not
recognize the ACK because it does not match the contact header of the OK
I've been trying to figure out how to get kamailio to send the OK back
using the public IP address but I cannot figure out how.
I've tried using various deployments of the nathelper module such as
fix_nated_contact()
set_contact_alias()
No matter what though, Kamailio will not change the contact header it
receives from FS before sending it back to the carriers.
This has become frustrating as I read tutorials that showed this is
possible, yet I am unable.
Thank you.
/V
Hello,
I have developed a Kamailio module to handle group messaging and am
using certain functions from the libm.so library. Compilation happens fine,
but Kamailio subsequently fails to start because the math.h symbols are
unlinked/undefined. Could someone please suggest a workaround for this.
Thanks,
Shouvanik.
Hi!
We meet such an issue with some kinds of client internet connections
(e.g. reproduces always on local wifi, but doesn't repr. on 3g inet).
We don't know what are exact network characteristics, but what happens
from perspective of traffic on SIP server is the following:
1. the SIP client registers successfully to Kamailio (which is recent
git master HEAD) with TCP transport for SIP;
2. another client calls this user;
3. Kamailio relays INVITE, it gets transmitted fully and ACK-ed on TCP level;
4. then, within 0.1-0.2 second, Kamailio fires first retransmit of
that INVITE, which doesn't get fully transmitted (it is shown
trunkated in sniffer output, no TCP ACK replies for it);
5. Kamailio tries to retransmit INVITE again, with the same result as in #5.
6. The caller gets SIP/2.0 408 Request Timeout.
A piece of traffic from "ngrep -t -e -d any -W byline port 5060":
https://gist.githubusercontent.com/krieger-od/219f9975e5efb980ff5b/raw/096a…
The called side app is based on mobile Linphone app.
Switching to UDP is not an option (in some networks SIP messages get
delivered trunkated which breaks calls), we will check how it works
with TLS transport a bit later when there's technical possibility.
I have two questions:
1. How would I completely disable retransmissions to TCP connections?
2. Any ideas what can be the reason for this issue? Retransmissions by
themselves?
--
Andrey Utkin
