Requirements for SHAKEN service providers
There are three requirements for a Service Provider to be included in the SHAKEN ecosystem: 1. Service Provider must have an OCN 2. Service Provider must have a current Form 499-A filed with the FCC 3. Service Provider must have direct access to telephone numbers from the North American Number Plan Administrator (NANPA) and National Pooling Administrator (NPA) My company meets the first two requirements as we have an OCN as an interconnected voice provider (IPES) and a current Form 499-A filed, however we obtain telephone numbers from our carriers, and don't have our own numbers assigned from NANPA and NPA. How do we determine if we are eligible to obtain numbers and thus be qualified to play in the SHAKEN ecosystem? David ---------------------------------------------------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
I believe if you look at the footnote on the third point you will find that they have realized the problems it will cause. I don't know of anything providing a path around it yet, but at least they acknowledge the rule is not perfect? "While the access limitation is reasonable, signing a given call should not be limited to only the pool of numbers available to the provider via direct access. In other words, per ATIS-100074, 5.2.3, under correct conditions a qualified service provider (SP) must be allowed to sign leased numbers as well as other numbers belonging to an OCN not assigned to that qualified SP insofar as the SP can properly verify the customer's authorized use of that number." On Thu, Mar 26, 2020 at 2:52 PM Zilk, David <David.Zilk at cdk.com> wrote:
There are three requirements for a Service Provider to be included in the SHAKEN ecosystem:
1. Service Provider must have an OCN
2. Service Provider must have a current Form 499-A filed with the FCC
3. Service Provider must have direct access to telephone numbers from the North American Number Plan Administrator (NANPA) and National Pooling Administrator (NPA)
My company meets the first two requirements as we have an OCN as an interconnected voice provider (IPES) and a current Form 499-A filed, however we obtain telephone numbers from our carriers, and don?t have our own numbers assigned from NANPA and NPA. How do we determine if we are eligible to obtain numbers and thus be qualified to play in the SHAKEN ecosystem?
David ------------------------------ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
So connecting the dots between all the FCC statements we know of.......I think the following statements are still true: 1. A company can attest all their TNs (whether leased or owned) if they have a STIR/SHAKEN certificate, 2. Only those companies with a STIR/SHAKEN certificate can attest calls. 3. Only those companies with a state certification or FCC License can get a STIR/SHAKEN certificate because only companies with a state certification or FCC License are able to obtain direct access to NANPA. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111 On 2020-03-26 02:48 PM, Kent Adams wrote:
I believe if you look at the footnote on the third point you will find that they have realized the problems it will cause. I don't know of anything providing a path around it yet, but at least they acknowledge the rule is not perfect?
"While the access limitation is reasonable, signing a given call should not be limited to only the pool of numbers available to the provider via direct access. In other words, per ATIS-100074, 5.2.3, under correct conditions a qualified service provider (SP) must be allowed to sign leased numbers as well as other numbers belonging to an OCN not assigned to that qualified SP insofar as the SP can properly verify the customer's authorized use of that number."
On Thu, Mar 26, 2020 at 2:52 PM Zilk, David <David.Zilk at cdk.com> wrote:
There are three requirements for a Service Provider to be included in the SHAKEN ecosystem:
1. Service Provider must have an OCN
2. Service Provider must have a current Form 499-A filed with the FCC
3. Service Provider must have direct access to telephone numbers from the North American Number Plan Administrator (NANPA) and National Pooling Administrator (NPA)
My company meets the first two requirements as we have an OCN as an interconnected voice provider (IPES) and a current Form 499-A filed, however we obtain telephone numbers from our carriers, and don?t have our own numbers assigned from NANPA and NPA. How do we determine if we are eligible to obtain numbers and thus be qualified to play in the SHAKEN ecosystem?
David ------------------------- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (3)
-
David.Zilk＠cdk.com -
kent＠sip.us -
marylou＠backuptelecom.com