WebRTC unreachable after update Unsupported transport (PJSIP_EUNSUPTRANSPORT)

Reporting an Issue VitXi WebRTC
1

Last update broke WebRTC.
Outgoing calls are fine, but the registration is broken, so webrtc extensions are not reachable.

VitalPBX from 3.2.1 R1 to 3.2.3 R2
VitXi WebRTC from 1.0.6-7 to 1.1.1-3

== WebSocket connection from ‘195.134.172.171:47918’ for protocol ‘sip’ accepted using version ‘13’
– Added contact ‘sip:195.134.172.171:47918;transport=ws’ to AOR ‘bellq-404’ with expiration of 7200 seconds
[2022-08-17 08:38:50] ERROR[1755]: res_pjsip.c:1619 endpt_send_request: Error 171060 ‘Unsupported transport (PJSIP_EUNSUPTRANSPORT)’ sending NOTIFY request to endpoint bellq-404
[2022-08-17 08:38:50] ERROR[8291]: res_pjsip.c:1619 endpt_send_request: Error 171060 ‘Unsupported transport (PJSIP_EUNSUPTRANSPORT)’ sending OPTIONS request to endpoint bellq-404
– Contact bellq-404/sip:195.134.172.171:47918;transport=ws is now Unreachable. RTT: 0.000 msec

Switching to deafault PJSIP profile and asterisk restart did not help.

PJSIP_Endpoints
PJSIP_Endpoints884×56 6.63 KB

WebRTC_404
WebRTC_4042225×737 78.6 KB

WebRTC_Profile
WebRTC_Profile2532×1051 154 KB

1 Like
2

Hello sir,

Please, when you have no active calls, try to reload the asterisk service: systemctl restart asterisk then check if the extensions are registered correctly.

Regards,

3

Asterisk restart did not help.

In the asterisk logs I see many warnings if I apply changes.

All trunks and normal pjsip extensions are working fine, only webrtc cant register (since the update).

4

Try

yum clean all
yum update -y
1 Like
5

Thanks, that solved the problem for webrtc.
I still see this warnings in the logs when apply changes, but it does work.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-udp-3baa003c2d301de89c68’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-tcp-37eda84c495b784c1dd0’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-tls-608c7bb6130ab9815fbe’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-ws-4a22e66ed2320d0b84e8’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-wss-eb7e9c0a1b729f563090’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.
[2022-08-18 06:20:28] WARNING[31352]: res_pjsip/config_transport.c:745 transport_apply: Transport ‘transport-tls-ms-teams-bef5de028ca2dda67de6’ is not fully reloadable, not reloading: protocol, bind, TLS, TCP, ToS, or CoS options.

1 Like
6

hi!

It seems to be related to the latest version of Asterisk, web will test it on our development servers…

7

That’s totally normal. It means that the parameter “Allow transport Reload” is disabled under the PJSIP Settings module. When this parameter is disabled, you need to restart Asterisk to reload the PJSIP Transports.

8

After asterisk restart the transport warnings are still there. System reboot did not help either. Fortunately the warnings seems to do no harm, everything seems to work. Maybe it is a bug in Asterisk 18.12.1.

9

Restarting Asterisk only applies the Transport changes but doesn’t remove the warning.

10

same problem for me. Asterisk version 18.12.1.
Can we upgrade asterisk?
I read that:
“there was a bug with WebRTC so you want to be in at least 18.12.1”
… “Thank you. The issue has been fixed on a recent version of Asterisk 18.13.0”