Hello all,
I meanwhile found an issue in the config.ini file of openxcap. I did not
update the "xmlrpc_url" parameter.
Now at start of the Eyebeam client the two GET request (for pres-rules and
resource-list.xml) are successful but the documents are not visible in the
xcap-table. When I do a "SEL
El Domingo, 10 de Mayo de 2009, SAMEER KUMAR escribió:
> Dear Mr. Bogdan and OpenSIPS developers and users,
>
> While working in a team of four, I have made some changes in OpenSIPS and
> made it capable of providing multithreaded server.
Hi, let me a question: which are the advantages of multi-th
Hello all,
I have the following problem. I have configured an integrated XCAP server
(most simple configuration) and register a client with Eyebeam.
When the client registers it uploads obviously successfully two XML
documents:
- PUT
/xcap-r...@net1.test/org.openmobilealliance.pres-rules/users/ali
Hi Mauro,
You should consider the dialplan module for this - you can pass as input
the RURI ($ru), match the domain part of it via a regexp and do a subst
to replace the domain with the IP of the SBC.
See: http://www.opensips.org/html/docs/modules/1.5.x/dialplan.html#id227206
Regards,
Bogdan
Hi Sergio,
Do you set any traced_user_avp ? because setting such a user will
automatically enable the tracing.
Regards,
Bogdan
Sergio Gutierrez wrote:
> Hello to all members.
>
> I have a doubt about using siptrace.
>
> I am configuring siptrace to use trace_dialog feature, but it seems
> that
Hi Mauro,
The received field is used for NAT traversal purposes. As the contact
value cannot be altered (kept exactly as sent by client during
registration) and if UAC is natted , the contact is private, so
unusable, the USRLOC module keeps the public address of NAT in the
"received" field in
Hi Marc,
It is normal to increase as it is an absolute timestamp - see my prev
email on this thread.
Regarding the shm mem - do you see the dialogs actually being removed?
Regards,
Bogdan
Marc Leurent wrote:
> Sorry for the 3rd email.. but I think it's interesting, because the dialog
> timeou
Hi Marc,
no, that was just a mem leak with no affect on functionality of the module.
Regards,
Bogdan
Marc Leurent wrote:
> Do you think it could it be linked with bug id #2787654 ?? I don't think so
> but I will rebuild my OpenSIPs with trunk version...
> https://sourceforge.net/tracker/?func=d
Hi Marc,
Actually the timeout is an absolute time value - the timestamp when the
dialog will expire. It is not a relative (to start) value.
Regards,
Bogdan
Marc Leurent wrote:
> Hello all, I have juste a small question about the dialog module, I have set
> the parameters below for OpenSIPs dia
