Hello,
On 9/6/11 3:54 PM, Klaus Darilion wrote:
Hi!
Recently I had a problem with permanent usrloc entries when upgrading a
server from SER 0.9 to Kamailio 3.1.
Obviously the problem was that the permanent entries had flag=128 and
now expires=0 is used, see old thread:
Hello,
On 8/29/11 7:45 PM, Camila Troncoso wrote:
Hi,
I have a question about the assignment of Role permissions to limit
some Users privileges in Siremis. I defined a user , and then a Role
denying some actions, but I couldn't deny the action from de SER menu
. The Role permissions only
Am 07.09.2011 10:16, schrieb Daniel-Constantin Mierla:
Hello,
On 9/6/11 3:54 PM, Klaus Darilion wrote:
Hi!
Recently I had a problem with permanent usrloc entries when upgrading a
server from SER 0.9 to Kamailio 3.1.
Obviously the problem was that the permanent entries had flag=128 and
Hi Daniel,
thank you for your quick reply. We have already tried with node
selector '~~' after doc uri in the http XCAP PUT request. But We got
the error ERROR: xcap_server [xcap_misc.c:60]: http uri too long
then ERROR: xcap_server [xcap_misc.c:736]: error setting xcap uri data
I think that
Hi Daniel,
thanks for the quick fix and reply.
What is the easiest way to try this new patch? I'm running kamailio 3.1.4
and there is no t_flush_flags() in tmx module in that version. I suppose I
need to install Kamailio Devel from git (
Hello,
On 9/7/11 11:24 AM, laura testi wrote:
Hi Daniel,
thank you for your quick reply. We have already tried with node
selector '~~' after doc uri in the http XCAP PUT request. But We got
the error ERROR: xcap_server [xcap_misc.c:60]: http uri too long
then ERROR: xcap_server
Daniel-Constantin Mierla writes:
the error is because the size of http url is higher than 127. You can
increase it, no problem, it is now 255 in devel version -- be aware you
have to increase in the database xcap table as well the size of
doc_uri.
daniel,
if uri size in devel version now
Hello,
On 9/7/11 11:26 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
the error is because the size of http url is higher than 127. You can
increase it, no problem, it is now 255 in devel version -- be aware you
have to increase in the database xcap table as well the size of
Ovidiu,
Thanks for your time. The fixes I pulled in is the latest rr module only. I
didn't see anything in that diff to make this work. Could you elaborate a
little?
However, I was able to get Outbound working properly by adding ;r2=on to
the record_route_preset IPs. In going through the
Hi,
we have patch the xcap_misc.h with #define XCAP_MAX_URI_SIZE 255
which was 127, and extended the length of field doc_uri in the xcap
table to 256 from 128. Now the errror is gone.
After that we have done some test with curl, following are the results:
- DELETE an Entry from the list: OK
It seems that you are on the right path now.
Regards,
Ovidiu Sas
On Wed, Sep 7, 2011 at 5:22 AM, Sarat C. Vemuri sarat.vem...@fthco.com wrote:
Ovidiu,
Thanks for your time. The fixes I pulled in is the latest rr module only.
I didn't see anything in that diff to make this work. Could you
Hello,
On 8/30/11 7:43 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
In the xmlrpc command, there was an etag value, have you tried with '.'
as etag?
i haven't tried with . etag yet. i'll try that tomorrow.
mi pua publish from different UAs on same presentity seems to
work ok,
Hello,
inserting a new node seems not to be possible through xpath operations
only, so I made a patch to be able to add new nodes (entries) -- see it
attached -- it is for devel version (master branch), hopefully it
applies clean to 3.1 if you are using that version.
There was no option to
Hi,
Sorry, let me explain my situation.
my box is behind nat with private ip 192.168.2.3 and nat ip is 60.x.x.x
and asterisk is same nat as the box with private ip 192.168.2.23
now let say i got 2 UA. one UA is located on different nat and another UA is
same nat with the box.
UA1- private ip
14 matches
Mail list logo
