[Spce-user] Number portability issue.

[Matthew Ogden]

Thanks, I'm sure everyone appreciates it.

I assume you using API to create the ported entries from the Number porting
database as well?

Kind regards
ᐧ

On Mon, 8 Jun 2020 at 11:28, Anar Agayarov <anar at agayarov.com> wrote:

> Firstly I did create LNP rewrite rule for the domain's rewrite rule group.
>
> LNP Rewrite Rules for Callee:
>
> Match Pattern: ^([0-9]+)$
> Replacement Pattern: ${callee_lnp_prefix}#\1  This pattern is adding "tech
> prefix"
>
>
> In the Number Porting menu, LNP carrier created with the prefix.  This
> prefix will be added to the callee part by LNP Rule. (for example, 732)
>
> Create a ported number.
>
> Now, when you will dial ported number, it will ignore peering prefix and
> will try to dial 732#995XXX
>
> Go to peering servers, and add Outbound rule.
>
> Callee Pattern: ^sip:732  - this is the prefix when we add it to LNP
> carrier.
>
> Sometimes peering partners are not accepting tech prefix, so you should
> remove it before sending it to the trunk.
>
> Create a new rewrite rule set for peering server:
>
> Outbound rewrite rules for Callee
>
> Match pattern: ^([0-9]+)#([1-9][0-9]+)$
> Replacement pattern: \2
> Description: Removing technical prefix splitting by the sign #.
>
>
>
> That is all.
>
>
> On Mon, Jun 8, 2020 at 1:06 PM Matthew Ogden <matthew at tenacit.net> wrote:
>
>> HI Anar
>>
>> I'm sure the spce community would like to hear your method, its slowly
>> becoming a big problem for all countries as competition heats up.
>>
>> Kind Regards
>> ᐧ
>>
>> On Mon, 8 Jun 2020 at 09:31, Anar Agayarov <anar at agayarov.com> wrote:
>>
>>> Thank you, for your reply.
>>>
>>> It was done already.
>>>
>>> On Mon, Jun 8, 2020 at 11:30 AM Victor Seva <vseva at sipwise.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> On 6/7/20 3:19 PM, Anar Agayarov wrote:
>>>> > I am not sure that it is possible by LNP.  I would be most grateful to
>>>> > you if you could help me in sorting this out.
>>>>
>>>> https://www.sipwise.org/doc/mr8.4.1/sppro/?_href=ar01s06.html#local_lnp
>>>>
>>>> The Sipwise C5 platform comes with two ways of accomplishing local
>>>> number porting (LNP):
>>>>
>>>> one is populating the integrated LNP database with porting data,
>>>> the other is accessing external LNP databases via the Sipwise LNP daemon
>>>> using the LNP API.
>>>>
>>>> NOTE: Accessing external LNP databases is available for PRO and CARRIER
>>>> products only.
>>>>
>>>> Cheers,
>>>> Victor
>>>>
>>>> --
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>>>
>>>
>>>
>>> --
>>>
>>> Best Regards
>>> Anar Agayarov
>>>
>>> +994555644152
>>> --
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>>
>>
>>
>> --
>>
>>
>>
>>
>>
>> *Matthew Ogden*
>>
>> Management
>>
>> TenacIT
>>
>>
>>
>>
>>
>> *Strategic IT Consulting *•* Advanced Networking *• *Virtualisation*
>>
>> *Custom Development *• *Hosting *• *Syspro Support  *• *MS Licensing*
>>
>> National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
>> matthew at tenacit.net
>>
>> CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
>> http://www.tenacit.net
>>
>>
>>
>
>
> --
>
> Best Regards
> Anar Agayarov
>
>
>

-- 





*Matthew Ogden*

Management

TenacIT





*Strategic IT Consulting *•* Advanced Networking *• *Virtualisation*

*Custom Development *• *Hosting *• *Syspro Support  *• *MS Licensing*

National Tel: 041 10 10 100 | Cell: 084 205 4445 | Email:
matthew at tenacit.net

CT Tel: 021 201 0333 | Skype Name: matthew.ogden | Web:
http://www.tenacit.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200608/45b80552/attachment-0002.html>