Hello Nabeel: I was afraid someone would suggest that. But the number of sip registers we have, and to change the SIP timings for "qualify" is not practical for the number of registrations we have. We do not have any satellite registrations, but we do have overseas registrations. I suspected it might have been some of the overseas clients, but their connection is stable and rock solid.
Which leaves me to think that the 200 OK on Register is being generated by a North American account/client, but unfortunately its not practical on our part to change the "qualify" seconds. I'm still looking for some sort of answer/recommendation on how we can pin point the source... sort of take a magnet in a hay stack, swipe it over and get the needle... versus trying to find the needle in the hay stack, moving one hay at a time. Any suggestions? Cheers! Reza. ----- Original Message ----- From: "Nabeel Jafferali" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, September 21, 2007 6:57 AM Subject: RE: [on-asterisk] Locating the source of "200 OK on REGISTER" Usually to do with a significant delay, when the endpoint receives the Asterisk reply very late compared to the REGISTER message it sent. My experience was this was happening with endpoints with satellite Internet connectivity. Increase the SIP timings (I just quadrupled them from their default) and the problem should go away, since the device will have a higher tolerance for delay. Nabeel > -----Original Message----- > From: Reza - Asterisk Enthusiast [mailto:[EMAIL PROTECTED] > Sent: September 21, 2007 12:46 AM > To: [email protected] > Subject: [on-asterisk] Locating the source of "200 OK on REGISTER" > > Hello all: > > The "Got 200 OK on REGISTER that isn't a register" is annoying the day > lights out of me. I know what it means... but do not know how to > PIN > POINT the source. Any suggestions? > > Best, > Reza. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
