Disclosing Restricted Caller ID to customer
Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) *Nick Olsen* Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763
You don?t know if it really is harassment. Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data. From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Nick Olsen <nick at floridavirtualsolutions.com> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 [Image removed by sender.]
Who is your customer ? The Caller or the Called Entity ? Your obligations are to your paying customer?.. (which in this case is the Called Entity) You have zero obligations to the caller?. If your client is asking for the information, and you have it, you may choose to provide it. What your client does with it, is not your concern. (Law enforcement overrides your agreement of keeping your clients information confidential ) My two cents ! Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Matthew Crocker Sent: Monday, September 9, 2019 1:02 PM To: Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer You don?t know if it really is harassment. Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data. From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 [Image removed by sender.]
My customer is the called Party. The caller blocking their caller ID is supposedly the source of the harassment. *Nick Olsen* Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 On Mon, Sep 9, 2019 at 1:13 PM Faisal Imtiaz <faisal at snappytelecom.net> wrote:
Who is your customer ? The Caller or the Called Entity ?
Your obligations are to your paying customer?.. (which in this case is the Called Entity)
You have zero obligations to the caller?.
If your client is asking for the information, and you have it, you may choose to provide it.
What your client does with it, is not your concern.
(Law enforcement overrides your agreement of keeping your clients information confidential )
My two cents !
Faisal Imtiaz
Snappy Internet & Telecom
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net
*From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Matthew Crocker *Sent:* Monday, September 9, 2019 1:02 PM *To:* Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org *Subject:* Re: [VoiceOps] Disclosing Restricted Caller ID to customer
You don?t know if it really is harassment.
Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data.
*From: *VoiceOps <voiceops-bounces at voiceops.org> on behalf of Nick Olsen < nick at floridavirtualsolutions.com> *Date: *Monday, September 9, 2019 at 12:50 PM *To: *"voiceops at voiceops.org" <voiceops at voiceops.org> *Subject: *[VoiceOps] Disclosing Restricted Caller ID to customer
Greetings all, Had an interesting case come up today that I wanted some feedback on.
Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM.
Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full.
Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement)
*Nick Olsen*
Network Engineer
Office: 321-408-5000 x103
Mobile: 321-794-0763
[image: Image removed by sender.]
Can?t speak for US, but at least in Canada what you described wont fly. You have obligations as a carrier to honour restricted caller id received from PSTN if the caller choose to withhold it. If your paying customer is not happy with a private incoming call, they should contact police as someone earlier suggested. If deemed necessary, police or court or whatever authority will reach to you for the private caller id. If you just disclose caller id on your customers request as you described, you may just as well disregard rpid / whatever privacy flag you have from pstn all together. But people dont do that afaik.
On Sep 9, 2019, at 13:13, Faisal Imtiaz <faisal at snappytelecom.net> wrote:
Who is your customer ? The Caller or the Called Entity ?
Your obligations are to your paying customer?.. (which in this case is the Called Entity) You have zero obligations to the caller?. If your client is asking for the information, and you have it, you may choose to provide it. What your client does with it, is not your concern. (Law enforcement overrides your agreement of keeping your clients information confidential )
My two cents !
Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Matthew Crocker Sent: Monday, September 9, 2019 1:02 PM To: Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer
You don?t know if it really is harassment.
Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data.
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Nick Olsen <nick at floridavirtualsolutions.com> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer
Greetings all, Had an interesting case come up today that I wanted some feedback on.
Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM.
Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full.
Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement)
Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Cool, Looks like it is similar laws here in the USA too.. I stand corrected? https://www.federalregister.gov/documents/2017/12/01/2017-25917/calling-numb... Though I am curious about a scenario? Client is running his own pbx, and running Homer .. Would the Caller ID be visible to them in the homer trace ? Regards Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net From: Victor C <victor.chukalovskiy at gmail.com> Sent: Monday, September 9, 2019 1:23 PM To: Faisal Imtiaz <faisal at snappytelecom.net> Cc: Matthew Crocker <matthew at corp.crocker.com>; Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer Can?t speak for US, but at least in Canada what you described wont fly. You have obligations as a carrier to honour restricted caller id received from PSTN if the caller choose to withhold it. If your paying customer is not happy with a private incoming call, they should contact police as someone earlier suggested. If deemed necessary, police or court or whatever authority will reach to you for the private caller id. If you just disclose caller id on your customers request as you described, you may just as well disregard rpid / whatever privacy flag you have from pstn all together. But people dont do that afaik. On Sep 9, 2019, at 13:13, Faisal Imtiaz <faisal at snappytelecom.net<mailto:faisal at snappytelecom.net>> wrote: Who is your customer ? The Caller or the Called Entity ? Your obligations are to your paying customer?.. (which in this case is the Called Entity) You have zero obligations to the caller?. If your client is asking for the information, and you have it, you may choose to provide it. What your client does with it, is not your concern. (Law enforcement overrides your agreement of keeping your clients information confidential ) My two cents ! Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net<mailto:Support at Snappytelecom.net> From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> On Behalf Of Matthew Crocker Sent: Monday, September 9, 2019 1:02 PM To: Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>>; voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer You don?t know if it really is harassment. Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data. From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 [Image removed by sender.] _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
If they are an end-user the SIP INVITE should be sanitized by the providing carrier. Carrier <-> Carrier include CallerID with privacy bits set Carrier -> End-user include Sanitized CallerID (i.e. Anonymous or Private in the From header, no Remote-Party-ID) From: Faisal Imtiaz <faisal at snappytelecom.net> Date: Monday, September 9, 2019 at 2:02 PM To: Victor C <victor.chukalovskiy at gmail.com> Cc: Matthew Crocker <matthew at corp.crocker.com>, Nick Olsen <nick at floridavirtualsolutions.com>, "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: RE: [VoiceOps] Disclosing Restricted Caller ID to customer Cool, Looks like it is similar laws here in the USA too.. I stand corrected? https://www.federalregister.gov/documents/2017/12/01/2017-25917/calling-numb... Though I am curious about a scenario? Client is running his own pbx, and running Homer .. Would the Caller ID be visible to them in the homer trace ? Regards Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net From: Victor C <victor.chukalovskiy at gmail.com> Sent: Monday, September 9, 2019 1:23 PM To: Faisal Imtiaz <faisal at snappytelecom.net> Cc: Matthew Crocker <matthew at corp.crocker.com>; Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer Can?t speak for US, but at least in Canada what you described wont fly. You have obligations as a carrier to honour restricted caller id received from PSTN if the caller choose to withhold it. If your paying customer is not happy with a private incoming call, they should contact police as someone earlier suggested. If deemed necessary, police or court or whatever authority will reach to you for the private caller id. If you just disclose caller id on your customers request as you described, you may just as well disregard rpid / whatever privacy flag you have from pstn all together. But people dont do that afaik. On Sep 9, 2019, at 13:13, Faisal Imtiaz <faisal at snappytelecom.net<mailto:faisal at snappytelecom.net>> wrote: Who is your customer ? The Caller or the Called Entity ? Your obligations are to your paying customer?.. (which in this case is the Called Entity) You have zero obligations to the caller?. If your client is asking for the information, and you have it, you may choose to provide it. What your client does with it, is not your concern. (Law enforcement overrides your agreement of keeping your clients information confidential ) My two cents ! Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net<mailto:Support at Snappytelecom.net> From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> On Behalf Of Matthew Crocker Sent: Monday, September 9, 2019 1:02 PM To: Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>>; voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer You don?t know if it really is harassment. Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data. From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 [Image removed by sender.] _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Thanks? good info. Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net From: Matthew Crocker <matthew at corp.crocker.com> Sent: Monday, September 9, 2019 2:07 PM To: Faisal Imtiaz <faisal at snappytelecom.net>; Victor C <victor.chukalovskiy at gmail.com> Cc: Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer If they are an end-user the SIP INVITE should be sanitized by the providing carrier. Carrier <-> Carrier include CallerID with privacy bits set Carrier -> End-user include Sanitized CallerID (i.e. Anonymous or Private in the From header, no Remote-Party-ID) From: Faisal Imtiaz <faisal at snappytelecom.net<mailto:faisal at snappytelecom.net>> Date: Monday, September 9, 2019 at 2:02 PM To: Victor C <victor.chukalovskiy at gmail.com<mailto:victor.chukalovskiy at gmail.com>> Cc: Matthew Crocker <matthew at corp.crocker.com<mailto:matthew at corp.crocker.com>>, Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>>, "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Subject: RE: [VoiceOps] Disclosing Restricted Caller ID to customer Cool, Looks like it is similar laws here in the USA too.. I stand corrected? https://www.federalregister.gov/documents/2017/12/01/2017-25917/calling-numb... Though I am curious about a scenario? Client is running his own pbx, and running Homer .. Would the Caller ID be visible to them in the homer trace ? Regards Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net<mailto:Support at Snappytelecom.net> From: Victor C <victor.chukalovskiy at gmail.com<mailto:victor.chukalovskiy at gmail.com>> Sent: Monday, September 9, 2019 1:23 PM To: Faisal Imtiaz <faisal at snappytelecom.net<mailto:faisal at snappytelecom.net>> Cc: Matthew Crocker <matthew at corp.crocker.com<mailto:matthew at corp.crocker.com>>; Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>>; voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer Can?t speak for US, but at least in Canada what you described wont fly. You have obligations as a carrier to honour restricted caller id received from PSTN if the caller choose to withhold it. If your paying customer is not happy with a private incoming call, they should contact police as someone earlier suggested. If deemed necessary, police or court or whatever authority will reach to you for the private caller id. If you just disclose caller id on your customers request as you described, you may just as well disregard rpid / whatever privacy flag you have from pstn all together. But people dont do that afaik. On Sep 9, 2019, at 13:13, Faisal Imtiaz <faisal at snappytelecom.net<mailto:faisal at snappytelecom.net>> wrote: Who is your customer ? The Caller or the Called Entity ? Your obligations are to your paying customer?.. (which in this case is the Called Entity) You have zero obligations to the caller?. If your client is asking for the information, and you have it, you may choose to provide it. What your client does with it, is not your concern. (Law enforcement overrides your agreement of keeping your clients information confidential ) My two cents ! Faisal Imtiaz Snappy Internet & Telecom http://www.snappytelecom.net Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net<mailto:Support at Snappytelecom.net> From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> On Behalf Of Matthew Crocker Sent: Monday, September 9, 2019 1:02 PM To: Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>>; voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] Disclosing Restricted Caller ID to customer You don?t know if it really is harassment. Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data. From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Nick Olsen <nick at floridavirtualsolutions.com<mailto:nick at floridavirtualsolutions.com>> Date: Monday, September 9, 2019 at 12:50 PM To: "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Subject: [VoiceOps] Disclosing Restricted Caller ID to customer Greetings all, Had an interesting case come up today that I wanted some feedback on. Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM. Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full. Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement) Nick Olsen Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 [Image removed by sender.] _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
With us specifically. We're Asterisk based. Asterisk doesn't pass the RPID field to the B-LEG of the call. So it's not passed to my customer. The better question becomes where is that line drawn? I'm just buying it wholesale from the usual suspects. It seems like that data shouldn't be passed to wholesale customers (Like me). *Nick Olsen* Network Engineer Office: 321-408-5000 x103 Mobile: 321-794-0763 On Mon, Sep 9, 2019 at 2:02 PM Faisal Imtiaz <faisal at snappytelecom.net> wrote:
Cool,
Looks like it is similar laws here in the USA too..
I stand corrected?
https://www.federalregister.gov/documents/2017/12/01/2017-25917/calling-numb...
Though I am curious about a scenario?
Client is running his own pbx, and running Homer ..
Would the Caller ID be visible to them in the homer trace ?
Regards
Faisal Imtiaz
Snappy Internet & Telecom
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net
*From:* Victor C <victor.chukalovskiy at gmail.com> *Sent:* Monday, September 9, 2019 1:23 PM *To:* Faisal Imtiaz <faisal at snappytelecom.net> *Cc:* Matthew Crocker <matthew at corp.crocker.com>; Nick Olsen < nick at floridavirtualsolutions.com>; voiceops at voiceops.org *Subject:* Re: [VoiceOps] Disclosing Restricted Caller ID to customer
Can?t speak for US, but at least in Canada what you described wont fly.
You have obligations as a carrier to honour restricted caller id received from PSTN if the caller choose to withhold it. If your paying customer is not happy with a private incoming call, they should contact police as someone earlier suggested. If deemed necessary, police or court or whatever authority will reach to you for the private caller id.
If you just disclose caller id on your customers request as you described, you may just as well disregard rpid / whatever privacy flag you have from pstn all together. But people dont do that afaik.
On Sep 9, 2019, at 13:13, Faisal Imtiaz <faisal at snappytelecom.net> wrote:
Who is your customer ? The Caller or the Called Entity ?
Your obligations are to your paying customer?.. (which in this case is the Called Entity)
You have zero obligations to the caller?.
If your client is asking for the information, and you have it, you may choose to provide it.
What your client does with it, is not your concern.
(Law enforcement overrides your agreement of keeping your clients information confidential )
My two cents !
Faisal Imtiaz
Snappy Internet & Telecom
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: Support at Snappytelecom.net
*From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Matthew Crocker *Sent:* Monday, September 9, 2019 1:02 PM *To:* Nick Olsen <nick at floridavirtualsolutions.com>; voiceops at voiceops.org *Subject:* Re: [VoiceOps] Disclosing Restricted Caller ID to customer
You don?t know if it really is harassment.
Tell the customer you have the call details and will retain the data for 90 days. Have them call the police and open a case for harassment. The police can get a subpoena and request the call data.
*From: *VoiceOps <voiceops-bounces at voiceops.org> on behalf of Nick Olsen < nick at floridavirtualsolutions.com> *Date: *Monday, September 9, 2019 at 12:50 PM *To: *"voiceops at voiceops.org" <voiceops at voiceops.org> *Subject: *[VoiceOps] Disclosing Restricted Caller ID to customer
Greetings all, Had an interesting case come up today that I wanted some feedback on.
Customer called claiming they had been receiving harassing calls to their business number, But the calls were caller ID blocked (Caller likely dialed *67 before the call). I found the CDR's for the call in question, And sure enough "Anonymous" <Restricted> was the displayed Calling number and CNAM.
Out of curiosity, I went and pulled the capture of the same call from Homer. And sure enough, The actual calling number is delivered in the Remote-Party-ID field, With Privacy=full.
Obviously, The caller asked for... and expected that data to be private. What's everyones thoughts on the legality of disclosing that information to my customer receiving the call? Would you provide it on request to the end user? Or limit that information only if requested by legal request? (Court order or request from law enforcement)
*Nick Olsen*
Network Engineer
Office: 321-408-5000 x103
Mobile: 321-794-0763
[image: Image removed by sender.]
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (4)
-
faisal＠snappytelecom.net -
matthew＠corp.crocker.com -
nick＠floridavirtualsolutions.com -
victor.chukalovskiy＠gmail.com