One thing to keep in mind is that the Grandstream's firmware is notoriously buggy and unreliable. I've got one GXP2000 here that is on the 1.1.5.15 firmware, and I wouldn't even consider upgrading other phones to them. Unfortunately, the quality of the Grandstream firmware is appalling and doesn't seem to be getting any better - if anything, the stability is getting /worse/.
My advise for what it's worth is to use the Grandstream phones to their best purpose - as a doorstop (albeit for a fairly light door) Peder @ NetworkOblivion wrote: > I hate to reply to my own message, but I have some more info from > debugging. A Grandstream tries to register and uses a nonce and it is > accepted by *. The next time it tries to register, it uses the same > none and * says "SIP/2.0 401 Unauthorized". The Grandtream says "ok, > here try this new nonce" and then it works again. Again, the next time > it registers, it tries the old one and gets slapped again and gives a > new one. After some indeterminate amount of time, the Grandstream > actually tries to use the same nonce 3 times in a row. Once it works, > the next time it gets a "SIP/2.0 401 Unauthorized" and then the third > time, it gets a "SIP/2.0 403 Forbidden". This evidently causes the > Grandstream to completely give up registration as once * sends this, the > Grandstream nevers tries to register again. I've waited for 1-2 hours > and it never tries again. The "Forbidden" response appears to kill > registration until the Grandstream is rebooted. Has anybody else seen > this? Or maybe know how to get around it? > > > > Peder @ NetworkOblivion wrote: > >> I did post most of that. Point to point T1, no firewalls and no nat, >> cisco routers, bandwidth is monitored at 30 second intervals and never >> exceeds 50%, almost always 25% or less. The key is that I get messages >> from * like "failed to register" and it is from the IP of the phone, so >> it is like the phone is sending some messed up message. Asterisk is >> old, 1.0.3, but it has been stable for 2-3 years with zero issues. >> While it could be a asterisk version issue, I have 100-150 phones on it, >> mostly Cisco 7940/7960 and none of them have these issues. The only >> phones with issues appear to be Grandstream and they are all running >> 1.1.5.15. Here is a sample sip config: >> >> [7834-1] >> context=HASKI-LD >> type=friend >> callerid="HASKI" <7834> >> username=7834-1 >> secret=47834-1 >> host=dynamic >> [EMAIL PROTECTED] >> canreinvite=no >> qualify=yes >> >> Here is one of the log messages: >> >> Feb 11 18:18:05 NOTICE[20905]: Registration from >> '<sip:[EMAIL PROTECTED]>' failed for '192.168.2.165' >> >> That message is from a phone that is set to register every 5 minutes. >> It's been 50 minutes and it still hasn't re-registered. If I reboot the >> phone, it will register right away... >> >> Any ideas? >> >> >> Peder >> >> >> Andrew Joakimsen wrote: >> >>> Yes but network issues are still possible. What sort of network >>> connections are you using? What sort of routers/firewalls/other >>> network gear? Are you certain of the reliability of the T1? Also you >>> did not post what Asterisk version is in use. Please also post the >>> relevant sip.conf and configuration file of the phone. >>> >>> >>> On Feb 11, 2008 4:52 PM, Peder @ NetworkOblivion >>> <[EMAIL PROTECTED]> wrote: >>> >>>> I have 20-30 GXP2000's connected to * over a T1 line. Neither end is >>>> NAT'd and there is plenty of bandwidth available over the line. The >>>> GXP's are 1.1.5.15, which is the latest. I have a problem where the >>>> phones keep dropping off of * and I get a "failed to register" message >>>> in the log of *. Sometimes they eventually connect and sometimes, I >>>> have to reboot them to get them to reconnect (I never change the config >>>> though). Has anybody seen this? I've tried lowering the Register >>>> Expiration and that seems to make it worse. If I lower it to 1 minute >>>> or 5 minutes, I lose them every 10-15 minutes. If I put it at 10 >>>> minutes, it loses connectivity once or twice a day. I tried Grandstream >>>> support and their answer was completely useless. Has anybody seen this? >>>> Or does anybody have any ideas? Again, no NAT involved, so don't say >>>> STUN or NAT issue. >>>> >>>> Peder >>>> >>>> _______________________________________________ >>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>>> >>>> asterisk-users mailing list >>>> To UNSUBSCRIBE or update options visit: >>>> http://lists.digium.com/mailman/listinfo/asterisk-users >>>> >>>> >>> _______________________________________________ >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>> >>> asterisk-users mailing list >>> To UNSUBSCRIBE or update options visit: >>> http://lists.digium.com/mailman/listinfo/asterisk-users >>> >>> >> _______________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
