Hi Ovidiu,
Thanks for your reply. I don't see any errors in the syslog after raising
the debug level to 5. They are mainly informational about bridging and
relaying. The loadmodules sections is pasted below:
loadmodule db_mysql.so
loadmodule signaling.so
loadmodule sl.so
loadmodule tm.so
Hi John,
I tried to reproduce this on live system and I do not see this difference:
tester001:~# opensipsctl fifo get_statistics usrloc:
*usrloc:registered_users = 53*
usrloc:location-users = 53
usrloc:location-contacts = 56
usrloc:location-expires = 84
tester001:~# opensipsctl ul show --brief
Hi James,
thanks a lot for the feedback.
The log you added does not show anything wrong - the path fields may be
missing and the so called contact part (returned by usrloc) is either
the received URI (if present), either the contact URI (if not received URI).
What looks scary are the
Hi Chris,
To be honest I fail to understand what you are trying to do - better
please post the failure_route part (or the script).
Regards.
Bogdan
On 07/04/2011 12:24 PM, Chris Martineau wrote:
Hi Bogdan,
Tried these methods.
1.Doesn't seem to help entry of the custom reason into the db.
Hi Vic,
could you get a backtrace from the core you got ?
Thanks and Regards,
Bogdan
On 07/05/2011 09:48 PM, Vic Jolin wrote:
Hi,
after a few minutes that opensip is running, opensip just stops
without errors in console, so I started it to make a core dump.
the core dump output is as
Hi David,
OpenSIPS by itself does not generate such a reply, so:
1) either the reply comes from script
2) either reply is not gnerated by opensips, but by other entity on
the path
Regards,
Bogdan
On 07/06/2011 08:00 AM, David Cunningham wrote:
Hi all,
We're seeing a strange reply
Hi Tiberiu,
OpenSIPS by default cannot add this param as it is SDP transparent
(opensips is doing SIP signalling and it does not care too much on the SDP).
But you can use the textops functions to add new lines to SDP, of
course, if you know what you are doing :)
Regards,
Bogdan
On
Hi Nicolas,
what you experience seams to be about the subscription time - seams that
the subscribe simply expires (or there is an un-subscribe) and no
notifications are sent anymore to the watcher.
Check is the watchers table to see which are the current subscriptions
and when they are
Hi José,
'rport' VIA param is to be used in NAT situations. As the VIA hdr is
used for routing back the replies, if the caller is behind nat (and its
VIA with a private IP), the routing back of the reply to it will not be
possible.
The way rport works it is very simple - this param
Also I don't know if that helps you but Mediaproxy and CDRTool show you how
much bandwidth was used on a call after the call is over.
On Jul 8, 2011 11:20am, Bogdan-Andrei Iancu bog...@opensips.org wrote:
Hi Tiberiu,
OpenSIPS by default cannot add this param as it is SDP transparent
Thanks a lot Bogdan.
I follow the use of rPort all the way explained here. What I don't
understand, is, if the received and rport parameters are filled in by the
UAS that gets the request, how is that useful to the UAC that originated it
when the reply is routed back to it? What situations may
Hi,
thanks for your time but I think it was just an error on my configuration
On Fri, Jul 8, 2011 at 11:59 PM, Bogdan-Andrei Iancu bog...@opensips.orgwrote:
**
Hi Vic,
could you get a backtrace from the core you got ?
Thanks and Regards,
Bogdan
On 07/05/2011 09:48 PM, Vic Jolin wrote:
Bogdan,
Thank you for testing this. I also have done some more tests. On a second
server I loaded Ubuntu, then OpenSIPS 1.6.4 tls. On this server I am running
a very simple config and the statistic for registrations is steady - it does
not increment. Next, I am trying to run the same very simple
Thanks for the replies!
I actually found the solution in Linphone's settings: there are two settings
for Download and Upload rate limits.
If completed, these values will be added to the SDP body as Bandwidth
Information parameters.
Then I used openSIPS to extract the requested Download bandwidth:
Hi Bogdan,
I've been monitoring it (I wrote myself a script that checks the AORs
in memory against syslog).
I haven't seen any issues lately.
The trailing garbage is weird as well. In the DB, the contacts look ok.
I haven't tracked down where that is coming from yet.
-- James
On Fri, Jul 8, 2011
15 matches
Mail list logo