Hi all,
OpenSIPS has been enhanced with a new module called **event_rabbitmq**.
This module allows the proxy to feed a RabbitMQ server with useful
runtime events and information about OpenSIPS.
More exactly, **event_rabbitmq** is designed as a transport module for
the new OpenSIPS Event Inte
Well, there is no response on the NAPTR since this domain only has TCP SRV
records:
Oct 12 11:06:37 proxy /usr/local/sbin/opensips[5809]: DBG:core:mk_proxy:
doing DNS lookup...
Oct 12 11:06:37 proxy /usr/local/sbin/opensips[5809]:
DBG:core:sip_resolvehost: no port, no proto -> do NAPTR lookup!
Oct
I have the exact same issue. Did you figure this one out?
Ian Buckner wrote:
>
> I just wanted to pick up on question 1 as I have the same problem and may
> have got slightly further in tracing this:
>
> Using ssldump I see the following during the initial REGISTER operation:
>
> On OpenSips
On Tue, 2011-10-11 at 09:20 -0500, Brett Nemeroff wrote:
> On Tue, Oct 11, 2011 at 8:39 AM, Brad Bendy
> wrote:
>
> Hi list,
>
> Im trying to get a opensips 1.6.4-2 with rtpproxy 1.2.1 to
> work in bridge mode, calls will get a INVITE from a private
> ne
On 10/12/2011 07:55 PM, Brad Bendy wrote:
> Adding in some check for SDP did take care of that problem, just appears
> the outbound leg upstream is not getting rewritten with the correct
> external address, still using the internal one. From what Ive read you
> can use rtpproxy_answer() and rtpprox
Hi Saul,
Im running debian wheezy with the following versions
root@server2:~# aptitude show libgnutls26
Paquete: libgnutls26
Estado: instalado
Instalado automáticamente: no
Versión: 2.12.10-2
root@server2:~# aptitude show python-gnutls
Paquete: python-gnutls
Estado: instalado
Instalado automátic
