Systemd was Rate Limiting the console logs so that's the reason the capture
above was incomplete. Piping it to disk revealed the full debug log, thanks for
the tip.
The problem is that mongo does not have the AUTO INCREMENT id field such as
MySQL . The equivalent key is " _id" and is alphanume
Bogdan, the debug did not really print anything from the MSILO module as posted
below, Opensips 2.1.2. There is only a comment in the script during
registration when the m_dump() is executed. The mongdb query you see is just
housekeeping.
Mar 18 10:20:15 : route[initial_requests] : REGISTER:
I highlighted the comments on the reply from the UA in the reply-route. M_dump
is not printing any de bug messages. Tell me what to change in the code for
m_dump to print messages.
Two points:
It works ok when silo is in mariaDB .
If there is a problem with signaling it should not continue to r
If the messages are stored in a Mongo Replicaset using the CACHEDB module,
messages are stored, but being sent out repeatedly on each re-registration of
the client. It seems not able to update mongo on the 2xx.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/o
Case of ongoing audio call between UA1 and UA2 registered to different opensips
O1 and O2. Mediaproxy is started at O1 UA1. Call is going fine, UA1 sends a
re-invite for video, O2 receives request from O1 to relay to UA2 but chops off
a portion of the sdp containing the video port before sendin
I'm not understanding why it is a problem if Opensips deletes expired usrloc
records, wherever they may be. This may be an issue for you, but it is
problematic sharing location table among multiple opensips instances on other
levels. Most of all, lookups will not work properly because a user mig
Multi-line comment in call to "alter_mediaip" is not allowing function to
return normally (at least on Fedora). This can be seen by placing LM_INFO()
lines below the call or before the return 0 statement.
You can view, comment on, or merge this pull request online at:
https://github.com/OpenSI
Bogdan, I did some more tests and you are correct, rev_dns for the IP is
failing and finishing some time after. The solution now can be one of setting
rev_dns=no or not use flag 2 on the test.
How about a feature request to immediately cache the failed requests and a
setting to not make anothe
Bogdan, the answer is yes to your first question.
I also tested whether check_ip_address() is returning 0 by adding open/close
braces for each of the if/return 0 statements and placing a comment before the
return statement and the comments do not print nor does function perform the
final return
Based on the docs Global Settings, dns and rev_dns control
whether the sip server should lookup its own IP and Domain name. In testing for
RFC1918, it is also looking up the dns and rev_dns for the client's public IP.
If rev_dns=no then the client can register.
Some Troubleshooting Data:
Somet
Yes I tried your suggestion and it worked in the specific case flag index 2,
but I noticed some clients would register with the loopback IP (127.0.0.1) in
the AOR contact field after fix_nated_contact().
The script never before used the nathelper/fix_nated_contact() , just
nat_traversal/client
If someone else wants to use this the full version.
route[CHECKTOPVIA] {
if (pcre_match("$(hdr(via)[0])",".*UDP
(172\.\b([1][6-9]|[2][0-9]|[3][0-1])\b\.\b([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\b\.\b([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\b).*")
|| pcre_match("$(hd
Note: in route[CHECKTOPVIA] the asterisks were omitted when copied and pasted
in issue tracker.
eg: .*UDP
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/401#issuecomment-68878443___
Devel mailing li
Bogdan, normally the script uses nat_traversal/client_nat_test("3") . I have
tested flags 7 & 15 and NAT was still not detected; also tested all the flags
incrementally for nathelper/nat_uac_test("127") and also not detected.
I'm tending to think it is something out of the norm with the client
There is a client that cannot register because it is not detected as being
behind a NAT. It will register if treated as behind NAT by force. The top most
Via has a 10.x.x.x IP address, but neither nat_traversal nor nathelper can
detect it (xxx.xxx.xxx.xxx is a public IP). Client tried to connect
Eventually narrowed it down to the client UA where there may have been
bug/corruption in the application. The messages no longer appear after
reinstalling the app.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/384#issuecomment-63335048
/usr/sbin/opensips[6001]: WARNING:rr:after_loose: no socket found for match
second RR
/usr/sbin/opensips[6001]: WARNING:rr:after_loose: no socket found for match
second RR
/usr/sbin/opensips[6001]: WARNING:rr:after_loose: no socket found for match
second RR
These messages are appearing on serve
Applied patch and function is working as expected for all the cases, thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/340#issuecomment-57915314___
Devel mailing list
Devel@lists.opensips.org
http
fr_inv_timer no longer exists since 1.11, it was changed to fr_inv_timeout if
that is what you mean.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/342#issuecomment-57382338___
Devel mailing list
Devel
Usage: db_get_auth_id("$fu","$var(auth_id)","$var(auth_realm)");
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/340#issuecomment-57009023___
Devel mailing list
Devel@lists.opensips.org
http://lists.open
For example; if the UA is supplying "sip:us...@domain.com;protocol=udp" as the
$fu, this function fails to authenticate against the user table which has only
"domain.com" . This ";protocol=udp" is not being removed before comparison.
---
Reply to this email directly or view it on GitHub:
https:
missing semi-colon;
You can merge this Pull Request by running:
git pull https://github.com/jalung/opensips patch-2
Or you can view, comment on it, or merge it online at:
https://github.com/OpenSIPS/opensips/pull/265
-- Commit Summary --
* Update osipsconsole
-- File Changes --
M
The NOTRACK target occasionally appears but Media Proxy is working fine since
changing to a lower NAT test: client_nat_test("1") , on the reply route. It
seems unnecessary modifications were being done.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/i
Branch: refs/heads/1.11
Home: https://github.com/OpenSIPS/opensips
Commit: 2cb8bc791aa96dcf21b8fed0230e58e43e915ca7
https://github.com/OpenSIPS/opensips/commit/2cb8bc791aa96dcf21b8fed0230e58e43e915ca7
Author: jalung
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M
Opensips 1.11 fails to connect to Redis Cluster (beta6) running three masters.
This change should be backwards compatible.
You can merge this Pull Request by running:
git pull https://github.com/jalung/opensips patch-1
Or you can view, comment on it, or merge it online at:
https
This crash may be related to the libmemcache-devel package on the system. The
architecture may be incorrect i386, 1686, x64 etc.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/123#issuecomment-43571003
I've noticed that problem too, but I think it is caused due to the temp folder
clean-up by the OS's cron utilitiy. Create folder /var/run/opensips/ in an
rc.local startup script at boot time and assign ownership to Opensips; put the
fifo file there. The /var/run/ folder also gets cleaned up, b
During the build many of the below messages appear:
which: no confuse-config in
(/usr/lib/qt-3.3/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/user/bin)
which: no confuse-config in
(/usr/lib/qt-3.3/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbi
Hi Saghul,
There is some information here:
http://cateee.net/lkddb/web-lkddb/NETFILTER_XT_TARGET_NOTRACK.html
Below is a piece of log when mediaproxy is engaged.
Feb 22 23:20:34 sip /usr/sbin/opensips[2033]: Call control: user
sip:xxx...@example.net currently has: 1 call(s), Limit 2
Feb 22
This post is to make a comment rather than to report a bug.
Mediaproxy built on fedora 18 results in media transport issues.
Based on the documentation, Mediaproxy requires netfilter "NOTRACK" target
support, but this has been deprecated in favor of the newer "CT" target
available in iptables.
30 matches
Mail list logo
