I know your tips for SER. But it wouldn't work if there is another SIP UA using 5060 at the same IP.The record-route would be broken. regards, Gang On Tue, Mar 24, 2009 at 7:53 PM, Amit Sharma <amit398 at gmail.com> wrote: > Thanks Gang. > > I do see that port is not allowed for from and to in the table. I > can't really figure out the reason for this though. If the from or to > uri is used to construct a request-uri (as in the case of replaces) > the port information is gone. > > Regarding the problem with ser/openser, you would have to specify > additional aliases for the non standard ports for the comparison you > mentioned to work (this works in 1.2.2 for sure) > > e.g > listen=a.b.c.d > listen=a.b.c.d:ns1 > listen=a.b.c.d:ns2 > > alias=domain.proxy.com > alias=domain.proxy.com:ns1 > alias=domain.proxy.com:ns2 > > > > 2009/3/24 Gang Liu <gangban.lau at gmail.com>: > > 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 > > > > > > _______________________________________________ > > 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 > > > > > > _______________________________________________ > 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/20090326/9bab54bb/attachment.html>
