[Spce-user] ngcp-www-csc Addressbook
Marc Storck
mstorck at voipgate.com
Fri Jun 7 04:55:18 EDT 2013
Hello Daniel,
yes, it works for all the numbers which do _not_ share the Country Code of
the subscriber.
In my case I have a subscriber with CC=352. When I add the phone number
0035223456789 to a contact, the addressbook "normalizes" the number to
023456789. When adding a phone number which does not share the same CC as
the subscriber, e.g. 004923456789, the addressbook normalizes the number
to +4923456789.
I'm not sure if the International Access Code "00" is hardcoded into the
system, some countries use 011 or 0011
Best regards, Marc
-----Original Message-----
From: Daniel Grotti <dgrotti at sipwise.com>
Date: Friday, June 7, 2013 10:42 AM
To: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
Subject: Re: [Spce-user] ngcp-www-csc Addressbook
>Hello Marc,
>
>Please use the E164 to add a new address contact.
>For example if you write:
>
>00441234567
>
>the system will add the number :
>
>+441234567
>
>
>br,
>Daniel
>
>
>
>On 06/06/2013 07:22 PM, Marc Storck wrote:
>> Good evening,
>>
>> I've found that when adding records to the addressbook via the CSC web
>> interface, the NGCP always prefixes phone numbers within the same
>>country
>> code (or entered in national format e.g. 23456789) with a 0 regardless
>>of
>> the Rewrite Rule Set defined for the domain/user. This default behaviour
>> causes problems in countries where the trunk prefix
>> (Verkehrsausscheidungsziffer) is not 0 (NANPA Countries (US, Canada,
>> Bermuda, Puerto Rico, US Virgin Islands, Northern Marianas, Guam,
>>American
>> Samoa, Sint Marteen), Belarus, Hungary, Lithuania, Russia) or where no
>> trunk prefix is used (Czech Republic, Denmark, Estonia, Greece, Italy
>>(the
>> eventual 0 is part of the phone number and must be included when
>> dialling), Latvia, Luxembourg, Malta, Monaco, Norway, Poland, Portugal,
>> San Marino (see Italy), Spain, Vatican City (see Italy).
>>
>> (The call forward and call barring seems to be unaffected as the numbers
>> are stored in E164 format.)
>>
>> I'm not sure how this can be solved. Eventually the "inbound rewrite
>>rules
>> for callee" for the domain's/user's Rewrite Rule Set could be used to
>> validate the number entered into the addressbook against the Match
>> Pattern. If any pattern matches, the number is stored unmodified and
>> considered valid, unless it is possible to store these numbers in E164
>>as
>> well.
>>
>> Best regards, Marc
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>
>_______________________________________________
>Spce-user mailing list
>Spce-user at lists.sipwise.com
>http://lists.sipwise.com/listinfo/spce-user
>
Marc Storck
--
Chief Information Officer
voipGATE S.A.
http://mstorck.voipgate.tel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6079 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130607/aa5a6e09/attachment-0001.p7s>
More information about the Spce-user
mailing list