Documentation updated.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-6133___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Closed #217.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#event-125690958___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
I pushed some changes into trunk (some extra checks and more error logs).
Please give it a try and report back any issues.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-44030734___
Recreated pull request. The proper one:
https://github.com/OpenSIPS/opensips/pull/236
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43589176___
Devel mailing list
Both hash size and timer interval are configurable so the admin can tune them
to fit their needs.
One reason for having a hash is to avoid running over all records when the
timer fires.
When the timer fires, the modules checks only one entry into the hash table,
that's why the timer_interval is
I think this moment not well documented.
And also something wrong there.
If I have timer_interval 60 with hash_size 5 then for registration with
expires=120 we have
rec-registration_timeout = now + 120 - 60 = now + 60
So, we will update every 60 seconds. It's not good.
Maybe this logic will be
I've found the error. It's not on your side. We changed contact in local route,
then contact-uri != rec-contact_uri and module didn't use expires from
contact. We will try to avoid contact changing in local route. But I've found
logical problem in code. You divide timer_interval on reg_hsize
any progress in this task?
or you need some additional information?
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43065426___
Devel mailing list
Devel@lists.opensips.org
This issue was fixed a while ago (see my previous comments).
You need to build from the latest stable and re-test.
I know that you are claiming that you are building from latest git, but your
output for 'opensips -V' doesn't show the git version which is odd ...
You can try to register from a
we have latest stable version from git. now updated to 1.11 and problem is
still there
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43079389___
Devel mailing list
Please provide me with the output of 'opensips -V'.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-43079582___
Devel mailing list
Devel@lists.opensips.org
version: opensips 1.11.1-tls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method
You mentioned that you are compiling from git. I don't see your git version in
the output of 'opensips -V'.
I will need an account on your server and I will try to register to it to
reproduce it.
In the mean time, there's nothing I can do since it's working ok for me.
---
Reply to this email
Ovidiu, when you build rpm or compile opensips manually, opensip -V doesn't
write git version (I'll figure out how to fix this). But you may be sure we use
git. Today we change 1.10 into 1.11. The same problem. And sorry, we cannot
give you access. We can give you any information you need and
Nick,
I build my own rpms from git and it always has the git revision in it.
I tested the scenario that you provided to me and I pointed out to you that
this issue was fixed.
All I need is an account on your server to perform a registration, but it seems
that this is not possible.
The pcap
This is working fine on dev and 1.11.
I will try to reproduce it on 1.10 ...
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42319066___
Devel mailing list
Devel@lists.opensips.org
There are no differences between 1.10 and dev.
@achalkov please post your version of opensips here.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42326775___
Devel mailing list
One of latest 1.10 from git (92d6ed496c87e61865a43f46e524ff1d3090c856).
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42328884___
Devel mailing list
Devel@lists.opensips.org
Please post the uac_registrant params and the output of 'opensips -V'
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42330694___
Devel mailing list
Devel@lists.opensips.org
A similar issue was fixed a while ago:
commit f9a8d985829ed1cce3a2f0985a8c72368d0b3325
Author: Ovidiu Sas o...@voipembedded.com
Date: Fri Nov 22 12:34:03 2013 -0500
uac_registrant: re-register with expires value imposed by the registrar
---
Reply to this email directly or view it on
version: opensips 1.10.1-tls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method
The issue was fixed Nov 22. However, we use latest git 1.10.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42332246___
Devel mailing list
Devel@lists.opensips.org
Something is not right with your install: I don't see the git version on the
output of 'opensips -V'.
See the output that I have:
version: opensips 1.10.1-notls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_MALLOC,
You may be sure we use git.
# rpm -qa|grep opensips-1
opensips-1.10.1.20140505.92d6ed4-2.x86_64
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42333744___
Devel mailing list
Hi @ovidiusas , any progress with this bug ?
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42201242___
Devel mailing list
Devel@lists.opensips.org
I will try to work on it tomorrow.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-42204484___
Devel mailing list
Devel@lists.opensips.org
Situation:
A = registrant (our opensips with uac_registrant module). all REGISTERS sent
with expires=60 (as ct.fields(expires))
B = registrar (some sip-server). Sends 200OK with expires=600 (as
ct.fields(expires) too) to REGISTERs with expires lesser then 600.
When A receives 200OK with
Please provide a trace for it and the version of opensips that you are using.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-41672035___
Devel mailing list
Devel@lists.opensips.org
opensips 1.10 latest git commit as registrant.
i sent pcap trace to your email
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/217#issuecomment-41676251___
Devel mailing list
Devel@lists.opensips.org
29 matches
Mail list logo