<div dir="ltr">Dear friends!<div>I am grateful to yall</div><div>It is fixed.</div><div>1) Remove network provided CLI from subscriber;</div><div>2) Add * to allowed cli</div><div><br></div><div>That's all!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 24, 2022 at 5:49 PM Leighton Brennan <<a href="mailto:leightonbrennan@gmail.com">leightonbrennan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">If you add * to the allowed cli’s under the subscriber that should do the trick. <br>
<br>
You may need to change some preferences related to Where the caller ID is presented i.e whether the caller ID is in the FROM or PAID headers. <br>
<br>
Best Regards<br>
Leighton Brennan<br>
<br>
> On 24 Mar 2022, at 11:44, mcapetta--- via Spce-user <<a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a>> wrote:<br>
> <br>
> Hi Anar,<br>
> <br>
> how and by whom the forwarding is done?<br>
> * By Sipwise NGCP using CFNA?<br>
> * or, by FREEPBX sending back 302?<br>
> * or, by FREEPBX using an internal call forward logic?<br>
> <br>
> Depending on the above case you have to correctly configure the outbound_from_user for the peer where the call is going.<br>
> <br>
> Regards<br>
> Marco<br>
> <br>
>> On 24/03/22 11:47, Anar Agayarov <<a href="mailto:anar@agayarov.com" target="_blank">anar@agayarov.com</a>> wrote:<br>
>> Dear Andreas,<br>
>> I am grateful for your instant response.<br>
>> Our providers are supporting any CID.<br>
>> But as I said, Sipwise is forcing to send subscriber's number as a CID.<br>
>> What I should change in my Sipwise side?<br>
>> On Thu, Mar 24, 2022 at 2:38 PM A. Waschefort <<a href="mailto:a.waschefort@anwadi.de" target="_blank">a.waschefort@anwadi.de</a> <mailto:<a href="mailto:a.waschefort@anwadi.de" target="_blank">a.waschefort@anwadi.de</a>>> wrote:<br>
>> __ Hello Anar<br>
>> For this feature you need "Clip no Screening" active from your Voip<br>
>> Provider. Without it not will work.<br>
>> Best Regards<br>
>> Andreas from AnWaDi.de<br>
>> ------------------------------------------------------------------------<br>
>> *Von:* Anar Agayarov <<a href="mailto:anar@agayarov.com" target="_blank">anar@agayarov.com</a> <mailto:<a href="mailto:anar@agayarov.com" target="_blank">anar@agayarov.com</a>>><br>
>> *Gesendet:* 24. März 2022 10:31:33 UTC<br>
>> *An:* spce-user <<a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a><br>
>> <mailto:<a href="mailto:spce-user@lists.sipwise.com" target="_blank">spce-user@lists.sipwise.com</a>>><br>
>> *Betreff:* [Spce-user] Number spoofing.<br>
>> Dear colleagues,<br>
>> I hope you are doing well.<br>
>> I have a problem with number spoofing.<br>
>> The situation is that:<br>
>> Sipwise is receiving calls from an upstream peer and sending them to<br>
>> FreePBX by SIP subscriber trunk. If the extension is not available,<br>
>> then the call is forwarded to the cellular number of the extension<br>
>> owner. FreePBX is using the same Sipwise trunk for outgoing calls.<br>
>> Problem is that: The cellular number is not getting the original<br>
>> Caller ID, but receiving Sipwise subscriber number.<br>
>> I did check with sngrep, FreePBX is sending an original CID to<br>
>> Sipwise, but Sipwise is changing to the Subscriber's number and<br>
>> sending it to a peer.<br>
>> Is there any way to make an exception for "spoofing"?<br>
>> P.S. The instance is working in Canada and this activity is not<br>
>> accounted as illegal.<br>
>> -- Best Regards<br>
>> Anar Agayarov<br>
>> Mit freundlichem Gruß | Kindest Regards<br>
>> Andreas Waschefort<br>
>> AnWaDi.de I NGN, VoIP, IOT & Data Solutions<br>
>> Gartenstrasse 15 | D-49406 Barnstorf | Germany<br>
>> P: +49 5442 5017 824<br>
>> M: +49 1520 888 4317<br>
>> Fax: +49 5442 5013 709 | Email: <a href="mailto:a.waschefort@anwadi.de" target="_blank">a.waschefort@anwadi.de</a><br>
>> <mailto:<a href="mailto:a.waschefort@anwadi.de" target="_blank">a.waschefort@anwadi.de</a>><br>
>> <a href="https://www.anwadi.de" rel="noreferrer" target="_blank">https://www.anwadi.de</a> <<a href="https://www.anwadi.de" rel="noreferrer" target="_blank">https://www.anwadi.de</a>><br>
>> +++ This email and its attachments (if applicable) may contain<br>
>> confidential and/or proprietary information. If you are not the<br>
>> intended recipient and you believe you have received this email in<br>
>> error, you may not use the content of this email, open, copy or<br>
>> distribute/share its attachments. In this case please inform the<br>
>> sender and immediately delete this email and its attachments (if<br>
>> applicable). +++<br>
>> -- <br>
>> Best Regards<br>
>> Anar Agayarov<br>
>> +995 555 592 676<br>
> <br>
> -- <br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
> <a href="http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com" rel="noreferrer" target="_blank">http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a><br>
<br>
-- <br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com" rel="noreferrer" target="_blank">http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><br></div><div>Best Regards</div><div dir="ltr">Anar Agayarov<div><br></div><div><div dir="ltr" style="font-size:small"><div>+995 555 592 676</div></div></div></div></div></div></div></div></div>