Hi Slava,
1) NOTIFY'es
The presence NOTIFY requests are in dialog requests (part of the
SUBSCRIBE dialog). And a sequential request is sent to a RR or Contact
URI (from SUBSCRIBE) which typically hold IP addresses - so how do you
get the @domain.com URI when sending the NOTIFY ? Do you have a SIP
capture showing the SUBSCRIBE + 200 OK and the NOTIFY errors ?
2) BLF parsing errors - these are 3.0 specific, right ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit 2019
https://www.opensips.org/events/Summit-2019Amsterdam/
On 02/12/2019 05:13 AM, Slava Bendersky wrote:
Hello Everyone,
I manage fix route DNS issue for presence NOTIFY
But I can't route presence NOTIFY with TLS transport on public leg
Text in bold missing ;tranposrt=tls
Do I need add local route and catch NOTIFY and add transport=tls ?
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
INFO:presence:update_subscription: notify
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
INFO:presence:send_notify_request: NOTIFY sip:[email protected] via
*sip:106@public_ip:18156;nat=yes*;ob on behalf of
sip:[email protected] for event presence,
to_tag=656a154e9c9480ea0e92b7b8c389691c-5e5c, cseq=2
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 88
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:proto_tls:tls_conn_init: no TLS client domain found
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:core:tcpconn_new: failed to do proto 3 specific init for conn
0x7f2be9aece58
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:core:tcp_conn_new: tcpconn_new failed
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:proto_tls:tls_sync_connect: tcp_conn_create failed, closing the
socket
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:proto_tls:proto_tls_send: connect failed
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]: ERROR:tm:msg_send:
send() to public_ip:5081 for proto tls/3 failed
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
ERROR:tm:t_forward_nonack: sending request failed
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]: ERROR:tm:w_t_relay:
t_forward_nonack failed
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1280]:
INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1280]:
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 109
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1277]:
ERROR:proto_tls:tls_accept: New TLS connection from public_ip:49523
failed to accept
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1277]:
ERROR:proto_tls:tls_read_req: failed to do pre-tls reading
Feb 11 22:03:17 vprx00 /usr/sbin/opensips[1276]:
WARNING:presence:p_tm_callback: completed with status [500] and to_tag
[656a154e9c9480ea0e92b7b8c389691c-5e5c], cseq [CSeq: 2]
volga629
------------------------------------------------------------------------
*From: *"Slava Bendersky" <[email protected]>
*To: *"OpenSIPS users mailling list" <[email protected]>
*Sent: *Wednesday, February 6, 2019 10:58:38 AM
*Subject: *[OpenSIPS-Users] presence and dns
Hello Everyone,
How to avoid dns look up while NOTIFY is trying to reach end point for
presence subscriber.
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]:
INFO:presence:update_subscription: notify
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]:
INFO:presence:send_notify_request: NOTIFY sip:[email protected] via
sip:[email protected]:58924;nat=yes;ob on behalf of
sip:[email protected] for event presence,
to_tag=656a154e9c9480ea0e92b7b8c389691c-0448, cseq=1
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]:
CRITICAL:core:mk_proxy: could not resolve hostname: "domain.com"
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]: ERROR:tm:uri2proxy:
bad host name in URI <sip:[email protected]>
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]:
ERROR:tm:t_forward_nonack: failure to add branches
Feb 5 15:15:42 vprx00 /usr/sbin/opensips[3889]: ERROR:tm:w_t_relay:
t_forward_nonack failed
Also Pua Dialog Info producing the error of extra parameters
Feb 5 15:42:21 vprx00 /usr/sbin/opensips[4137]:
ERROR:pua_dialoginfo:pack_cb_params: Failed to parse peer nameaddr
[sip:[email protected]:5060#015#012]
Feb 5 15:42:21 vprx00 /usr/sbin/opensips[4137]:
ERROR:pua_dialoginfo:dialoginfo_set: Failed to allocate parameters
Feb 5 18:27:20 vprx00 /usr/sbin/opensips[5451]:
ERROR:pua_dialoginfo:pack_cb_params: Failed to parse peer nameaddr
[sip:[email protected]#015#012]
Feb 5 18:27:20 vprx00 /usr/sbin/opensips[5451]:
ERROR:pua_dialoginfo:dialoginfo_set: Failed to allocate parameters
volga629
_______________________________________________
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