Have a vendor that produced a pjsip-based app for Android that forms the TO and FROM headers with no angle brackets (<>) separating the URI from non-URI parameters i.e. tag. URI forms as follows: sip:alice at atlanta.com;tag=xxxxx-xxxxx-xxxxx I understand that that, as other folks have posted, "According to RFC 3261, the angle brackets around the SIP address are not required for the To..." (or FROM) "...header if using the addr-spec instead of the name-addr format" It seems that the industry at large has defaulted to the "name-addr" form of these headers and ignores the "addr-spec" form. I have several SIP applications (old and new) that won't accept the URI in the "addr-spec" format so calls fail when initiated from the Android (pjsip) application. I think the answer lies in the header format (angle brackets), so the following should always be accepted: <sip:alice at atlanta.com>;tag=xxxxx-xxxxx-xxxxx My vendor's engineering dept. doesn't seem to be open to exploring that idea, so I thought I'd take on a hobby/project of decoding their app to see if I could change that specific behavior. I've never coded an app or done this type of thing otherwise, so if it sounds overly complex for the average IT dude, feel free to shoot me down. Otherwise any advice or direction in regards to decoding the .apk, .odex, and other files, editing them, and recompiling would be greatly appreciated. For reference, other pjsip-based clients (notably MicroSIP) function correctly in my environment. the only thing I can see different between MicroSIP and the Android client is the angle brackets in the FROM and TO headers. (present n MicroSIP, absent in Android client) Thanks in advance for any advice. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20150630/73c6f2cf/attachment.html>
