[OpenSIPS-Users] Memory leak v2.1.4
One of my OpenSIPS Proxy servers has a memory leak that is bad enough to require the service to be restarted once a week. It was running version 2.1.1 and I just upgraded it this morning to v.2.1.4, but the memory leak is still happening. What are the best next steps to help track down the problem? John Quick Smartvox Limited Web: www.smartvox.co.uk ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Function set_advertised_address() seems to have wrong decision. Workaround?
Hi.
The function set_advertised_address() is changing the wrong IP in record-routs
from the SIP OK message.
I need to avoid this issue. The caller is in a remote network and the callee is
in the local network.
What is my situation:
An UAS (the callee), running in the same hardware as OpenSIPS, is registered
with IP 127.0.0.1. It could be 192.168.0.100 too. However, due to some
specifics requirements of our project, such UAS must register itself using IP
127.0.0.1, not 192.168.0.100.
What is the problem:
---
When set_advertised_address("domain") is called, for the SIP OK message, this
function decides to change 127.0.0.1 to "domain".
For example, OpenSIPS receives:
SIP/2.0 200 OK
Via: SIP/2.0/TCP
XXX.YYY.240.204:61871;rport=61871;received=131.221.240.204;branch=z9hG4bKPj8bd4d5988f4a4a0ba3599eba77f42600;alias
Record-Route:
Record-Route:
and change it to:
SIP/2.0 200 OK
Via: SIP/2.0/TCP
XXX.YYY.240.204:61871;rport=61871;received=131.221.240.204;branch=z9hG4bKPj8bd4d5988f4a4a0ba3599eba77f42600;alias
Record-Route:
Record-Route:
But, OpenSIPS should change the IP 192.168.0.100 to "domain", not the other
Record-Route.
As I have this issue, the UAC can't send the SIP ACK confirming the SIP OK.
What I need to provide:
I have to get/build a solution to make the set_advertised_address("domain")
change the Record-Route that contains the IP 1921.168.0.100.
Maybe, the OpenSIPS always change the top most Record-Route. If it is true, I
need a workaround for it.
So, how can I fix the record-routs as I need? Does it make sense to do what I'm
needing?
Any hint will be very helpful!
Best regards.
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] t_replicate and dispatcher module to forward REGISTER messages
Hi Guys, We have an old platform we are looking to redesign but in the meantime we need to fix a problem we have. Currently we have an opensips proxy/registrar with 2 x Asterisk boxes behind it. Now currently we use t_replicate and the dispatcher module (ds_next_domain()) to send REGISTER requests in parallel to both Asterisk Servers so they can update their sip peers. This works great but we sometimes (an issue we are investigating) dont always get a 200ok response back from one or both Asterisk servers for the REGISTER message. Therefore I am looking to resend the REGISTER whenever this may happen. This is fine using the fr timers should both Asterisk Servers not respond, however if only 1 Server doesnt respond, and the other does, this problem is lost, due to the parallel forking being applied to the t_replicate scenario. I can capture 200 ok messages in onreply routes to confirm which Asterisk servers have responded, however I cannot t_relay again from this type of route. Is there another way to do this? Whereby I can remain transaction stateful, and resend a REGISTER message if only one of the Asterisk Servers doesnt respond to a REGISTER message? Thanks Jon ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
