James Lamanna
2010-Jun-19 01:58 UTC
[asterisk-users] Linksys SPA94x keep-alive reply replies to wrong address (1.4.32)
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 SIP trace: U external.ip:9375 -> asterisk.ip:5060 NOTIFY sip:asterisk.ip SIP/2.0..Via: SIP/2.0/UDP 10.10.30.65:9375;branch=z9hG4bK-8ebce8bc..From: "xxx-xxx-xxxx" <sip:9497197231 at asterisk.ip>;tag=3a6a735864619b8bo0..To: <sip:asterisk.ip>..Call-ID: 19a0bd7 c-3cb137b7 at 10.10.30.65..CSeq: 395 NOTIFY..Max-Forwards: 70..Contact: "xxx-xxx-xxxx" <sip:xxxxxxxxxx at 10.10.30.65:9375>..Event: keep-alive..User-Agent: Linksys/SPA942-6.1.3(a)-000e08d87445..Content-Length: 0.... # U asterisk.ip:5060 -> 10.10.30.65:9375 SIP/2.0 489 Bad event..Via: SIP/2.0/UDP 10.10.30.65:9375;branch=z9hG4bK-8ebce8bc;received=external.ip..From: "xxx-xxx-xxxx" <sip:9497197231 at asterisk.ip>;tag=3a6a735864619b8bo0..To: <sip:asterisk.ip>;tag=as4a 4466b0..Call-ID: 19a0bd7c-3cb137b7 at 10.10.30.65..CSeq: 395 NOTIFY..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO..Supported: replaces..Content-Length: 0....
Stefan Schmidt
2010-Jun-19 05:51 UTC
[asterisk-users] Linksys SPA94x keep-alive reply replies to wrong address (1.4.32)
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 steve