RFC 3261 Table 1: Use and default values of URI components for SIP header field values, Request-URI and references SER/OpenSER has this issue if we use uri!=myself to check From. regards, Gang On Tue, Mar 24, 2009 at 4:50 PM, Amit Sharma <amit398 at gmail.com> wrote: > Hi, > PJSIP doesn't print the port in from and to headers even when the > port is explicitly specified. This seems to be intentional > > pjsip/src/pjsip/sip_uri.c line 276-278 > > /* Only print port if it is explicitly specified. > * Port is not allowed in To and From header. > */ > > I couldn't find the relevant section in the rfc which prohibits port > in from and to headers. > > The behavior causes an issue where the domain proxy is listening on a > non standard port and transfer with replaces is attempted on an > existing call. > > The issue occurs because the referred-to uri doesn't have the > non-standard port in the uri and the subsequent invite(for replace) > fails > as the proxy is only listening on a non-standard port and not 5060. > > Thanks, > Amit > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090324/fb818007/attachment.html>
