Yes, the 2801 at each location is for SRST and 911 issues.<br>All IP phones have the same default gateway. It might be the 2801 or a 3560, I will have to confirm tomorrow when I am back at the office. I think the 2801 is doing DHCP server duties, something I need to get off of it.<br>
<br><div class="gmail_quote">On Sun, Jul 13, 2008 at 11:20 AM, Steve G <<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>This may be an obvious question, but why is there a 2801 at each location? is it for SRST/911 purposes? Do all IP Phones have the same default gateway, or do they look to their respective 2801s to provide routing for them?</div>
<div> </div><font color="#888888">
<div>Steve<br><br></div></font><div><div></div><div class="Wj3C7c">
<div class="gmail_quote">On Sun, Jul 13, 2008 at 8:07 AM, Todd Franklin <<a href="mailto:toddnh65@gmail.com" target="_blank">toddnh65@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Interesting thought. The 2801 did have some sort of notice about a duplicate DHCP entry or some such thing....unfortunately, everything was happening so fast, and there is that need to JUST FIX IT,that there isn't a lot of time to write stuff down or gather relevant stats. <br>
<br>Looks like I will be doing further research!!<br><br>Todd<br><br>I think it might be time to set up my cisco gear so it logs relevant happenings to a syslogger on one of my linux/doze boxes.
<div>
<div></div>
<div><br><br>
<div class="gmail_quote">On Sun, Jul 13, 2008 at 12:50 AM, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One-way audio is almost always a routing issue, my guess is that you<br>have a duplicate route to a subnet or a duplicate IP taking over a key<br>
layer-3 routed interface.<br><br><br><br>Jonathan<br>
<div>
<div></div>
<div><br>On Sat, Jul 12, 2008 at 7:42 AM, Todd Franklin <<a href="mailto:toddnh65@gmail.com" target="_blank">toddnh65@gmail.com</a>> wrote:<br>> Environment:<br>><br>> CCM 4.1, Unity version 4 also.<br>> 3560s, 2801s. 6 buildings all linked by fiber. Each building has a 2801<br>
> and 3560.<br>> Total phone count: 60, mostly 7940s, some 7912s, a few 7960s.<br>><br>> All fiber runs back to main location where it joins the network through<br>> GBICs on 3560s.<br>> At the main location we have a PRI that goes into a 2801.<br>
><br>> Problem: 3 times in the last year, we will get a situation that goes like<br>> this:<br>> Pressing 9 to dial out, and dialing your number: Phone shows call is<br>> completed, starts counting the seconds, but you hear nothing.<br>
> If we call another extension internally, they will hear us but we cannot<br>> hear them.<br>> If someone calls in from outside and gets the auto attendant, no input is<br>> accepted, the attendant just keeps going. (i.e. Press 2 for this, she just<br>
> keeps going, you can press as many buttons as you like, no change).<br>><br>> The solution seems to be to reboot the main 2801 with the PRI. I am not<br>> sure why this would cure internal extension-to-extension calls, but it<br>
> does. My facility runs 24 hours a day, so a reboot is never a good thing.<br>><br>> Where should I start looking? Broadcast storms? Is this a sort of known<br>> bug that Cisco might have fixed somewhere? Anything in Unity or CCM I<br>
> should look at? Counters on ports?<br>><br>> Would appreciate any direction at all!<br>><br>> Todd<br>><br></div></div>> _______________________________________________<br>> cisco-voip mailing list<br>
<div>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br></div>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br></blockquote></div><br></div></div><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>
</div></div></blockquote></div><br>