# WebRTC unreachable after update Unsupported transport (PJSIP\_EUNSUPTRANSPORT) **URL:** https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665 **Category:** VitXi WebRTC **Created:** [August 17, 2022, 7:39am UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665 "2022-08-17T07:39:20Z") **Posts on this page:** 10 **Page:** 1
### Author: ![mvdvorm](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mvdvorm](https://forums.vitalpbx.org/u/mvdvorm) #### Post date: [August 17, 2022, 7:39am UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/1 "2022-08-17T07:39:20Z")
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](https://forums.vitalpbx.org/uploads/default/original/2X/d/d88ce544f7070dce3417ce431f1108035def310d.png) ![WebRTC_404](https://forums.vitalpbx.org/uploads/default/original/2X/f/f773b6597c827d3324c129ab4d3aebbd12daa08a.png) ![WebRTC_Profile](https://forums.vitalpbx.org/uploads/default/original/2X/c/c38f18251ec42722f8891731a5935b3df6801342.png) ---
### Author: ![maynor](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/3e96dc/32.png) [@maynor](https://forums.vitalpbx.org/u/maynor) #### Post date: [August 17, 2022, 4:10pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/2 "2022-08-17T16:10:55Z")
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, ---
### Author: ![mvdvorm](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mvdvorm](https://forums.vitalpbx.org/u/mvdvorm) #### Post date: [August 17, 2022, 7:47pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/3 "2022-08-17T19:47:37Z")
Asterisk restart did not help. In the asterisk logs I see many warnings if I apply changes. > **[\-- Reloading module 'extconfig' (Configuration) == Binding queue\_log to o -...](https://pastebin.com/jKbkPvrn)** > > Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time. All trunks and normal pjsip extensions are working fine, only webrtc cant register (since the update). ---
### Author: ![PitzKey](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pitzkey/32/420_2.png) [@PitzKey](https://forums.vitalpbx.org/u/PitzKey) #### Post date: [August 18, 2022, 12:53am UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/4 "2022-08-18T00:53:27Z")
Try ```auto yum clean all yum update -y ``` ---
### Author: ![mvdvorm](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mvdvorm](https://forums.vitalpbx.org/u/mvdvorm) #### Post date: [August 18, 2022, 4:25am UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/5 "2022-08-18T04:25:05Z")
> [@maynor](#): > > systemctl restart asterisk 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. ---
### Author: ![maynor](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/3e96dc/32.png) [@maynor](https://forums.vitalpbx.org/u/maynor) #### Post date: [August 18, 2022, 7:19pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/6 "2022-08-18T19:19:05Z")
hi! It seems to be related to the latest version of Asterisk, web will test it on our development servers… ---
### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel) #### Post date: [August 22, 2022, 1:31pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/7 "2022-08-22T13:31:00Z")
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. ---
### Author: ![mvdvorm](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@mvdvorm](https://forums.vitalpbx.org/u/mvdvorm) #### Post date: [August 22, 2022, 1:51pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/8 "2022-08-22T13:51:30Z")
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. ---
### Author: ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel) #### Post date: [August 22, 2022, 2:41pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/9 "2022-08-22T14:41:14Z")
Restarting Asterisk only applies the Transport changes but doesn’t remove the warning. ---
### Author: ![pawel319](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pawel319/32/1617_2.png) [@pawel319](https://forums.vitalpbx.org/u/pawel319) #### Post date: [November 14, 2022, 2:43pm UTC](https://forums.vitalpbx.org/t/webrtc-unreachable-after-update-unsupported-transport-pjsip-eunsuptransport/1665/10 "2022-11-14T14:43:16Z")
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”