[Spce-user] Cannot had an E164 number with a SN starting with 0

[Daniel Grotti]

Hi Matthew,
I already relplied to you about that:


you need to change /etc/ngcp-congfig/config.yml:

routing:
      ac_regex: '[1-9]\d{0,4}'
      cc_regex: '[1-9]\d{0,3}'
      sn_regex: '[1-9]\d+'



setting something like:

routing:
      ac_regex: '[1-9]\d{0,4}'
      cc_regex: '[1-9]\d{0,3}'
      sn_regex: '[0-9]\d+'



then apply the changes.

Daniel




On 02/03/2014 09:20 AM, Matthew Ogden wrote:
> Hi Guys,
> 
>  
> 
> Can I just go edit this in the mysql DB and it will work normally?
> 
>  
> 
> *From:*Matthew Ogden [mailto:matthew at tenacit.net
> <mailto:matthew at tenacit.net>]
> *Sent:* 30 January 2014 02:53 PM
> *To:* spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
> *Subject:* Cannot had an E164 number with a SN starting with 0
> 
>  
> 
> Hi
> 
>  
> 
> I am running SPCE 2.8 (and templates are on 2.8.18 – so I’ve run update
> recently), but when I am unable to create a subscriber with a 0 in the
> SN (The CC and nc are normal the same as other subscribers, and the only
> 0 is in the SN). (In our country its quite normal to have a 0 starting
> in the SN)
> 
>  
> 
> What can I do as a workaround to this, as the number is about to port to
> my network tomorrow. (I assume it’s a bug, and that an SN starting with
> 0 is actually allowed?
> 
>  
> 
> Kind Regards
> 
> Matthew
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>