Anca I got the following logs when subscribing:
Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:presence:build_dlg_t: CONTACT = sip:[email protected]:5060 ;transport=tcp Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:t_uac: next_hop=<sip:213.151.105.170:6666;lr=on> Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:core:mk_proxy: doing DNS lookup... Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:dlg2hash: 42964 Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:print_request_uri: sip:[email protected]:5060;transport=tcp Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:set_timer: relative timeout is 500000 Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:insert_timer_unsafe: [4]: 0x7f8fa84c0068 (4508500000) Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:set_timer: relative timeout is 30 Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:insert_timer_unsafe: [0]: 0x7f8fa84c0098 (4538) Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: INFO:presence:send_notify_request: NOTIFY sip:[email protected]<sip%[email protected]>via sip:213.151.105.170:6666;lr=on on behalf of sip:[email protected]<sip%[email protected]>for event presence Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:tm:t_unref: UNREF_UNSAFE: after is 0 Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:core:destroy_avp_list: destroying list (nil) Mar 11 15:28:40 test /usr/local/sbin/opensips[3258]: DBG:core:receive_msg: cleaning up Mar 11 15:28:40 test /usr/local/sbin/opensips[3259]: DBG:core:parse_msg: SIP Reply (status): Mar 11 15:28:40 test /usr/local/sbin/opensips[3259]: DBG:core:parse_msg: version: <SIP/2.0> Mar 11 15:28:40 test /usr/local/sbin/opensips[3259]: DBG:core:parse_msg: status: <200> Mar 11 15:28:40 test /usr/local/sbin/opensips[3259]: DBG:core:parse_msg: reason: <OK> What log could I add to your patch so we can get more details ? I recompiled the whole opensips and its modules just to make sure your patch is activated. Cheers Pascal On Thu, Mar 11, 2010 at 2:07 PM, Anca Vamanu <[email protected]> wrote: > Hi Pascal, > > I have just tested myself - with a Subscribe sent on udp and contact > with trasport=tcp and the Notify is sent over tcp. > I would suggest to run opensips in debug mode and paste the log messages > when starting the processing for sending the Notify ( starting with > "DBG:presence:build_dlg_t: CONTACT "). > > Regards, > > -- > Anca Vamanu > www.voice-system.ro > > > > Pascal Maugeri wrote: > > to: OpenSIPS users mailling list <[email protected] > > <mailto:[email protected]>> > > cc: Albert Petit <[email protected] <mailto:[email protected]>> > > > > Hello Anca > > > > Sorry but this patch does not help neither :-( > > > > FYI we applied it against rev 6706. > > > > I will test this afternoon with a subscriber that is not behind NAT, > > maybe we can isolate a bit more the problem. > > > > I'm going to answer to Iñaki's email providing tracers. > > > > Cheers > > Pascal > > > > > > > > On Wed, Mar 10, 2010 at 3:02 PM, Anca Vamanu <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Pascal, > > > > Please try this revised patch. It is also against svn, take a new > > copy of the tm module and apply it. > > > > Thanks and regards, > > > > > > -- > > Anca Vamanu > > www.voice-system.ro <http://www.voice-system.ro> > > > > > > > > Pascal Maugeri wrote: > > > > Hi Anca > > > > We just tested the patch you sent us but we don't see any > > difference. > > > > Just in case, we recompiled the whole server (first we updated > > to rev 6700) and applied the patch you kindly sent us: > > > > svn update > > ... > > patch -p0 < tm_proto_fix.patch > > make all > > make install > > service opensips restart > > > > The NOTIFY message is still sent over UDP :-( > > > > What information could we send you in order to help you ? > > > > A big thank you for your help and fast answer! > > > > Cheers > > Pascal > > > > On Tue, Mar 9, 2010 at 4:55 PM, Anca Vamanu <[email protected] > > <mailto:[email protected]> <mailto:[email protected] > > <mailto:[email protected]>>> wrote: > > > > Hi Pascal, > > > > We found the problem - the socket on which the Subscribe was > > received was always used when sending the Notify. > > Find attached a patch for tm module that should fix this > > problem. > > Please test and report the results. > > > > Regards, > > > > -- Anca Vamanu > > www.voice-system.ro <http://www.voice-system.ro> > > <http://www.voice-system.ro> > > > > > > > > > > Pascal Maugeri wrote: > > > > Hi > > > > Using opensips 1.6 we need to have the presence module > > to send > > NOTIFY over TCP rather than UDP when the size of the > > message > > is greater than a given MTU. > > > > We tried to force it sending a SUBSCRIBE with > > transport=tcp in > > Contact header: > > > > SUBSCRIBE > > sip:[email protected]<sip%[email protected]> > > <mailto:sip%[email protected]<sip%[email protected]> > > > > > > <mailto:sip%[email protected]<sip%[email protected]> > > <mailto:sip%[email protected]<sip%[email protected]> > >> > > > > <mailto:sip%[email protected]<sip%[email protected]> > > <mailto:sip%[email protected]<sip%[email protected]> > > > > > > <mailto:sip%[email protected]<sip%[email protected]> > > > > <mailto:sip%[email protected]<sip%[email protected]>>>> > SIP/2.0 > > > > > > [...] > > Contact: <sip:[email protected]:5233;transport=tcp> > > Event: presence > > > > > > but the NOTIFY messages are sent over UDP (observe the > > "transport=tcp" in the request line): > > > > NOTIFY sip:[email protected]:5233;transport=tcp > SIP/2.0 > > [...] > > Contact: <sip:[email protected]:6667 > > <http://sip:[email protected]:6667> > > <http://sip:[email protected]:6667> > > <http://sip:[email protected]:6667>> > > > > Subscription-State: active;expires=120 > > Content-Type: application/pidf+xml > > Content-Length: 1254 > > > > > > Could you please let me know what we should do to > > enable the > > sending over TCP ? I don't understand what we're doing > > wrong. > > > > Cheers > > Pascal > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>> > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > > Users mailing list > > [email protected] <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>> > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > [email protected] <mailto:[email protected]> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] <mailto:[email protected]> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
