[Spce-user] Problem with new peer : ngcp-lb at 82.139.112.32:5060; ngcpct='sip%3A10.18.3.200%3A5080'
Jon Bonilla (Manwe)
jbonilla at sipwise.com
Tue Jun 18 17:58:43 EDT 2013
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130618/a2ac00d0/attachment-0001.asc>
More information about the Spce-user
mailing list