[Spce-user] Problem with new peer : ngcp-lb at 82.139.112.32:5060; ngcpct='sip%3A10.18.3.200%3A5080'

[Raul Alonso]

Thanks Jon.

Regards,
Raúl

> -----Mensaje original-----
> De: spce-user-bounces at lists.sipwise.com [mailto:spce-user-
> bounces at lists.sipwise.com] En nombre de Jon Bonilla (Manwe)
> Enviado el: martes, 18 de junio de 2013 23:59
> Para: spce-user at lists.sipwise.com
> Asunto: Re: [Spce-user] Problem with new peer : ngcp-
> lb at 82.139.112.32:5060; ngcpct='sip%3A10.18.3.200%3A5080'
> 
> El Tue, 18 Jun 2013 16:47:29 +0200
> Jon Bonilla (Manwe) <jbonilla at sipwise.com> escribió:
> 
> > El Tue, 18 Jun 2013 11:53:39 +0200
> > "Raul Alonso" <raul.alonso at tpartner.net> escribió:
> >
> > > Hi,
> > >
> > > Is possible to have this patch to see if that solves the proble?
> > >
> > >
> >
> >
> > Sorry Raul. There was a problem in the patch discovered by Andrew
> > Pogrebennyk in one of his tests. A new version has been developed by
> > Richard Fuchs and will be available for testing soon (this week).
> >
> 
> The backport is available in 2.8 repos as Andrew has announced. It will
> encode the ngcpct value by default with a safe_base64 function. Should
> work (tm) and fix those crappy peer implementations.