Re: [VoiceOps] VoiceOps Digest, Vol 121, Issue 4

[Jason Kuylen]

We have a form that the customer takes to the Sheriff's Office that basically 
says " I 'customer' do hereby request that Telco identify the source of calls 
that happened at date/time. I authorize and agree not to hold telco to any 
claims, demands, other legalese, etc." The customer signs it and has the 
sheriff or deputy sign and are given a reference number. We then call or fax 
the information to the Sheriff after the customer brings us back the form and 
performs a Caller Originated Trace.

We absolutely under no circumstances give information directly to the customer.

-Original Message-
From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of 
voiceops-requ...@voiceops.org
Sent: Monday, September 9, 2019 1:13 PM
To: voiceops@voiceops.org
Subject: VoiceOps Digest, Vol 121, Issue 4

Send VoiceOps mailing list submissions to
voiceops@voiceops.org

To subscribe or unsubscribe via the World Wide Web, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_voiceops=DwICAg=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=UsggrYHjFUWXi3kKPTjVkMUoseBpwHsFa0CMhvYkPUo=eiHWslAflAXZq56a6xrfbzZyNgcbtDRYsq_pEVQR9HE=FeO3hxrT4NO3W4Hi8DwgyMIOd6RoSJSmio8MoUdzjRk=
or, via email, send a message with subject or body 'help' to
voiceops-requ...@voiceops.org

You can reach the person managing the list at
voiceops-ow...@voiceops.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of VoiceOps digest..."

Important/Confidential: This communication and any files or documents attached 
to it are intended only for the use of the person(s) or entity to which it is 
addressed. It contains information that may be confidential and exempt from 
disclosure under applicable law. If you are not the intended recipient of this 
communication, you are hereby notified that the copying, disclosure, 
distribution, storage, retransmission or other use of this communication is 
strictly prohibited. If you have received this communication by mistake, please 
notify the sender immediately and destroy all forms of this communication 
(electronic or paper).
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Nick Olsen]

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 
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-number-identification-service-caller-id
>
>
>
> 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: supp...@snappytelecom.net
>
>
>
> *From:* Victor C 
> *Sent:* Monday, September 9, 2019 1:23 PM
> *To:* Faisal Imtiaz 
> *Cc:* Matthew Crocker ; Nick Olsen <
> n...@floridavirtualsolutions.com>; voiceops@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  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: supp...@snappytelecom.net
>
>
>
> *From:* VoiceOps  *On Behalf Of *Matthew
> Crocker
> *Sent:* Monday, September 9, 2019 1:02 PM
> *To:* Nick Olsen ; voiceops@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  on behalf of Nick Olsen <
> n...@floridavirtualsolutions.com>
> *Date: *Monday, September 9, 2019 at 12:50 PM
> *To: *"voiceops@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"  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@voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Faisal Imtiaz]

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: supp...@snappytelecom.net

From: Matthew Crocker 
Sent: Monday, September 9, 2019 2:07 PM
To: Faisal Imtiaz ; Victor C 

Cc: Nick Olsen ; voiceops@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 mailto:fai...@snappytelecom.net>>
Date: Monday, September 9, 2019 at 2:02 PM
To: Victor C 
mailto:victor.chukalovs...@gmail.com>>
Cc: Matthew Crocker 
mailto:matt...@corp.crocker.com>>, Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>, 
"voiceops@voiceops.org" 
mailto:voiceops@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-number-identification-service-caller-id

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: 
supp...@snappytelecom.net

From: Victor C 
mailto:victor.chukalovs...@gmail.com>>
Sent: Monday, September 9, 2019 1:23 PM
To: Faisal Imtiaz mailto:fai...@snappytelecom.net>>
Cc: Matthew Crocker 
mailto:matt...@corp.crocker.com>>; Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>; 
voiceops@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 
mailto:fai...@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: 
supp...@snappytelecom.net

From: VoiceOps 
mailto:voiceops-boun...@voiceops.org>> On Behalf 
Of Matthew Crocker
Sent: Monday, September 9, 2019 1:02 PM
To: Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>; 
voiceops@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 
mailto:voiceops-boun...@voiceops.org>> on behalf 
of Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>
Date: Monday, September 9, 2019 at 12:50 PM
To: "voiceops@voiceops.org" 
mailto:voiceops@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"  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 

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Matthew Crocker]

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 
Date: Monday, September 9, 2019 at 2:02 PM
To: Victor C 
Cc: Matthew Crocker , Nick Olsen 
, "voiceops@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-number-identification-service-caller-id

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: supp...@snappytelecom.net

From: Victor C 
Sent: Monday, September 9, 2019 1:23 PM
To: Faisal Imtiaz 
Cc: Matthew Crocker ; Nick Olsen 
; voiceops@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 
mailto:fai...@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: 
supp...@snappytelecom.net

From: VoiceOps 
mailto:voiceops-boun...@voiceops.org>> On Behalf 
Of Matthew Crocker
Sent: Monday, September 9, 2019 1:02 PM
To: Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>; 
voiceops@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 
mailto:voiceops-boun...@voiceops.org>> on behalf 
of Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>
Date: Monday, September 9, 2019 at 12:50 PM
To: "voiceops@voiceops.org" 
mailto:voiceops@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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Faisal Imtiaz]

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-number-identification-service-caller-id

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: supp...@snappytelecom.net

From: Victor C 
Sent: Monday, September 9, 2019 1:23 PM
To: Faisal Imtiaz 
Cc: Matthew Crocker ; Nick Olsen 
; voiceops@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 
mailto:fai...@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: 
supp...@snappytelecom.net

From: VoiceOps 
mailto:voiceops-boun...@voiceops.org>> On Behalf 
Of Matthew Crocker
Sent: Monday, September 9, 2019 1:02 PM
To: Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>; 
voiceops@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 
mailto:voiceops-boun...@voiceops.org>> on behalf 
of Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>
Date: Monday, September 9, 2019 at 12:50 PM
To: "voiceops@voiceops.org" 
mailto:voiceops@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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Victor C]

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  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: supp...@snappytelecom.net
>  
> From: VoiceOps  On Behalf Of Matthew Crocker
> Sent: Monday, September 9, 2019 1:02 PM
> To: Nick Olsen ; voiceops@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  on behalf of Nick Olsen 
> 
> Date: Monday, September 9, 2019 at 12:50 PM
> To: "voiceops@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"  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@voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Nick Olsen]

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 
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: supp...@snappytelecom.net
>
>
>
> *From:* VoiceOps  *On Behalf Of *Matthew
> Crocker
> *Sent:* Monday, September 9, 2019 1:02 PM
> *To:* Nick Olsen ; voiceops@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  on behalf of Nick Olsen <
> n...@floridavirtualsolutions.com>
> *Date: *Monday, September 9, 2019 at 12:50 PM
> *To: *"voiceops@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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Faisal Imtiaz]

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: supp...@snappytelecom.net

From: VoiceOps  On Behalf Of Matthew Crocker
Sent: Monday, September 9, 2019 1:02 PM
To: Nick Olsen ; voiceops@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 
mailto:voiceops-boun...@voiceops.org>> on behalf 
of Nick Olsen 
mailto:n...@floridavirtualsolutions.com>>
Date: Monday, September 9, 2019 at 12:50 PM
To: "voiceops@voiceops.org" 
mailto:voiceops@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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disclosing Restricted Caller ID to customer

[Matthew Crocker]

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  on behalf of Nick Olsen 

Date: Monday, September 9, 2019 at 12:50 PM
To: "voiceops@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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

[VoiceOps] Disclosing Restricted Caller ID to customer

[Nick Olsen]

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"  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@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops