{"id":922,"date":"2015-10-15T23:59:13","date_gmt":"2015-10-15T21:59:13","guid":{"rendered":"https:\/\/marc.storck.lu\/blog\/?p=922"},"modified":"2016-01-05T22:46:41","modified_gmt":"2016-01-05T21:46:41","slug":"the-fairy-tale-of-clip-no-screening","status":"publish","type":"post","link":"https:\/\/marc.storck.lu\/blog\/2015\/10\/the-fairy-tale-of-clip-no-screening\/","title":{"rendered":"CLIP No Screening a fairy tale?"},"content":{"rendered":"<p>VoIP protocols have made the manipulation of the &#8220;CallerID&#8221; easier for the regular IPBX user or admin. So users started to question the industry to relax &#8220;CallerID screening&#8221; to display\u00a0the original calling party number on call forwarding (done by the PBX), or the number of the company&#8217;s Headquarters and so on.\u00a0While &#8220;CallerID screening&#8221; has been around for a very long time and has been a default feature in most cases,\u00a0only a few customers were able to\u00a0benefit\u00a0from a more relaxed screening.<\/p>\n<p>With the rise of ITSPs, marketing departments invented &#8220;CLIP No Screening&#8221;, a kind of &#8220;send any CallerID and we&#8217;ll accept it&#8221;. I suppose most of you understand the value of the average email with a faked sender address, well imagine what kind of phone calls you&#8217;d get once everyone would offer &#8220;CLIP No Screening&#8221; to anybody who asked for it.<!--more--><\/p>\n<p>Luckily or sadly &#8220;CLIP No Screening&#8221; isn&#8217;t always implemented the same way. At large there 2 types of implementations:<\/p>\n<h2>#1 CLIP No Screening Implementation:<\/h2>\n<p>Forwards\u00a0what the customer sends, don&#8217;t check, don&#8217;t sanitize, actually do nothing to the &#8220;CallerID&#8221; provided by the customer (except maybe apply\u00a0some dial plan manipulation to convert the number to E.164 format).<\/p>\n<h2>#2\u00a0CLIP No Screening Implementation:<\/h2>\n<p>This actually works pretty the same as #1 except that the &#8220;CallerID&#8221; provided by the customer&#8217;s equipment is transported along the real Calling Line ID of the customer&#8217;s SIP trunk. In order to distinguish both numbers, these 2 numbers are usually\u00a0called &#8220;User Provided Number (UPN)&#8221; and &#8220;Network Provided Number (NPN)&#8221; respectively.<br \/>\nThe UPN is\u00a0transported in the &#8220;From:&#8221; header within SIP and as an &#8220;Additional Calling Party Number&#8221; in\u00a0a &#8220;Generic Number&#8221; information element within\u00a0SS7(1). The NPN\u00a0is transported in the &#8220;P-Asserted-Identity:&#8221; Header within SIP and as the &#8220;Calling Line Identification&#8221; within SS7.<\/p>\n<p>The second implementation allows to show a different &#8220;CallerID&#8221; to the called party\u00a0but still allows to determinate the source of the call in case of need.<\/p>\n<p>Unfortunately the second implementation doesn&#8217;t work for each destination. Some network operators don&#8217;t support to display the additional number, others\u00a0are blocking the feature. It is open\u00a0to discussion if blocking the 2nd implementation drives more users and service providers to use the first implementation.<\/p>\n<p>&nbsp;<\/p>\n<p>(1) <a href=\"https:\/\/en.wikipedia.org\/wiki\/Signalling_System_No._7\" target=\"_blank\">Signalling System No. 7<\/a>: telephony signalling protocols used in most public switched telephone networks.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>VoIP protocols have made the manipulation of the &#8220;CallerID&#8221; easier for the regular IPBX user or admin. So users started to question the industry to relax &#8220;CallerID screening&#8221; to display\u00a0the original calling party number on call forwarding (done by the PBX), or the number of the company&#8217;s Headquarters and so on.\u00a0While &#8220;CallerID screening&#8221; has been &hellip; <a href=\"https:\/\/marc.storck.lu\/blog\/2015\/10\/the-fairy-tale-of-clip-no-screening\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;CLIP No Screening a fairy tale?&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[72],"tags":[],"class_list":["post-922","post","type-post","status-publish","format-standard","hentry","category-voip"],"_links":{"self":[{"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/posts\/922","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/comments?post=922"}],"version-history":[{"count":5,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/posts\/922\/revisions"}],"predecessor-version":[{"id":928,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/posts\/922\/revisions\/928"}],"wp:attachment":[{"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/media?parent=922"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/categories?post=922"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/marc.storck.lu\/blog\/wp-json\/wp\/v2\/tags?post=922"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}