On Thu, 2009-12-17 at 16:29 -0600, Eric Varsanyi wrote: > After having a problem with Audiocodes I picked up a few linksys spa > 3102's. They have a widely reported problem of sending non-sip > compliant headers for callerid (they don't quote the caller id string > even if it contains special characters). > > >From the postings on the Linksys/Cisco forums it appears this problem > is long standing and they are not going to fix it. > > I hacked up the SIP message receive function in sipXtackLib to try to > fix these specific broken headers. Its certainly not standards > compliant and not something anyone would want in a released codebase, > but it does work around the problem in at least my limited setup > (Polycom 650's and 335's, linksys SPA 3102's) and doesn't have any > other obvious bad effects. It looks for unquoted addresses in inbound > From and Remote-Party-Id fields and adds quotes in the parsed out > SipMessage fields (it leaves the raw packet text untouched for > debugging). > > Would it be appropriate to post a patch to this list or post a URL to > it in case anyone else needs to get one of these evil things working? > > I'd be willing to rework it so it is an optional plugin, but I'm new > to your codebase and it didn't look like any plugins had access to the > message stream early enough to not require tons of changes (I put the > hack in the SipClient::preprocessMessage function). > > If there's interest in cleaning it up for inclusion I'd be open to a > review and suggestions, otherwise I'd just like to make it available > in case someone is stuck with one of these and has no other easy way > out. I sure wish Audiocodes would have worked for me, the SPA was > quite a hassle.
Let's do this ... please create an issue in the tracker (summary something like "Linksys URI special character workaround" and attach a clean-as-possible version of the patch you've got to it. Some of the people who can best review how to incorporate it are on extended holiday until after New Years, so it will be a little while before we decide what if anything to do with it. I'd also be interested in finding out where the problem manifests (that is, what goes wrong) when you _don't_ have the patch... _______________________________________________ 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/
