Greg - Cirelle Enterprises
2004-Dec-17 06:25 UTC
[Asterisk-Users] erroneous errors - registration fails for grandstream phones
Has anybody seen this behaviour? sip conf is stored in mysql database in 2 tables ast_config for static (general) key/values sip_buddies for sip extension detail. database on the same machine as asterisk Grandstream phones (I happen to have 2) register with asterisk via sip with accounts and passwords successfully for a variable period of time. Then after a while, i get errors which appear to be erroneous since the phones/extensions apparently are working. example of 1 phone, but it happens with both: *** from asterisk CLI> -- SIP Seeding '40852' at 40852@192.168.20.25:5060 for 2400 Dec 17 08:01:59 NOTICE[22259]: chan_sip.c:7742 handle_request: Registration from '<sip:40852@192.168.20.2>' failed for '192.168.20.25' -- Saved useragent "Grandstream BT100 1.0.5.20" for peer 40852 -- SIP Seeding '40852' at 40852@192.168.20.25:5060 for 2400 The date obviously changes *** from /var/log/asterisk/messages Dec 17 08:01:59 NOTICE[22259]: Registration from '<sip:40852@192.168.20.2>' failed for '192.168.20.25' The phones appear to work no traffic on the server 3Ghz P4 512MB RAM 75GB Free Disk Space Regards Greg Cirino
Diego Aguirre
2004-Dec-17 07:38 UTC
[Asterisk-Users] erroneous errors - registration fails forgrandstream phones
Hi, Look in your sip.conf host=192.168.20.2 and your phone is set to use 192.168.20.25 try to change host directive in sip.conf to host=192.168.20.25 ---- Diego Aguirre ----- Original Message ----- From: "Greg - Cirelle Enterprises" <gcirino@cirelle.com> To: <asterisk-users@lists.digium.com> Sent: Friday, December 17, 2004 11:25 AM Subject: [Asterisk-Users] erroneous errors - registration fails forgrandstream phones> Has anybody seen this behaviour? > > sip conf is stored in mysql database in 2 tables > ast_config for static (general) key/values > > sip_buddies for sip extension detail. > > database on the same machine as asterisk > > > Grandstream phones (I happen to have 2) register with asterisk > via sip with accounts and passwords successfully for a variable > period of time. Then after a while, i get errors which appear to > be erroneous since the phones/extensions apparently are working. > > example of 1 phone, but it happens with both: > > *** from asterisk CLI> > -- SIP Seeding '40852' at 40852@192.168.20.25:5060 for 2400 > Dec 17 08:01:59 NOTICE[22259]: chan_sip.c:7742 handle_request: > Registration from '<sip:40852@192.168.20.2>' failed for '192.168.20.25' > -- Saved useragent "Grandstream BT100 1.0.5.20" for peer 40852 > -- SIP Seeding '40852' at 40852@192.168.20.25:5060 for 2400 > > The date obviously changes > > > *** from /var/log/asterisk/messages > Dec 17 08:01:59 NOTICE[22259]: Registration from > '<sip:40852@192.168.20.2>' failed for '192.168.20.25' > > > The phones appear to work > no traffic on the server 3Ghz P4 512MB RAM 75GB Free Disk Space > > > > > Regards > Greg Cirino > > _______________________________________________ > 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 > >
Greg - Cirelle Enterprises
2004-Dec-18 09:48 UTC
[Asterisk-Users] erroneous errors - registration fails for grandstream phones
At 09:38 AM 12/17/04, you wrote:>Hi, > >Look in your sip.conf > >host=192.168.20.2 > >and your phone is set to use 192.168.20.25 > >try to change host directive in sip.conf to > >host=192.168.20.25 > >---- >Diego AguirreHost is set to dynamic host=dynamic type=friend I think this is an issue in the way chan_sip handles things with the grandstream phones. this does not occur with the sipura 2k units or xten softphones on the same network. I have set the dtmfmode to info (instead of inband) to see if there is a difference. This might also be specific to the way "realtime" handles this. I have not seen this occur with the sip.conf file (no database). Then again, I may not have noticed it happening. it appears to be an inconsistent bug in the the way registration is handled with the GS phones. This settles down with a restart of asterisk, but just happens again later. Operation doesn't seem to be affected, but I can't swear to that either. Greg