[Asterisk-Users] GXP-2000

[list mail]

I'm willing to bet the phones that are stalling have the most active  
computer users attatched to them. I wouldn't advise having the  
computer running through the phones port. To me that is asking too  
much out of the <$100 phone.
Run each device from it's own port on your switch.



On Jun 7, 2006, at 9:36 PM, Daniel Salama wrote:

> They are extremely casual web surfers. Just have their Outlook  
> client opened checking email every minute. Email traffic is very low.
>
> They are all connected to the same switch. It's a Netopia DSL  
> router/modem/switch for the BellSouth DSL service. The computers  
> are connected to the PC port behind the GXP-2000.
>
> Any suggestions?
>
> Thanks,
> Daniel
>
> On Jun 7, 2006, at 8:49 PM, list mail wrote:
>
>> What do they do on the internet? Heavy surfing, large transfers,  
>> myspace.
>> How are these units connected to the network? Are they passing  
>> through the same switch?
>> I don't think it is the phones...
>>
>> On Jun 7, 2006, at 12:32 PM, Daniel Salama wrote:
>>
>>> Mike,
>>>
>>> I added a qualify=500 on those phones. My client has peers 100218  
>>> thru 100222 (a total of 5 phones). Below is the messages log  
>>> since I activated it this morning at 8:30AM:
>>>
>>> Jun  7 10:59:21 NOTICE[3648] chan_sip.c: Peer '100219' is now TOO  
>>> LAGGED! (1075ms / 500ms)
>>> Jun  7 10:59:31 NOTICE[3648] chan_sip.c: Peer '100219' is now  
>>> REACHABLE! (66ms / 500ms)
>>> Jun  7 11:02:32 NOTICE[3648] chan_sip.c: Peer '100219' is now TOO  
>>> LAGGED! (1075ms / 500ms)
>>> Jun  7 11:02:42 NOTICE[3648] chan_sip.c: Peer '100219' is now  
>>> REACHABLE! (68ms / 500ms)
>>> Jun  7 11:35:15 NOTICE[3648] chan_sip.c: Peer '100222' is now TOO  
>>> LAGGED! (1114ms / 500ms)
>>> Jun  7 11:35:25 NOTICE[3648] chan_sip.c: Peer '100222' is now  
>>> REACHABLE! (90ms / 500ms)
>>> Jun  7 11:48:20 NOTICE[3648] chan_sip.c: Peer '100219' is now TOO  
>>> LAGGED! (1077ms / 500ms)
>>> Jun  7 11:48:30 NOTICE[3648] chan_sip.c: Peer '100219' is now  
>>> REACHABLE! (72ms / 500ms)
>>> Jun  7 12:24:51 NOTICE[3648] chan_sip.c: Peer '100221' is now TOO  
>>> LAGGED! (1077ms / 500ms)
>>> Jun  7 12:25:01 NOTICE[3648] chan_sip.c: Peer '100221' is now  
>>> REACHABLE! (73ms / 500ms)
>>>
>>> As you can see, it only happens to a couple of their phones and  
>>> at random times. They're behind a DSL circuit. I don't know if  
>>> it's because their DSL line is going up/down. They don't  
>>> necessarily claim their Internet goes down, however, they are not  
>>> constantly check it.
>>>
>>> What would you (or anyone else) suggest?
>>>
>>> Thanks,
>>> Daniel
>>>
>>> On Jun 7, 2006, at 8:07 AM, Mike Fedyk wrote:
>>>
>>>> Do you have multiple phones going down at the same time?  If so,  
>>>> monitor them with "qualify=500" in sip.conf to see if they hit  
>>>> that limit.  If you see more than one go down within a short  
>>>> period of time, you have network problems.  Check the quality of  
>>>> the network switches they have.
>>>
>>> _______________________________________________
>>> --Bandwidth and Colocation provided by Easynews.com --
>>>
>>> Asterisk-Users mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> Asterisk-Users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060608/7dc42e2d/attachment.htm