[Spce-user] CLIR issue - Blocking Outgoing CLI coming in from Subscriber

Bob Fryer bob at netintegrity.com.au
Mon Aug 5 04:30:11 EDT 2013


Jon,

Sorry for the delay on thanking you for your post, but I put a few more days into understanding the CLIR function and indeed the CLI functionality a little deeper before I responded. 

Your post helped a lot in clearing up a misconception I had, one that was further confused by a Proxy (between SIPWise and the Carrier - the result of an earlier post) that was stripping the Privacy flag information.

Finally got a "Blocked" CLI come through on the Mobile after changes on the Proxy.

Again, appreciate your help.

Regards

Bob




-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Jon Bonilla (Manwe)
Sent: Thursday, 1 August 2013 9:29 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] CLIR issue - Blocking Outgoing CLI coming in from Subscriber

El Thu, 1 Aug 2013 08:25:39 +1000
"Bob Fryer" <bob at netintegrity.com.au> escribió:

> Dear List,

Hi Bob

> My understanding was that under the subscriber, with CLIR enabled, 
> that this would "block out going CLI's)

Yes. You can set permanent clir or per call basis. Selecting that preference will make all calls to be callerid restricted.


> 
> As the client does not receive calls via SIPWise (as mentioned no 
> incoming), under Masterdata for the subscriber, we do not set an E.164 
> number (however we have also tested it with one added (with no change).
> 
> What occurs is that the Subscribers PBX is sending through the 
> extension that they are dialling from e.g. extension 201 in this case 
> and then the "loose" rewrite rules kick in and add a 0011, so the 
> number goes out as
> 0011201 and naturally this is received by the Caller.
> 
> Can you provide a little more information on any setting prerequisites 
> for the CLIR function to work, or have I got it totally wrong.


As you will see in the logs you send or even with a network capture, the CLIR is working well.

When you select CLIR, the From displayname  is anonymized. And that's the
*only* information a subscriber would receive.

In case the call goes to a peer, for regulatory reasons, the From header suffers the same anonymization but the NPN is also provided in the PAI header.
Another header is also added, the Privacy header asking the peers to carry on the CLIR.

In other words, in peer traffic, the cli should be sent and it is, and anonymization is asked via the From header manipulaton and Privacy headers.
It's up to the last carrier to hide the callerid to its subscribers as the spce would do in case such a call comes in.

Checking your logs:



> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Caller anonymization - R=sip:0418191919 at sip.ourdomain.com.au
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>: 
> Call to SIP Peering - R=sip:61418191919 at sip.ourdomain.com.au
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Prepare From username setting -
> R=sip:61418191919 at 111.23.25.44:5060;transport=udp
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Setting caller_cli_userprov/caller_domain_userprov
> '0011201 at sip.ourdomain.com.au' for upn  - 
> R=sip:61418191919 at 111.23.25.44:5060;transport=udp
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Anonymizing From display-name -
> R=sip:61418191919 at 111.23.25.44:5060;transport=udp ID=09db2e 
> f55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Setting From to 'Anonymous <sip:0011201 at sip.ourdomain.com.au>' -
> R=sip:61418191919 at 113.20
> .24.83:5060;transport=udp
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au


The displayname is set to Anonymous. I see that the username/domain are not and not 100% sure if they should. Depends on the implementation. But if you check the ngrep capture you'll see the Privacy header

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Prepare PAI username setting -
> R=sip:61418191919 at 111.23.25.44:5060;transport=udp ID=09db2ef 
> 55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Setting caller_cli_netprov/caller_domain_netprov
> '0011201 at sip.ourdomain.com.au' for npn -  
> R=sip:61418191919 at 111.23.25.44:5060;transport=udp
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au

> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:
> Setting PAI to '<sip:0011201 at sip.ourdomain.com.au>' -
> R=sip:61418191919 at 111.23.25.44:5060
> ;transport=udp 
> ID=09db2ef55acc4261350a46a36d774cd4 at sip.ourdomain.com.au
> Aug  1 07:48:09 sipwise01 /usr/sbin/kamailio[2362]: INFO: <script>:

The PAI with the NPN is added always in carrier calls. A subscriber wouldn't receive this information in case of CLIR call.



cheers,

Jon




More information about the Spce-user mailing list