Hi Benny, Thanks for the reply. Ok, I thought the Route URI transport param has higher priority than the transport switching feature. Here's log I get : 14:52:52.299 tcpc0x1b853ac .......TCP client transport created 14:52:52.299 tcpc0x1b853ac .......TCP transport 172.20.254.171:45351 is connecting to xx.xxx.xxx.xxx:5060... 14:52:52.299 pjsua_core.c .......TX 1563 bytes Request msg INVITE/cseq=23803 (tdta0x1ace708) to *tcp* xx.xxx.xxx.xxx:5060: INVITE sip:XXXXXXX at domain.dom.ru SIP/2.0 v: SIP/2.0/TCP 172.20.254.171:45351;rport;branch=z9hG4bKPj7FTejgGLlRkPuvGobtlt5EXMEdH55yBB Max-Forwards: 70 f: <sip:me at domain.dom.ru>;tag=2zWyuFaby5MeaubVTAnyCjbxkLx40HEj t: <sip:XXXXXXX at domain.dom.ru> m: <sip:me at yy.yyy.yyy.yy:5060;ob>;+sip.ice i: SAVHJ4dCRR.2O-Kw4q2EeeViDKS-Dm8N CSeq: 23803 INVITE *Route: <sip:domain.dom.ru;transport=udp;lr> * k: replaces, 100rel, timer, norefersub x: 1800 Min-SE: 90 ..... ..... That's why I was surprised. I'll do more tests and RFC reading to understand my mistake. Sorry for the noise. On 13/07/2012 14:43, Benny Prijono wrote: > Hi R?gis, > > I rather doubt that the behavior has changed. Switching is done > against the next hop, whether the next hop is specified by request URI > or by Route URI. So the current behavior sounds correct to me. > > Best regards, > Benny > > On Fri, Jul 13, 2012 at 7:30 PM, R?gis Montoya <r3gis.3r at gmail.com > <mailto:r3gis.3r at gmail.com>> wrote: > > Hi, > > I just noticed a change in the behavior of the automatic switch > from UDP to TCP. > > Previously if a proxy was configured on the account with > ";transport=udp", it was sure that all requests for this account > will use UDP (even if packet size is bigger than > PJSIP_UDP_SIZE_THRESHOLD value). > > Apparently, the behavior is now different. Even with > ";transport=udp" on the proxy, if the packet size is too big it > will switch to TCP. > Does somebody else observed that ? > Also, I'm wondering if this change was expected ? and if doesn't > break the fact that when specifying transport for the proxy we > could expect it to be set to UDP ? > In my opinion, the previous behavior was pretty good (and also > permits to set the disable_tcp_switch per account as soon as there > is a proxy which is a common case). > > I'm on r1476, I'll upgrade to latest and I'll also try to find > what introduced this change in the behavior. > > Best regards, > R?gis > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org <mailto: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/20120713/43fcc238/attachment.html>
