[Spce-user] Problem with e164_to_ruri?

Andrew Pogrebennyk apogrebennyk at sipwise.com
Fri Sep 20 07:38:35 EDT 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,
this issue has been fixed in the templates update to 3.0.17 which has
been released today.

On 09/18/2013 11:05 AM, Jon Bonilla (Manwe) wrote:
> Hi Barry and Mario
> 
> Thanks for the report. The e164_to_ruri does not work in parallel
> forking scenarios. This is because the preference is not applied to
> every branch. This will be solved in the next release of the
> templates later this week.
> 
> 
> cheers,
> 
> Jon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlI8M7sACgkQdegZtfziaKMAHAD/fMyO8kMN8C+nF/9d6gmE/b+o
5+btZmieZshAnNie//wBAIBs9C6Efr167se72EJpndNyH5teoCVv1TWfO59HRloR
=hG4Y
-----END PGP SIGNATURE-----




More information about the Spce-user mailing list