<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Nathan,
<div><br>
</div>
<div>CLID as it applies to the PSTN is inherently outbound. That being said, a number of switches (PBXs) have the capability of modifying the caller ID of a user. You see this with internal Caller IDs and external caller ID (extension versus CNAM). Some providers
(2600hz included) have introduced a third caller ID classification: emergency.</div>
<div><br>
</div>
<div>Let me give you a practical example.</div>
<div><br>
</div>
<div>My Internal Caller ID is: 7923 (THE MARKETING GUY)</div>
<div>My external Caller ID is: 415.886.7923 2600hz</div>
<div>My emergency Caller ID is: 415.886.7900 2600hz ($Address)</div>
<div><br>
</div>
<div>The purpose here is to take our block of 100 DIDs and only support emergency services in a single uniform fashion. We can override this on a user by user or per-device basis, but the point is to simplify emergency calling.</div>
<div><br>
</div>
<div>Does that help clarify what we're doing?</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Joshua</div>
<div><br>
</div>
<div>P.S. I previously sent this email only to Nathan. Adding voiceops onto the chain just in case there's interest.</div>
<div><br>
</div>
<div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Joshua Goldbard</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
VP of Marketing, 2600hz</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
116 Natoma Street, Floor 2</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
San Francisco, CA, 94104</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
415.886.7923 | <a href="mailto:j@2600hz.com">j@2600hz.com</a></div>
<br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<span></span> </div>
<br>
<div>
<div>On Jan 18, 2013, at 1:04 PM, Nathan Anderson <<a href="mailto:nathana@fsr.com">nathana@fsr.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">I'm confused, and I apologize to those who have already been involved in this discussion thread for a while since I am just now jumping in. CLID is inherently outbound, so I am not sure what you mean by "inbound vs. outbound caller
IDs". Perhaps by "inbound CLID" you mean DID, or DNIS?<br>
<br>
I'm also not sure how you propose to bind E911 details to a device instead of a telephone number. The few E911 services I've looked at all only give you the option to provision E911 information via TN. So if you propose a set-up such as what is being discussed
here, where each company phone only has an internal extension # and no DID, and CLID is uniformly set to a single number for all outbound calls from any phone whether it is located in the office building or at an employee's residence, then there can only be
a single E911 address for all of those phones. That seems inescapable. Are you saying that there are E911 companies that can provision differently, and not use the CLID as the "key" to looking up an address? What do they use/how do they work, and can you
name some names?<br>
<br>
The only other kludgey workaround I can think of that might pass muster would be to assign unique "throwaway" TNs to each individual extension that you would use as the CLID for outbound from that extension *only* when 911 is dialed, and continue to use the
global office TN as CLID across all extensions for all other outbound calls. It's not a perfect solution, since if the individuals using those phones have no clue about those numbers, they might get confused when asked to verify their own telephone number
by the PSAP and the dispatcher reads some number back to them that isn't their main office number. At that point, you might as well let the customer know that these numbers exist and give them the option of using them as DIDs for the extensions/devices they've
been assigned to.<br>
<br>
--<br>
Nathan Anderson<br>
First Step Internet, LLC<br>
<a href="mailto:nathana@fsr.com">nathana@fsr.com</a><br>
<br>
-----Original Message-----<br>
From: voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org] On Behalf Of Carlos Alvarez<br>
Sent: Friday, January 18, 2013 11:49 AM<br>
To: Joshua Goldbard<br>
Cc: voiceops@voiceops.org<br>
Subject: Re: [VoiceOps] 911 address policy for company phones at home<br>
<br>
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j@2600hz.com> wrote:<br>
<br>
<br>
<span class="Apple-tab-span" style="white-space:pre"></span>Yeah, but you're talking about inbound.<br>
<br>
<span class="Apple-tab-span" style="white-space:pre"></span>In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the
inbound and outbound caller IDs can certainly be different.<br>
<br>
<span class="Apple-tab-span" style="white-space:pre"></span>Does that help clarify my viewpoint?<br>
<br>
<br>
Ah, yes. We very rarely get anyone who wants to do that, so it didn't cross my mind.<br>
<br>
We do have special 911 CLID/DID settings and special processing for those calls. However we bind them to a device, since the device is what has location, in most of our installations.<br>
<br>
<br>
-- <br>
<br>
Carlos Alvarez<br>
TelEvolve<br>
602-889-3003<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
https://puck.nether.net/mailman/listinfo/voiceops<br>
</blockquote>
</div>
<br>
</body>
</html>