[Spce-user] inbound number assigned to a local subscriber

[Matthias Hohl]

Hello,

This is very simple.
You have just to add the CC in the rewrite rule you apply as inbound rewrite rule for caller. There you have to do a regex to remove the zero and change it to the CC.

But normally, you get from a peering partner a full e164 number... like 491234 or +491234




> Am 10.11.2020 um 17:09 schrieb Diego Ramos <diego.ramos1 at gmail.com>:
> 
> 
> Hi, 
> 
> I have a peering and I am receiving an external call with destination caller_ac + number, how do I rewrite it to caller_cc + caller_ac + number so that it finds the subscriber's alias?
> 
> Diego Ramos
> 
>> Em ter., 10 de nov. de 2020 às 05:05, Marco Capetta <mcapetta at sipwise.com> escreveu:
>> Hi Diego,
>> 
>> There is not incoming routing table in NGCP.
>> The inbound Rewriting Rules associated to the Peer are applied to the incoming caller and callee number.
>> Then the resulting callee number is looked through the subscriber's primary number or subscriber's alias numbers.
>> 
>> Regards
>> Marco
>> 
>> 
>>> On 09/11/20 22:38, Diego Ramos wrote:
>>> Hi,
>>> 
>>> I already configured the inbound peering rules but I don't know how to direct the call to the subscriber. How do I direct a call that arrives through peering to a caller?
>>> 
>>> Diego Ramos
>>> 
>>> 
>> 
>> -- 
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20201113/f290f9fc/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2373 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20201113/f290f9fc/attachment-0002.p7s>