Asterisk 18.12 - Transport ERROR WSS

Hello, In asterisk 18.12 the endpoint don’t receive a call (wss)

In console we have TRANSPORT_ERROR

In 18.11.3 version works with the same configurations

May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4497 handle_outgoing_request : PJSIP/9999-00000011: Method is INVITE

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4506 handle_outgoing_request : PJSIP/9999-00000011

[May 15 22:23:22] DEBUG [4649][C-00000009]: channel.c : 4469 indicate_connected_line : PJSIP/9302-00000010: Dropping redundant connected line update “” <9999>.

[May 15 22:23:22] DEBUG [31974]: res_pjsip/pjsip_resolver.c : 475 sip_resolve : Performing SIP DNS resolution of target ‘131.196.XXX.XXX’

[May 15 22:23:22] DEBUG [31974]: res_pjsip/pjsip_resolver.c : 502 sip_resolve : Transport type for target ‘131.196.XXX.XXX’ is ‘(null)’

[May 15 22:23:22] DEBUG [31974]: res_pjsip/pjsip_resolver.c : 523 sip_resolve : Target ‘131.196.225.225’ is an IP address, skipping resolution

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4631 session_inv_on_state_changed : PJSIP/9999-00000011 Event: TSX_STATE Inv State: DISCONNCTD

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4368 __print_debug_details : Function session_inv_on_state_changed called on event TSX_STATE

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4382 __print_debug_details : The state change pertains to the endpoint ‘9999(PJSIP/9999-00000011)’

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4387 __print_debug_details : The inv session still has an invite_tsx (0x7f2f5c00fdc8)

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4402 __print_debug_details : There is no transaction involved in this state change

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4404 __print_debug_details : The current inv state is DISCONNCTD

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4657 session_inv_on_state_changed : PJSIP/9999-00000011: Source of transaction state change is TRANSPORT_ERROR

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4704 session_inv_on_state_changed :

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4749 session_inv_on_tsx_state_changed : PJSIP/9999-00000011 TSX State: Terminated Inv State: DISCONNCTD

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4368 __print_debug_details : Function session_inv_on_tsx_state_changed called on event TSX_STATE

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4382 __print_debug_details : The state change pertains to the endpoint ‘9999(PJSIP/9999-00000011)’

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4390 __print_debug_details : The inv session does NOT have an invite_tsx

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4393 __print_debug_details : The UAC INVITE transaction involved in this state change is 0x7f2f5c00fdc8

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4397 __print_debug_details : The current transaction state is Terminated

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4399 __print_debug_details : The transaction state change event is TRANSPORT_ERROR

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4404 __print_debug_details : The current inv state is DISCONNCTD

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4770 session_inv_on_tsx_state_changed : Disconnected

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4181 session_on_tsx_state : (null session) TSX State: Terminated Inv State: DISCONNCTD

[May 15 22:23:22] DEBUG [31974]: res_pjsip_session.c : 4189 session_on_tsx_state :

If you believe an issue has been introduced then the issue tracker[1] is where things should go, including a complete trace of both working and non-working.

[1] System Dashboard - Digium/Asterisk JIRA

I would be happy if you share a solution if you find one. I also experience the same problem.

@shmuel4 An issue was filed at [ASTERISK-30065] pjsip: Open Websocket connection is not reused for outgoing requests - Digium/Asterisk JIRA and you can log in and add yourself as a watcher for future updates.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.