<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body bgcolor="#FFFFFF">
<div>Yeah, but you're talking about inbound.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Does that help clarify my viewpoint?</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Joshua <br>
<br>
Sent from my iPhone</div>
<div><br>
On Jan 18, 2013, at 11:29 AM, "Carlos Alvarez" <<a href="mailto:carlos@televolve.com">carlos@televolve.com</a>> wrote:<br>
<br>
</div>
<div></div>
<blockquote type="cite">
<div>On Fri, Jan 18, 2013 at 12:16 PM, Joshua Goldbard <span dir="ltr"><<a href="mailto:j@2600hz.com" target="_blank">j@2600hz.com</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF">
<div>We run our e911 through a service as well but price per location as opposed to per phone. We've also found that, if possible, binding the e911 to a did is preferable to device binding.</div>
</div>
</blockquote>
<div><br>
</div>
<div>We price per location also. The extension binding versus device binding is confusing to me; don't you give a customer the same DID to ring all of their devices? That's what we do, so the home phone and office ring concurrently.</div>
<div> </div>
</div>
-- <br>
<div>Carlos Alvarez</div>
<div>TelEvolve</div>
<div>602-889-3003</div>
<div><br>
</div>
</div>
</blockquote>
</body>
</html>