On Fri, Jun 18, 2010 at 10:51 PM, Stefan Schmidt <s...@sil.at> wrote: > James Lamanna schrieb: >> It appears as though the 489 Bad Event response to the NAT keep alive >> event responds to the local address, instead of responding to the >> NATted address. >> This causes Linksys phones to go amber (no registration) after a short >> amount of time after placing calls. >> Turning the Linksys NAT keep alive off is a workound, but non-ideal in >> may situations. >> >> Apparently the asterisk devs don't even think this is a bug: >> https://issues.asterisk.org/view.php?id=17532 >> >> Has anyone dealt with this at all? >> >> Thanks. >> >> -- James >> > Hello james, > > in the SPA config webpage on EXT 1 in the Nat Keep Alive MSG you should > set $OPTIONS instead of $NOTIFY. > > then in your asterisk extension default context just set this: > > exten => s,1,Hangup > > then the phone will send a options packet and you will get a 200 OK > instead of 489 Bad event. > > this should help. > > best regards
Thanks Steve, I'll give that a try. I think I'll also look into why responses to NOTIFYs don't do the right thing in terms of NAT either. > > steve -- James -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
