[Spce-user] Clir - Hiding caller ID

Theo axessofficetheo at gmail.com
Tue Feb 23 06:08:37 EST 2016


Hi

I had another look - you are correct it seems. Apologies. It's the next
step in the chain that strips the flag hence it doesn't arrive upstream.

Thanks!



On Tue, Feb 23, 2016 at 12:14 PM, Jon Bonilla (Manwe) <manwe at sipdoc.net>
wrote:

> El Tue, 23 Feb 2016 11:30:24 +0200
> Theo <axessofficetheo at gmail.com> escribió:
>
> > Hi
> >
> > I am having some issues hiding our caller ID through some interconnects.
> > Sipwise does add the privacy flag to the header but does this in the
> "from
> > header". The response from our interconnect partners is that this is not
> > according to RFC:
> >
> > "the caller here attempted to anonymize their call using only the
> > displayname of the FROM header." They did not include a P-Asserted
> Identity
> > / Privacy header. The displayname of the FROM header is optional to begin
> > with, and while it's recommended that it be displayed at the far-end UI,
> > the far-end carriers are not required to use it at all."
> >
> > So - are they correct in saying this and if so, how would we hide the
> > number the correct way?
> >
>
>
> When you hide the callerid and send a call to a peer, the ngcp system adds
> the
> Privacy and the PAI headers by default.
>
> When sending the call to a subscriber it does not. It only sends anonymous
> in
> the from header.
>
> could you paste one of those INVITE requests?
>
>
> cheers,
>
> Jon
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160223/5dbba3a9/attachment-0001.html>


More information about the Spce-user mailing list