Just tested by changing the listening port from TLS to TCP (5061 to 5060) and registration occurs without any errors. This means something in the TLS connection is failing: maybe the record route URI? How do I set this anyway? On 7 Jul 2015 05:16, "Nabeel" <[email protected]> wrote:
> Also getting these errors in the same log; they may be related: > > ERROR:core:tls_blocking_write: TLS send timeout (30000) > > ERROR:core:tcp_send: failed to send > ERROR:tm:msg_send: tcp_send failed > ERROR:tm:t_forward_nonack: sending request failed > > ERROR:core:tls_accept: New TLS connection from 87.xx.xxx.42:42997 failed > to accept > ERROR:core:tls_accept: TLS error: (ret=-1, err=5, errno=32/Broken pipe): > > > > On 7 July 2015 at 04:31, Nabeel <[email protected]> wrote: > >> Hi, >> >> I added a NAPTR record to my domain for TLS. OpenSIPS resolves this >> correctly and does the SRV lookup for the correct port, but then fails to >> register with the following error. Please advise how to fix. >> >> DBG:core:tcp_read_req: last char=0x0A, parsed msg=#012REGISTER sip: >> server.mydomain.com SIP/2.0#015#012Via: SIP/2.0/TLS >> 10.174.254.93:37559;rport;branch=z9hG4bK78314#015#012Max-Forwards: >> 70#015#012To: <sip:[email protected]>#015#012From: < >> sip:[email protected]>;tag=z9hG4bK99091243#015#012Call-ID: >> [email protected]#015#012CSeq >> <http://[email protected]#015%23012CSeq>: 1 >> REGISTER#015#012Expires: 3600#015#012User-Agent: >> MyApp/1.3.0/SM-G900F#015#012Contact: >> <sip:[email protected]:37559;transport=tls>;reg-id=1;+sip.instance="<urn:uuid:d52851ce-0a00-421a-98fc-4bad71ce346c>"#015#012Supported: >> path, outbound#015#012Content-Length: 0 >> >> ERROR:core:tcpconn_add_alias: possible port hijack attempt >> ERROR:core:tcpconn_add_alias: alias already present and points to another >> connection (39 : 5061 and 40 : 5061) >> ERROR:core:receive_msg: tcp alias failed >> > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
