ok :) one less bug to trace ;).

regards, bogdan

Klaus Darilion wrote:

I've found the problem - it was a config bug (copy paste):

sl_send_reply("403","......\n"); ^^^^ regards klaus

Bogdan-Andrei Iancu wrote:

...

no idea ....does it happen also only onTCP? I will try to debug it also...

regards, bogdan

Klaus Darilion wrote:

...

Hi! I have the following problem

openser1 <-----TLS----> openser2

-----INVITE------------> <------403--------------

openser1 does not like the 403 response (generated with sl_send_reply()).

tcp_read_headers: ERROR: no clen, p=A ERROR: tcp_read_req: bad request, state=4, error=4 buf: SIP/2.0 403 do not reuse this TLS connection ^M Via: SIP/2.0/TLS 10.10.0.41:5063;branch=z9hG4bK2ac3.a346b0f3.0^M Via: SIP/2.0/UDP 10.10.0.41;branch=z9hG4bK2ac3.54290e8.0^M Via: SIP/2.0/UDP 10.10.0.205:7836;branch=z9hG4bK-d87543-4f7f2765412a2d12-1--d87543-;rport=7836^M To: sip:+43201@proxy1.ienum.labs.nic.at;tag=10ad1f9ed36b57d334f8c84f393c0304.7a7e^M From: sip:user101@proxy1.ienum.labs.nic.at;tag=ca36697e^M Call-ID: 6c71b8428247c758@d2lnd2Ft^M CSeq: 2 INVITE^M server_header: BP 2^M Content-Length: 0^M Warning: 392 10.10.0.42:5063 "Noisy feedback tells: pid=2661 req_src_ip=10.10.0.41 req_src_port=32918 in_uri=sip:+43201@bp2.ienum.labs.nic.at;transport=tls out_uri=sip:+43201@bp2.ienum.labs.nic.at;transport=tls via_cnt==3"^M ^M parsed: SIP/2.0 403 do not reuse this TLS connection ^M

Does someone knows this problem? If not, I will debug next week :-(

regards klaus

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users