Seeding is important, more important then most people think. If you are running a gateway and people can't call a phone behind the gateway because Asterisk has done a reboot, then the call from the pay phone cannot get in because the phone address is not know.
While the 30-45 second or 5 minute delay until the register may seem picky so some it is to long for others. Business can not be halted while we are waiting for the SIP phone to register. A customer does not want to call in and then be told the phone is not available, make you look bad to the customer. Don't think of the normal 9-5 office stuff, think of a server doing continuous calls all day long. Think 3rd World Bodega. I use a "Zombie" list; every time a phone registers I note its address. When asterisk reboots it checks the "Zombie" file and tells each phone in the list to "re-register" (a cool SIP command) immediately. This way there is no waiting for the phone time out to expire. The Zombie list is great for development as we, or at least I, tend to fix, boot, break, fix, boot, break... hundreds of times a day. If I had to wait on the phone to call in then nothing would get done. If I have the phone self-registration set low, the messages make extra debug traffic to wade through. Too high and I am sitting idle till it calls in. Race Vanderdecken Merry Christmas -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg - Cirelle Enterprises Sent: 22 December 2004 11:30 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] sip seeding vs registration At 12:43 AM 12/22/04, you wrote: >Seeding occurs if there is still a persistent record (in astdb) of a preceding >location registration of a peer after a restart of asterisk or the sip >channel. > >If Asterisk goes down and the peer has a long registration refresh time, >the phone maybe inaccessible for a while (until its own refresh timer expires) >if there is no record of its IP address after the restart. >The persistent record and seeding (of the IP address) solves this. > > so this might be the problem with the registration failures? Registration from '<sip:[EMAIL PROTECTED]>' failed for '192.168.70.26' Asterisk registration timeout is shorter than the phone registration timeout??? I'm not sure my statement makes any kind of sense, if it does, than there is a serious issue with the asterisk device communication system. Regards Greg ___________________________________ _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users