Sorry, you're right of course, the NOTIFY coming from the SPA is missing the contact field. I was looking at the INVITE.
I vaguely remember its only mandatory on INVITE and the response to an invite. If its not mandatory than the fix to freeswitch is the appropriate fix, if it is mandatory then I'll update my 3102 'fixer' code to add it on proxy ingress (since afaict Cisco does not fix 3102 problems, its a 'dead' product from their perspective). -Eric On Jan 3, 2010, at 11:30 PM, Scott Lawrence wrote: > On Sun, 2010-01-03 at 17:19 -0600, Eric Varsanyi wrote: >> MikeJ of the FreeSwitch project sent me a patch (thank you!) that just >> ignores the lack of a Contact header when processing the NOTIFY >> message. This does fix the immediate problem (FreeSwitch doesn't SEGV >> and I can press 'Reject' as soon as I like and the caller goes to >> voicemail) but it still seems "wrong" (per the RFC) that the Contact >> header is missing on the NOTIFY/Ringing... message from sipXproxy. >> >> I'm happy to help (try patches/more testing/whatever), even a shove in >> the right direction as to where to dig deeper. > > You're correct that it is a bug not to send a Contact in that NOTIFY, > but you've got the wrong culprit. The sipXproxy is just forwarding it - > that message comes from the Linksys and didn't have a Contact there > either, so you'll have to take it up with them. > > If you'd like, and you can't file an issue with Linksys in some public > place, you can file an issue in the External project at > track.sipfoundry.org to record the facts. You've done a good job of > documenting the problem (the messages in a sipviewer trace have frame > numbers - it's easier to identify them that way than copying them, but > that's a nit... good job). > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
