Re: [Asterisk-Users] sip seeding vs registration
At 07:00 PM 12/22/04, you wrote: What registration failure is that? from the asterisk messages log: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' The only way to tell is a complete SIP trace of what's going on. That may be, but the point is when the registration failure like above occurs, the phone is useless, the calls directed to that phone go to voice mail The registration timeout on the phone and in Asterisk should be the same, unless the server goes down and reboots. The server usually has no way to tell a phone to re-register (no real need to do so) On the next phone registration they will be in sync again. We tried that but still had the registration failures. What has stopped the registration failures is stripping out a bunch of unused (in our case) modules to try to isolate the issue. so far No Registration Failures have been detected. the following is what our current modules.conf file looks like: modules.conf [modules] autoload=yes noload = pbx_gtkconsole.so noload = pbx_gtkconsole.so noload = pbx_kdeconsole.so noload = app_intercom.so noload = chan_modem.so noload = chan_modem_aopen.so noload = chan_modem_bestdata.so noload = chan_modem_i4l.so noload = chan_mgcp.so noload = chan_skinny.so ; require for voicemail load = res_adsi.so load = res_musiconhold.so noload = app_festival.so noload = app_url.so noload = app_image.so noload = app_disa.so noload = app_qcall.so noload = app_adsiprog.so noload = app_ices.so noload = codec_lpc10.so noload = codec_g729.so noload = codec_g726.so noload = codec_alaw.so noload = format_vox.so noload = format_h263.so noload = format_jpeg.so noload = cdr_csv.so noload = cdr_manager.so noload = app_zapras.so noload = app_flash.so noload = app_zapbarge.so noload = app_zapscan.so noload = app_talkdetect.so noload = app_alarmreceiver.so noload = chan_alsa.so noload = chan_oss.so noload = res_config_odbc.so noload = res_odbc.so noload = cdr_odbc.so noload = cdr_pgsql.so noload = app_realtime.so [global] chan_modem.so=no Eventually, we will retry the app_realtime again, but so far that has been a failure. The more pressing issue is the registration failure issue 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
Re: [Asterisk-Users] sip seeding vs registration
Oh, I see. This is the realtime connected problem. Can't say too much constructive about that without info, I'm not a fan of it. We need a debug trace of the registration process (SIP trace and * messages) to debug why it failed, not just a one-line message, and anything after that is useless, as you point out. However, I don't think it has anything do to with loading (or not) all your modules, unless you're running out of memory. Greg - Cirelle Enterprises wrote: At 07:00 PM 12/22/04, you wrote: What registration failure is that? from the asterisk messages log: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' The only way to tell is a complete SIP trace of what's going on. That may be, but the point is when the registration failure like above occurs, the phone is useless, the calls directed to that phone go to voice mail The registration timeout on the phone and in Asterisk should be the same, With this I didn't mean you need to set them to be the same, it just should be the same because asterisk would dictate it's own value if the client's value is out of bounds of configuration, otherwise Asterisk will accept the client's, and so the two will always have the same value automatically. unless the server goes down and reboots. The server usually has no way to tell a phone to re-register (no real need to do so) On the next phone registration they will be in sync again. We tried that but still had the registration failures. What has stopped the registration failures is stripping out a bunch of unused (in our case) modules to try to isolate the issue. so far No Registration Failures have been detected. the following is what our current modules.conf file looks like: modules.conf [modules] autoload=yes noload = pbx_gtkconsole.so noload = pbx_gtkconsole.so noload = pbx_kdeconsole.so noload = app_intercom.so noload = chan_modem.so noload = chan_modem_aopen.so noload = chan_modem_bestdata.so noload = chan_modem_i4l.so noload = chan_mgcp.so noload = chan_skinny.so ; require for voicemail load = res_adsi.so load = res_musiconhold.so noload = app_festival.so noload = app_url.so noload = app_image.so noload = app_disa.so noload = app_qcall.so noload = app_adsiprog.so noload = app_ices.so noload = codec_lpc10.so noload = codec_g729.so noload = codec_g726.so noload = codec_alaw.so noload = format_vox.so noload = format_h263.so noload = format_jpeg.so noload = cdr_csv.so noload = cdr_manager.so noload = app_zapras.so noload = app_flash.so noload = app_zapbarge.so noload = app_zapscan.so noload = app_talkdetect.so noload = app_alarmreceiver.so noload = chan_alsa.so noload = chan_oss.so noload = res_config_odbc.so noload = res_odbc.so noload = cdr_odbc.so noload = cdr_pgsql.so noload = app_realtime.so [global] chan_modem.so=no Eventually, we will retry the app_realtime again, but so far that has been a failure. The more pressing issue is the registration failure issue 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
Re: [Asterisk-Users] sip seeding vs registration
At 03:43 PM 12/23/04, you wrote: Oh, I see. This is the realtime connected problem. Can't say too much constructive about that without info, I'm not a fan of it. We need a debug trace of the registration process (SIP trace and * messages) to debug why it failed, not just a one-line message, and anything after that is useless, as you point out. However, I don't think it has anything do to with loading (or not) all your modules, unless you're running out of memory. The module elimination was to try and rule out memory issues as the machine is limited to 512MB RAM. When utilizing the app_realtime: The CLI interface is consistently issuing these messages. it has been a slow day with no real phone activity. -- SIP Seeding '40853' at [EMAIL PROTECTED]:5060 for 3600 -- Saved useragent Sipura/SPA2000-2.0.10(e) for peer 40853 -- SIP Seeding '40853' at [EMAIL PROTECTED]:5060 for 3600 -- SIP Seeding '40854' at [EMAIL PROTECTED]:5061 for 3600 -- SIP Seeding '40854' at [EMAIL PROTECTED]:5061 for 3600 -- Saved useragent Sipura/SPA2000-2.0.10(e) for peer 40854 -- SIP Seeding '40854' at [EMAIL PROTECTED]:5061 for 3600 -- SIP Seeding '52221' at [EMAIL PROTECTED]:5060 for 3600 -- SIP Seeding '52221' at [EMAIL PROTECTED]:5060 for 3600 Dec 23 16:22:44 NOTICE[12551]: chan_sip.c:7742 handle_request: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' -- SIP Seeding '52221' at [EMAIL PROTECTED]:5060 for 3600 -- Saved useragent Grandstream BT100 1.0.5.20 for peer 52221 -- SIP Seeding '52221' at [EMAIL PROTECTED]:5060 for 3600 -- SIP Seeding '1002' at [EMAIL PROTECTED]:5060 for 1800 -- SIP Seeding '1002' at [EMAIL PROTECTED]:5060 for 1800 -- Saved useragent X-Lite release 1103m for peer 1002 -- SIP Seeding '1002' at [EMAIL PROTECTED]:5060 for 1800 -- SIP Seeding '40852' at [EMAIL PROTECTED]:5060 for 3600 -- SIP Seeding '40852' at [EMAIL PROTECTED]:5060 for 3600 Dec 23 16:48:47 NOTICE[12551]: chan_sip.c:7742 handle_request: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' -- SIP Seeding '40852' at [EMAIL PROTECTED]:5060 for 3600 -- Saved useragent Grandstream BT100 1.0.5.20 for peer 40852 -- SIP Seeding '40852' at [EMAIL PROTECTED]:5060 for 3600 -- SIP Seeding '1002' at [EMAIL PROTECTED]:5060 for 1800 -- SIP Seeding '1002' at [EMAIL PROTECTED]:5060 for 1800 -- Saved useragent X-Lite release 1103m for peer 1002 The /var/log/asterisk/messages file gives Dec 23 12:24:00 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' Dec 23 12:50:05 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' Dec 23 13:23:41 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' Dec 23 14:23:22 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' Dec 23 14:49:26 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' Dec 23 15:23:03 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' Dec 23 16:22:44 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' Dec 23 16:48:47 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.25' Dec 23 17:22:25 NOTICE[12551]: Registration from 'sip:[EMAIL PROTECTED]' failed for '192.168.70.26' D Restoring the system to using *.conf files eliminates all of this output and calls going directly to voicemail Unfortunately, I don't have the exact channel cannot be created or ? messages as there were non today and are usually seen in the CLI. Unless I'm mistaken, these general messages indicate a registration failure, do they not? When a call comes in and goes directly to voicemail while the extension is sitting idle waiting for a call, not busy or off the hook, I think is an issue. g ___ 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
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
RE: [Asterisk-Users] sip seeding vs registration
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
Re: [Asterisk-Users] sip seeding vs registration
What registration failure is that? The only way to tell is a complete SIP trace of what's going on. The registration timeout on the phone and in Asterisk should be the same, unless the server goes down and reboots. The server usually has no way to tell a phone to re-register (no real need to do so) On the next phone registration they will be in sync again. Greg - Cirelle Enterprises wrote: 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
[Asterisk-Users] sip seeding vs registration
does anybody have an idea what the difference and significance of sip seeding and registration is. g Regards Greg Cirino ___ Cirelle Enterprises Inc. 603-425-2221 www.cirelle.com Web Application Development Design www.cirelle.net ProSpeed High Speed Dial-up - 6 Times Faster www.cedata.com Web, FTP, Email Hosting Services www.mlsbot.com NNEREN MLS IDX Services When You Want It Done Well, Just Call Cirelle It's not just a Rhyme... There's a Reason! ___ 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
