[Spce-user] Number Porting

[Julian Seifert]

Hi again,

I forgot to mention that there are rewrite rules which try to apply the value of ${callee_lnp_prefix} and prepend
the called number with that. Including that - that's the gist of it, right? 

kind regards,

  julian

________________________________________
Von: Spce-user [spce-user-bounces at lists.sipwise.com]" im Auftrag von "Julian Seifert [js at dacor.de]
Gesendet: Donnerstag, 28. April 2016 16:01
An: Andreas Granig; spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Number Porting

Hi Andreas,

thank you for providing a quick overview.
(btw. I really like the 4.3.1 release - the call verify tool is great and I appreciate LNP support being
implemented )

Just to clarify:  (with enabled stuff in config.yml)
My subscriber A makes an outgoing call, ngcp looks at the number and recognizes its not local.
As it is not local it tries to look it up in local LNP-DB. Let's say there is an entry for the called number
like D001 (Deutsche Telekom for example). This value gets assigned to ${callee_lnp_prefix}.
I can then use D001 as callee prefix in my peering rules to route the call via the peering group I prefer
for D001?


Can't wait to see the updated docs :) Is there a timeframe for release of 4.4?

kind regards,

  Julian
________________________________________
Von: Spce-user [spce-user-bounces at lists.sipwise.com]" im Auftrag von "Andreas Granig [agranig at sipwise.com]
Gesendet: Donnerstag, 28. April 2016 10:13
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Number Porting

Hi,

LNP docs are catching up at the moment and are going to be published soon.

In general, there are two different approaches.

First, the lock level "ported". The request this has been implemented
for is targeting the use case of "LNP light" if you want, where you set
a forward to a certain number (e.g. "<carrier prefix of new
owner><number>") and set the lock level to "ported". This causes the
subscriber to not be able to register and call anymore, however a call
to this number is triggering a forward to the destination. After like a
grace period of 3 months, you terminate the subscriber.

The other thing is the local LNP database support. You have to enable it
in config.yml at "kamailio.proxy.lnp.enable: yes" and
"kamailio.proxy.lnp.type: local". That way, if a number is not assigned
to a subscriber, an lnp lookup is done in the DB, populating certain
vars which you then can use in the new lnp rewrite rules to for example
prefix the number with the code ("${callee_lnp_prefix}" would be the
typical one you'd use).

Based on that rewritten number, you can put carrier prefixes in the
callee prefix of peering rules to force certain prefixes via certain
peer groups.

There is also a new value for the force outbound calls to peer
preference, where you can force a call back to a peer if it came from a
peer in case the lnp lookup yielded a result.

There are more values and settings to fine-tune (e.g. a default lnp
prefix for subs/doms/peers which are written to CDRs), more on that in
the upcoming documentation. Also, the upcoming 4.4 release allows to
perform lnp lookups before doing the subscriber lookup to handle ported
out numbers without having to terminate them on the platform.

Andreas

On 04/27/2016 04:19 PM, Matthias Hohl wrote:
> Hello,
>
>
>
> can anybody explain the „number porting“ function in the 4.3.1 version?
>
> How does it work and how can I use it?
>
>
>
> What about the new lock level “ported”? What does it do? Must I also set
> the “status to “locked” to activate the ported status?
>
>
>
> I searched the handbook but couldn’t find any information about that topic.
>
>
>
>
>
>
>
> I also did some tests:
>
> I set a subscriber to lock level “ported” and also create a “LNP
> Carrier” with a prefix #99# and add the ported number from the
> subscriber to the ported number with start date yesterday.
>
> But if I try to call this number from another subscriber, I just get the
> voice message, that this subscriber is not available.
>
>
>
>
>
> So for what is this feature for?
>
> What would the right way to handle ported numbers from our own block to
> another carrier?
>
> Just terminate the subscriber and notice it elsewhere in excel to know,
> that this number is ported away and should not be give away a second
> time to another subscriber?
>
>
>
>
>
> Maybe you can give me some advices.
>
> Thanks.
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user