I agree w Lelio


—
Sent from Mailbox

On Thu, Oct 30, 2014 at 1:46 PM, Lelio Fulgenzi <[email protected]> wrote:

> I think shared lines are gonna cause you more grief. Especially if they're 
> centrally located, in quadrants so to speak. Guessing out loud, an emergency 
> is probably going to affect multiple people, in the same area, think fire. If 
> it's a shared line in a quadrant, all those people are going to want to dial 
> 911. Outbound calling with shared lines is not the best. 
> I think you should consider creating a separate partition, and using those 
> for your logged out extensions. They're not dialable by anything but the 
> system processes that needs to dial them. Because it's a system process 
> dialing them, they don't have to even be the same length, since interdigit 
> dialing does not come into play. Actually a different length would be better 
> so you don't have duplicates. 
> If you really must be able to dial them from other phones, than you can use 
> dialing codes, say *99-123 will reach logged out extension 123. 
> Just some thoughts. 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst, Network Infrastructure 
> Computing and Communications Services (CCS) 
> University of Guelph 
> 519‐824‐4120 Ext 56354 
> [email protected] 
> www.uoguelph.ca/ccs 
> Room 037, Animal Science and Nutrition Building 
> Guelph, Ontario, N1G 2W1 
> ----- Original Message -----
> From: "Scott Voll" <[email protected]> 
> To: "Ryan Ratliff (rratliff)" <[email protected]> 
> Cc: "cisco-voip voyp list" <[email protected]> 
> Sent: Thursday, October 30, 2014 11:20:04 AM 
> Subject: Re: [cisco-voip] Remove lines on phones with BAT 
> how about a shared line per floor? 
> Scott 
> On Thu, Oct 30, 2014 at 8:09 AM, Ryan Ratliff (rratliff) < [email protected] 
> > wrote: 
> And no, you can't put a shared line on 1300 phones. Use a different DN range 
> or something and let CER handle the translations for you just like it would 
> any other phone. 
> -Ryan 
> On Oct 30, 2014, at 11:03 AM, Erick Wellnitz < [email protected] > 
> wrote: 
> Use a partition that isn't accessible by anything except CER CTI ports. 
> On Thu, Oct 30, 2014 at 8:22 AM, Scott Voll < [email protected] > wrote: 
> <blockquote>
> OK I get the picture....... 
> So if I'm going to put a line on all phones, can I put a shared line on all 
> 1300 phones? If so, how does CER work? will the PSAP call back the line or 
> does it call back the phone? 
> I have a dialing plan that doesn't allow for much in the way of non DID 
> numbers so have a very limited amount to use. 
> TIA 
> Scott 
> On Wed, Oct 29, 2014 at 2:17 PM, Wes Sisk (wsisk) < [email protected] > wrote: 
> <blockquote>
> Agreed with Ryan, Anthony, and Erick. 
> Give the phones DN’s, even just internal DN’s. It is “burning a DN” in the 
> sense that number is allocated. That number does not have to be a DID. Give 
> the phones/lines a CSS that PLAR’s to a help desk. Or at least allow them to 
> invoke local emergency services - private or public. 
> -Wes 
> On Oct 29, 2014, at 3:13 PM, Erick Wellnitz < [email protected] > 
> wrote: 
> Not having lines on a physical phone can be a career altering decision if 
> someone needs to dial emergency services and they grab the nearest logged out 
> phone. There could also be legal issues but I'm not a lawyer so take that for 
> what you will. 
> On Wed, Oct 29, 2014 at 1:03 PM, Anthony Holloway < 
> [email protected] > wrote: 
> <blockquote>
> That's a "Yes" for my experiences. The logout profile or default state of the 
> phone has a nonDID in most cases, DID in a few cases (with a CSS restriction 
> for Internal and EMS), and the UDP of the user has a DID in most cases, 
> nonDID in a few cases (with typical CSS). 
> On Wed, Oct 29, 2014 at 1:33 PM, Scott Voll < [email protected] > wrote: 
> <blockquote>
> So what are people doing in a Extension Mobility only environment? Burning 
> two DN's? one for the user and one for every phone? 
> scott 
> On Wed, Oct 29, 2014 at 11:11 AM, Ryan Ratliff (rratliff) < 
> [email protected] > wrote: 
> <blockquote>
> Auto-reg will provision lines as well, and I agree with Anthony. 
> I don't think anyone wants to deal with the potential issue of somebody 
> picking up a phone to dial emergency services and not getting dialtone. 
> -Ryan 
> On Oct 29, 2014, at 2:05 PM, Anthony Holloway < 
> [email protected] > wrote: 
> Scott, 
> SIP or SCCP, either way, for emergency reasons you don't want phones laying 
> about, unable to save a life when people depend on the reliability of 911. 
> Here's one option without knowing your environment design or limitations: 
> Setup Auto Registration and then Bulk Delete all the phones. 
> On Tue, Oct 28, 2014 at 1:38 PM, Ryan Ratliff (rratliff) < [email protected] 
> > wrote: 
> <blockquote>
> All phones? SIP phones won't register without a line. 
> -Ryan 
> On Oct 28, 2014, at 1:16 PM, Scott Voll < [email protected] > wrote: 
> is there a way to bulk delete all lines on all phones? 
> we are moving to extension mobility and want to remove all the lines on all 
> the phones 
> Thanks 
> scott 
> CM 8.6.2 
> _______________________________________________ 
> cisco-voip mailing list 
> [email protected] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> _______________________________________________ 
> cisco-voip mailing list 
> [email protected] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> </blockquote>
> </blockquote>
> _______________________________________________ 
> cisco-voip mailing list 
> [email protected] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> </blockquote>
> _______________________________________________ 
> cisco-voip mailing list 
> [email protected] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> </blockquote>
> </blockquote>
> </blockquote>
> _______________________________________________ 
> cisco-voip mailing list 
> [email protected] 
> https://puck.nether.net/mailman/listinfo/cisco-voip 
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to