[Spce-user] Number spoofing.

[A. Waschefort]

Hello Anar

For this feature you need "Clip no Screening" active from your Voip Provider. Without it not will work.
Best Regards
Andreas from AnWaDi.de


-------- Ursprüngliche Nachricht --------
Von: Anar Agayarov <anar at agayarov.com>
Gesendet: 24. März 2022 10:31:33 UTC
An: spce-user <spce-user at lists.sipwise.com>
Betreff: [Spce-user] Number spoofing.

Dear colleagues,
I hope you are doing well.
I have a problem with number spoofing.
The situation is that:

Sipwise is receiving calls from an upstream peer and sending them to
FreePBX by SIP subscriber trunk. If the extension is not available, then
the call is forwarded to the cellular number of the extension owner.
FreePBX is using the same Sipwise trunk for outgoing calls.

Problem is that: The cellular number is not getting the original Caller ID,
but receiving Sipwise subscriber number.

I did check with sngrep, FreePBX is sending an original CID to Sipwise, but
Sipwise is changing to the Subscriber's number and sending it to a peer.

Is there any way to make an exception for "spoofing"?
P.S. The instance is working in Canada and this activity is not accounted
as illegal.

-- 

Best Regards
Anar Agayarov

Mit freundlichem Gruß | Kindest Regards

Andreas Waschefort

AnWaDi.de I NGN, VoIP, IOT & Data Solutions

Gartenstrasse 15 | D-49406 Barnstorf | Germany
P: +49 5442 5017 824
M: +49 1520 888 4317
Fax: +49 5442 5013 709 | Email: a.waschefort at anwadi.de
https://www.anwadi.de
 

+++ This email and its attachments (if applicable) may contain confidential and/or proprietary information. If you are not the intended recipient and you believe you have received this email in error, you may not use the content of this email, open, copy or distribute/share its attachments. In this case please inform the sender and immediately delete this email and its attachments (if applicable). +++
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20220324/d60af579/attachment-0002.html>