Hi,
Just to remind you all to contribute to the topics list for the 8th of
MArch 2011 IRC meeting. See:
http://www.opensips.org/Resources/IRCmeeting20110308
Thanks and regards,
Bogdan
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 28th February 2011
OpenSIPS solutions and know-how
The parameters for rtpproxy_offer/answer are the same as the old
parameters for force_rtp_proxy.
The swap flag was no longer necessary and therefor removed.
Regards,
Ovidiu Sas
On Wed, Mar 2, 2011 at 1:35 AM, Andrew O. Zhukov gn...@telegroup.com.ua wrote:
On 03/01/2011 06:59 PM, Ovidiu Sas
Hello all,
I want to announce that by the end of the week we will make some
structure modifications to the *nathelper* module.
The module will be split into two parts - separating the communication
with RTPProxy from the signaling and testing functions. The RTPProxy
specific functions will
Hello Razvan,
Splitting the nathelper module is the right thing to do. Thank you
for taking care of it.
With respect to the mangler module, there are still a few functions
that are useful: the encode/decode contact header.
Will you move these functions into an existing module?
Regards,
Ovidiu
Hello Ovidiu,
All the functions from mangler module will be moved in nat_traversal,
including the encode/decode contact header ones.
Regards,
Razvan
On 03/02/2011 04:12 PM, Ovidiu Sas wrote:
Hello Razvan,
Splitting the nathelper module is the right thing to do. Thank you
for taking care
Hi All,
Is it possible in the OpenSIPS script to make somehow back resolution of
ip-address?
Something like this pseudocode:
$var(ip) = 127.0.0.1;
$var(name) = $(var(ip){ip.rev_resolve}); # rev_resolve - just desirable...
# name == localhost
Thanks,
Igor.
On 2 March 2011 13:47, Razvan Crainea razvancrai...@opensips.org wrote:
Note that there will be no functional changes, but only structural ones, all
current functions exported by nathelper module will still be available (some
name changes might be possible though), just that they will be
Hi Igor,
no, there is no such transformation, but if it is something critical for
you, open a feature request on SF tracker and somebody may take care of
it in the future.
Regards,
Bogdan
Igor Solovyov wrote:
Hi All,
Is it possible in the OpenSIPS script to make somehow back resolution
Hi Andrew
Andrew O. Zhukov wrote:
Force_rtp_proxy() was replaced by rtpproxy_offer() (first step) and
rtpproxy_answer() (second step). See:
http://www.opensips.org/html/docs/modules/1.6.x/nathelper.html
and
Bogdan,
As I understand. If I use the very old style stabile working config
Hi,
If I use
if ($si==some.server.com)
{
...
}
and some.server.com has several A records,
are all of them used in upper comparison?
How does TTL influence on saved IPs?
Regards,
Igor.
___
Users mailing list
Users@lists.opensips.org
Igor,
I'm pretty sure that won't work at all. You would need to use the
transformation ip.resolve.
I don't know if it returns multiple IPs but if it does you would want to
assign it to an avp that can handle multiple.
An example to try:
$var(fqdn) = some.server.com; # Not sure if you can do a
Hi Bogdan,
I get a very similar behavior as what Jeff gets. I can see the re-INVITE
coming and I'm sure that it goes through loose_route block. I can also see
the Update by a REQUEST log. Here's a snippet of the logs after getting
the re-INVITE:
DBG:dialog:dlg_onroute: route param is
Dave,
Thanks for idea.
I've done the test:
route[test]
{
$var(fqdn) = google.com;
$avp(s:ips) = $(var(fqdn){ip.resolve});
xlog(L_ERR, --TEST--:
$(avp(s:ips)[0])::$(avp(s:ips)[1])::$(avp(s:ips)[2]));
return(-11);
}
The results:
Mar 2 22:20:12 os1 opensips: --TEST--:
Hi all,
Is it possible to hook into registration removal events? I'd like to
notify an external server when a user goes off-line, including when they
don't deregister properly. I can call an external program in the route
handling REGISTER requests but can't find any way to handle the case
where a
14 matches
Mail list logo
