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:9497197...@asterisk.ip>;tag=3a6a735864619b8bo0..To: <sip:asterisk.ip>..Call-ID: 19a0bd7 c-3cb13...@10.10.30.65..cseq: 395 NOTIFY..Max-Forwards: 70..Contact: "xxx-xxx-xxxx" <sip:xxxxxxx...@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:9497197...@asterisk.ip>;tag=3a6a735864619b8bo0..To: <sip:asterisk.ip>;tag=as4a 4466b0..Call-ID: 19a0bd7c-3cb13...@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.... -- _____________________________________________________________________ -- 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
