isseus after upgrade to VitalPBX 2.3.3-1

VitalPBX Community Support General Discussion isseus after upgrade to VitalPBX 2.3.3-1

  • Post
    gerrykernan
    Participant
    Up
    0
    Down
    ::

    hi

    ive just updagded to 2.3.3-1

    but sip enpoint keep going unreachable now and getting warnings below

     

    [2019-06-10 16:01:31] WARNING[982]: chan_sip.c:3832 __sip_xmit: sip_xmit of 0x7f01d0039c50 (len 675) to 192.168.2.118:12712 returned -2: No such file or directory
    [2019-06-10 16:01:31] ERROR[982]: chan_sip.c:4321 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
    [2019-06-10 16:01:31] WARNING[982]: chan_sip.c:3832 __sip_xmit: sip_xmit of 0x7f01d003d200 (len 675) to 192.168.2.112:11902 returned -2: No such file or directory
    [2019-06-10 16:01:31] ERROR[982]: chan_sip.c:4321 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data
    [2019-06-10 16:01:31] WARNING[982]: chan_sip.c:3832 __sip_xmit: sip_xmit of 0x7f01d003c300 (len 676) to 192.168.2.116:12072 returned -2: No such file or directory
    [2019-06-10 16:01:31] ERROR[982]: chan_sip.c:4321 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data

    0
Viewing 5 replies - 1 through 5 (of 5 total)
  • Replies
    Up
    0
    Down
    ::

    We will release an update soon with Asterisk 16.4.0 who solves many issues on SIP protocol

    0
    gerrykernan
    Participant
    Up
    0
    Down
    ::

    thanks much appreciated

     

    gerry

    0
    Up
    0
    Down
    ::

    We just release the new version of VitalPBX who comes with Asterisk 16.4.0

    0
    eddy70
    Participant
    Up
    0
    Down
    ::
    Hi Jose,

    I’ve recently just updated my pbx to 2.4.2-4 and when i try to register a webrtc client, it comes up with the below error:

    == WebSocket connection from ‘210.7.14.118:52091’ forcefully closed due to fatal write error
    [2020-07-07 12:19:44] WARNING[10479]: res_http_websocket.c:831 __ast_websocket_uri_cb: WebSocket connection from ‘210.7.14.118:52261’ could not be accepted – no protocols out of ‘sip’ supported
    [2020-07-07 12:19:44] WARNING[10480]: res_http_websocket.c:831 __ast_websocket_uri_cb: WebSocket connection from ‘210.7.14.118:52263’ could not be accepted – no protocols out of ‘sip’ supported
    [2020-07-07 12:19:48] WARNING[10487]: res_http_websocket.c:831 __ast_websocket_uri_cb: WebSocket connection from ‘210.7.14.118:52266’ could not be accepted – no protocols out of ‘sip’ supported
    [2020-07-07 12:19:52] WARNING[10493]: res_http_websocket.c:831 __ast_websocket_uri_cb: WebSocket connection from ‘210.7.14.118:52267’ could not be accepted – no protocols out of ‘sip’ supported

    0
    Up
    0
    Down
    ::
    @eddy70

    Please, open a new thread for your issue.

    0
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘isseus after upgrade to VitalPBX 2.3.3-1’ is closed to new replies.