Hi Brian, So you have problems with a SUBSCRIBE that is internally generated by one of the presence modules? It is not a proxied request, right ?
Regards, Bogdan [email protected] wrote: > Hello list, > > An jeu., janv 21, 2010, [email protected] schrieb: > >> An mer., janv 20, 2010, Bogdan-Andrei Iancu schrieb: >> >>> [email protected] wrote: >>> >>>> Here's a record I see when I run 'opensipsctl ul show': >>>> >>>> AOR:: mylogin-osips >>>> Contact:: >>>> sip:[email protected]:2310;transport=tls;line=2acy67zm Q=1 >>>> Expires:: 560 >>>> Callid:: 2b21cdfae784-av13rj1txbsq >>>> Cseq:: 2 >>>> User-agent:: Bigphone123 >>>> Received:: sip:85.182.68.45:2240;transport=TLS >>>> State:: CS_SYNC >>>> Flags:: 0 >>>> Cflag:: 64 >>>> Socket:: tls:80.200.123.45:5061 >>>> Methods:: 7999 >>>> >>>> OpenSIPS is trying to reach the private IP number above from time >>>> to time, and I see this in the logs: >>>> >>>> Jan 19 17:57:20 name.host.tld <error> opensips[23432]: ERROR:tm:t_uac: >>>> attempt to send to >>>> 'sip:[email protected]:2310;transport=tls;line=2acy67zm' failed >>>> >>>> >>> the problem is not the private IP in the contact, as opensips >>> properly saved the source IP (of the REGISTER) too -> see the >>> Received field. So the Received field will be used over the Contact >>> for sending the requests to UAC. >>> >>> Now, what probably goes wrong in your case is that when using >>> TLS/TCP (connection oriented protos), after the REGISTER, the >>> connection is dropped and opensips cannot open later a TCP >>> connection behind a NAT :(....By default opensips closes the >>> inactive TCP connections. >>> >>> >> After running a socket listener on 192.168.0.31 on the OpenSIPS host: >> >> $ socat TCP4-LISTEN:2310,bind=192.168.0.31,reuseaddr - >> SUBSCRIBE sip:[email protected]:2310;transport=tls;line=2acy67zm >> SIP/2.0 >> Via: SIP/2.0/TCP 86.90.39.44;branch=G4z9hb82dK8.f144.0 >> To: <sip:[email protected]>;tag=ty6sjh9iz9 >> From: <sip:[email protected]>;tag=6c9d4319c74d756e6b696-baa1 >> CSeq: 11 SUBSCRIBE >> Call-ID: [email protected] >> Content-Length: 0 >> User-Agent: OpenSIPS (1.6.1-tls) >> Max-Forwards: 70 >> Event: dialog;sla >> Contact: <sip:[email protected]> >> Expires: 610 >> >> I'm trying to implement presence by using the presence, >> presence_xml, pua, and pua_bla modules. >> >> So it seems that one of these modules (see event dialog;sla) is >> getting the contact from the locations table (in AAA on our server) >> and ignoring the Received header. >> >> OpenSIPS replies to messages from UACs such as INVITE and CANCEL >> properly, and opens connections to the IP in Received. This problem >> is limited to the SUBSCRIBES sent from one of the presence modules. >> >> > ...and similar SUBSCRIBE messages (sent from one of the presence > modules) are not having this problem. They are almost the same as > the one above, but simply don't have a to tag. > > Greetings, > Brian > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
