[Spce-user] Best practice handling with ported numbers in 4.4.1

Julian Seifert js at dacor.de
Fri Jul 1 11:08:00 EDT 2016


without further looking (not currently with access to our lab)
you can try to set "force_inbound_calls_to_peer" to true for this subscriber. I did not have time to do
proper testing with the porting-feature yet but in the next few weeks I hope to find a window.
It would be interesting to see if the header gets manipulated properly if you configure the
LNP-settings for this number. (Did you do that?)

kind regards,

  Julian Seifert
Von: Spce-user [spce-user-bounces at lists.sipwise.com]" im Auftrag von "Matthias Hohl [matthias.hohl at telematica.at]
Gesendet: Freitag, 1. Juli 2016 16:24
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] Best practice handling with ported numbers in 4.4.1


today i tried something with a subscriber which is currently not in use cause the number is ported.

I want the ported number is not anymore a local call.
I want that if a subscriber calls another subscriber that still exists but which number is ported away to another carrier, that the call goes out to our peering partner.

How can I solve this right now?

I tried to set the subscriber to lock level “ported” but I always get the same message “The number you are trying to reach is currently not available. Please try again later.”
Also if I edit the subscriber and delete the E164 number the I can hear the same message (maybe a bug? Cause if totally delete the e164 number, the subscriber should has no number and should not be reachable or not?)

But anyway, what is the right behavior to handle with ported numbers?
At the moment it looks like that only deleting the whole subscriber will solve my problem.
But then I have the problem that I have no “warning” that I create another subscriber with a number that was already given to another subscriber that have ported away his number.
So it would be good if the subscriber could be active, but if I set the lock level to “ported” to call would be going out to the peering, instead of checking if the Callee is local.

Thank you for your informations.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160701/090b0a34/attachment-0001.html>

More information about the Spce-user mailing list